APPLIES TO: Business Central 2025 release wave 2 (v27) and earlier. For later versions, this setup isn't needed. Learn more in Save business contacts to Microsoft Outlook.
Important
This legacy integration uses Exchange Web Services (EWS). Exchange Online starts disabling EWS in October 2026 and fully disables it in April 2027. Configuring OAuth doesn't prevent the EWS retirement from affecting contact synchronization. Learn more in Deprecation of Exchange Web Services in Exchange Online. For Business Central version 28 and later, use Save business contacts to Microsoft Outlook.
In this article, you learn how to set up Business Central on-premises to synchronize contacts in Business Central with contacts in Outlook. Learn more in Synchronize contacts in Business Central with contacts in Microsoft Outlook.
Authentication requirements for legacy contact sync
Contact synchronization requires using the OAuth 2.0 protocol for authentication with Exchange Online. Previously, basic authentication was also supported, but it's been deprecated and is no longer supported with Exchange Online. Learn more in Deprecation of Basic authentication in Exchange Online. The following steps configure OAuth authentication for the legacy integration.
Prerequisites for legacy contact sync
- Exchange Online, either a standalone version or through Microsoft 365 plan
- Access to the Microsoft Entra tenant used by Exchange Online
- Business Central users have a Microsoft 365 or Exchange Online email account, which is assigned to their accounts in Business Central. You can check this setting in the Microsoft 365 Authentication section of user profile in the Users list.
Set up contact sync
Complete the following steps to set up contact sync. If you're running Business Central Spring 2019 (v.14), you'll have to do an extra step that either modifies application code or sets up a connection to Power BI.
Register an app for Exchange Online API in your Microsoft Entra tenant.
In this step, you add a registered app in the Microsoft Entra tenant of your Microsoft 365 or Exchange Online plan. Like other Azure services that work with Business Central, Exchange Online requires a registered app in Microsoft Entra ID. The registered app provides authentication and authorization services between Business Central and Exchange Online.
Learn more in Register an application in Microsoft Entra ID in the developer and IT pro help. As you go through the instructions, remember the following points:
If you've already registered an application as part of an integration with another Microsoft product, such as Power BI, then reuse that registered app. In this case, you'll just have to set up the app with the Office 365 Exchange Online permissions described in the next bullet.
Configure the registered app with the following delegated permissions to the Office 365 Exchange Online API:
- Contacts.ReadWrite
- EWS.AccessAsUser.All
For Business Central version 14, do one of the following tasks:
Modify page 6700 by changing
FALSEtoTRUEin the following line of code in theOnOpenPagetrigger:PasswordRequired := AzureADMgt.GetAccessToken(AzureADMgt.GetO365Resource,AzureADMgt.GetO365ResourceName,TRUE) = '';Create a new page with the following code in the
OnOpenPagetrigger:PasswordRequired := AzureADMgt.GetAccessToken(AzureADMgt.GetO365Resource,AzureADMgt.GetO365ResourceName,TRUE) = '';Set up Power BI by following the instructions at Set up Business Central on-premises for Power BI integration.
After the solution you choose is in place, ask users to either run the new/modified page or connect to Power BI. They'll only need to do this step once.
Related information
Synchronize Contacts in Business Central with Contacts in Microsoft Outlook