Are there guidelines or recommendations as to how one should structure the administration of Windows Azure services aside from what I'm finding here? -- http://msdn.microsoft.com/en-us/library/azure/hh531793.aspx  I need clarification on what happens if I use all Organizational Accounts for Azure administration, as is suggested in the above link, and then my Azure-hosted ADFS farm craps out leaving none of my administrators able to authenticate to manage the Windows Azure account.  Should we be adding a backup non-organizational Microsoft account as a Service Admin in order to protect against this possibility?

• Edited by pkpkpk Tuesday, April 08, 2014 4:31 PM clarified question

hello,

Do you want to add co-administrator into your service?

I suppose that's the question, isn't it?

If the authentication for all of our administrative accounts is handled by an ADFS farm hosted in Windows Azure, and something happens to the ADFS farm that makes it unable to process logins, then conceivably none of my administrative accounts can log into Windows Azure to resolve the issue.  Should it be recommended that not all of the admin accounts be organizational accounts (as defined by the link in my original post) and that an external Microsoft account should be added as a backup?  Am I missing something key here?  I'd rather not create an external Microsoft account with so much administrative clout if I don't have to, but I don't really see another option.

You don't have to use ADFS for the highest account administrator. You can use the default account (Microsoft ID or an organization account with domain yourorg.onmicrosoft.com). You can create custom domains, but the default domain should still be available. So even if the ADFS is down, you can still use the highest account administrator to manage everything.