Windows Azure Multi-Factor Authentication Release Notes
Published: September 23, 2013
Updated: September 30, 2013
Welcome to the release notes for Windows Azure Multi-Factor Authentication. Before you attempt to use and configure Multi-Factor Authentication, we recommend that you read this entire document and Securing access to cloud services - Information for Administrators. You can use these notes to guide you as you troubleshoot issues that may arise when you use Windows Azure Multi-Factor Authentication.
Microsoft Account Users in a directory Global Admin role need to use their Organizational ID to manage Multi-Factor Authentication
When you click on the Manage Multi-Factor Auth button, a new window appears stating the Microsoft Account is not supported. To work around this issue, sign out and then sign-in with your Organizational ID credentials.
Users who are admins in multiple directories can only manage MFA for their home directory.
This is a known issue.
Users who are federated cannot use app passwords.
This is a known issue. App password use with federated users is currently in private preview.
Unable to Create App Passwords in Internet Explorer 11
When creating an App Password while using Internet Explorer 11, you may be unable to click the “next” button after providing a name for your App Password. If you experience such this issue, please turn on compatibility mode by following these steps and try creating your app password again.
Users who authenticate by using mobile application notifications may receive an “Authentication request is not for an activated account” error
Follow the steps at What do I do when I see a “Authentication request is not for an activated account” error? if you see this error.