-->
Authenticator generates 2-Step Verification codes in your browser. Use it to add an extra layer of security to your online accounts. IMPORTANT. Always keep a backup of your secrets in a safe location. Encrypting your secrets is strongly recommended, especially if you are logged into a Microsoft Account.
This article applies to both Office 365 Enterprise and Microsoft 365 Enterprise.
Microsoft remote desktop mac 8 vs 10. This version is definitely NOT an improvement over 8. Wad11656, Fantastic, fast, and smooth from my small useHad no qualms with the “square logo” version. So if I leave my desk, I let it time out and when I come back and log in again, the apps are still open (I can see this in the RDS icon menu) but I can’t get the apps to pull up on the screen. Also, in version 8, I could toggle on my kepboard and see the box with the list of apps on my desktop easily, but with the new version - no. I used it often, using both Active Directory logins and local logins.
Modern Authentication enables Active Directory Authentication Library (ADAL)-based sign-in for Office client apps across different platforms. This enables sign-in features such as Multi-Factor Authentication (MFA), smart card, and certificate-based authentication.
Learn more about multi-factor authentication and certificate-based authentication.
Supported platforms
- Windows 10 Desktop
- Windows 10 Modern Apps
- Web browsers1
- Android2
- iOS
- macOS
For more information about platform support in Office 365, see System requirements for Office 365.
Supported clients
The latest versions of the following clients support modern authentication:
Access | Azure Portal | Company Portal | Delve | Dynamics 365 |
Edge | Excel | Flow | Forms | Kaizala |
Office.com | Office 365 Admin | Office Lens | OneDrive | OneNote |
Outlook | Planner | PowerApps | Power BI | PowerPoint |
Project | Publisher | Sharepoint | Skype for Business1 | StaffHub |
Sticky Notes | Stream | Sway | Teams | To Do |
Visio | Whiteboard1,2 | Word | Yammer | Yammer Notifier |
Supported PowerShell modules
Azure AD PowerShell | Exchange Online PowerShell | SharePoint Online PowerShell |
Note
1 Support for Whiteboard and Skype for Business on web app available soon.
2 Support for Whiteboard on Android available soon.
2 Support for Whiteboard on Android available soon.
See also
-->The Microsoft Authentication Library (MSAL) for macOS and iOS supports Single Sign-on (SSO) between macOS/iOS apps and browsers. This article covers the following SSO scenarios:
This type of SSO works between multiple apps distributed by the same Apple Developer. It provides silent SSO (that is, the user isn't prompted for credentials) by reading refresh tokens written by other apps from the keychain, and exchanging them for access tokens silently.
Microsoft provides apps, called brokers, that enable SSO between applications from different vendors as long as the mobile device is registered with Azure Active Directory (AAD). This type of SSO requires a broker application be installed on the user's device.
- SSO between MSAL and Safari
SSO is achieved through the ASWebAuthenticationSession class. It uses existing sign-in state from other apps and the Safari browser. It's not limited to apps distributed by the same Apple Developer, but it requires some user interaction.
If you use the default web view in your app to sign in users, you'll get automatic SSO between MSAL-based applications and Safari. To learn more about the web views that MSAL supports, visit Customize browsers and WebViews.
This type of SSO is currently not available on macOS. MSAL on macOS only supports WKWebView which doesn't have SSO support with Safari.
- Silent SSO between ADAL and MSAL macOS/iOS apps
MSAL Objective-C supports migration and SSO with ADAL Objective-C-based apps. The apps must be distributed by the same Apple Developer.
See SSO between ADAL and MSAL apps on macOS and iOS for instructions for cross-app SSO between ADAL and MSAL-based apps.
Silent SSO between apps
MSAL supports SSO sharing through iOS keychain access groups.
To enable SSO across your applications, you'll need to do the following steps, which are explained in more detail below:
- Ensure that all your applications use the same Client ID or Application ID.
- Ensure that all of your applications share the same signing certificate from Apple so that you can share keychains.
- Request the same keychain entitlement for each of your applications.
- Tell the MSAL SDKs about the shared keychain you want us to use if it's different from the default one.
Use the same Client ID and Application ID
For the Microsoft identity platform to know which applications can share tokens, those applications need to share the same Client ID or Application ID. This is the unique identifier that was provided to you when you registered your first application in the portal.
The way the Microsoft identity platform tells apps that use the same Application ID apart is by their Redirect URIs. Each application can have multiple Redirect URIs registered in the onboarding portal. Each app in your suite will have a different redirect URI. For example:
App1 Redirect URI:
App2 Redirect URI:
App3 Redirect URI:
msauth.com.contoso.mytestapp1://auth
App2 Redirect URI:
msauth.com.contoso.mytestapp2://auth
App3 Redirect URI:
msauth.com.contoso.mytestapp3://auth
Important
The format of redirect uris must be compatible with the format MSAL supports, which is documented in MSAL Redirect URI format requirements.
Setup keychain sharing between applications
Microsoft Authenticator For Windows 10
Refer to Apple's Adding Capabilities article to enable keychain sharing. What is important is that you decide what you want your keychain to be called and add that capability to all of your applications that will be involved in SSO.
When you have the entitlements set up correctly, you'll see a
entitlements.plist
file in your project directory that contains something like this example:Add a new keychain group
Add a new keychain group to your project Capabilities. The keychain group should be:
com.microsoft.adalcache
on iOScom.microsoft.identity.universalstorage
on macOS.
For more information, see keychain groups.
Configure the application object
Once you have the keychain entitlement enabled in each of your applications, and you're ready to use SSO, configure
MSALPublicClientApplication
with your keychain access group as in the following example:Objective-C:
Swift:
Warning
When you share a keychain across your applications, any application can delete users or even all of the tokens across your application.This is particularly impactful if you have applications that rely on tokens to do background work.Sharing a keychain means that you must be very careful when your app uses Microsoft identity SDK remove operations.
That's it! The Microsoft identity SDK will now share credentials across all your applications. The account list will also be shared across application instances. Microsoft office update mac 2018.
SSO through Authentication broker on iOS
MSAL provides support for brokered authentication with Microsoft Authenticator. Microsoft Authenticator provides SSO for AAD registered devices, and also helps your application follow Conditional Access policies.
The following steps are how you enable SSO using an authentication broker for your app:
- Register a broker compatible Redirect URI format for the application in your app's Info.plist. The broker compatible Redirect URI format is
msauth.<app.bundle.id>://auth
. Replace `<app.bundle.id>`` with your application's bundle ID. For example: - Add following schemes to your app's Info.plist under
LSApplicationQueriesSchemes
: - Add the following to your
AppDelegate.m
file to handle callbacks:Objective-C:Swift:
If you are using Xcode 11, you should place MSAL callback into the
SceneDelegate
file instead.If you support both UISceneDelegate and UIApplicationDelegate for compatibility with older iOS, MSAL callback would need to be placed into both files.Objective-C:
Swift:
Next steps
How To Disable Microsoft Authenticator
Learn more about Authentication flows and application scenarios