5. What is Azure Multi-Factor Authentication? An Azure Identity and Access management service that prevents unauthorized access to both on- premises and cloud applications by providing an additional level of authentication Trusted by thousands of enterprises to authenticate employee, customer, and partner access.

6. How It Works

8. MFA for Office 365 Azure Multi-Factor Authentication Administrators can Enable/Enforce MFA to end-usersYes Use Mobile app (online and OTP) as second authentication factorYes Use Phone call as second authentication factorYes Use SMS as second authentication factorYes Application passwords for non-browser clients (e.g. Outlook, Lync)Yes Default Microsoft greetings during authentication phone callsYes Remember Me (Public Preview coming in June)*Yes Custom greetings during authentication phone callsYes Fraud alertYes MFA SDKYes Security ReportsYes MFA for on-premises applications/ MFA Server.Yes One-Time BypassYes Block/Unblock UsersYes Customizable caller ID for authentication phone callsYes Event ConfirmationYes IP Whitelist (currently in Public Preview)*Yes

10. Users must also authenticate using their phone or mobile device before access is granted. Users sign in from any device using their existing username/password.

12. 01234 No devices or certificates to purchase, provision, and maintain No end user training is required Users replace their own lost or broken phones Users manage their own authentication methods and phone numbers Integrates with existing directory for centralized user management and automated enrollment

13. Works with all leading on-premises applications Supports ADFS and SAML-based apps for federation to the cloud Built into Microsoft Azure Active Directory for use with cloud apps SDK for integration with custom apps and directories Reliable, scalable service supports high-volume, mission-critical scenarios

14. Strong multi-factor authentication Real-Time Fraud Alert PIN option Reporting and logging for auditing Enables compliance with NIST 800-63 Level 3, HIPAA, PCI DSS, and other regulatory requirements

16. Users must also authenticate using their phone or mobile device before access is granted. Users sign in from any device using their existing username/password.

17. SessionTitleTimeslot FDN02Enabling Enterprise Mobility with Windows Intune, Microsoft Azure, and Windows ServerMonday, May 12 11:00 AM - 12:00 PM DCIM-B382Cloud Identity and Access Management: Microsoft Azure Active Directory PremiumTuesday, May 13 10:15 AM – 11:30 AM OFC-B250Multi-Factor Authentication for Office 365Wednesday, May 14 10:15 AM - 11:30 AM PCIT-B212Design Considerations for BYODTuesday, May 13 10:15 AM - 11:30 AM PCIT-B213Access Control in BYOD and Directory Integration in a Hybrid Identity InfrastructureWednesday, May 14 3:15 PM - 4:30 PM PCIT-B310Empowering Your Users and Protecting Your Corporate DataMonday, May 12 1:15 PM - 2:30 PM PCIT-B313Hybrid Identity: Extending Active Directory to the CloudMonday, May 12 4:45 PM - 6:00 PM PCIT-B314Understanding Microsoft’s BYOD Strategy and an Introduction to New Capabilities in Windows Server 2012 R2 Tuesday, May 13 8:30 AM - 9:45 AM PCIT-B330Active Directory + BYOD = Peace of MindThursday, May 15 8:30 AM - 9:45 AM

19. www.microsoft.com/learning http://microsoft.com/msdn http://microsoft.com/technet http://channel9.msdn.com/Events/TechEd