{"title":"Set up the add-ins for Outlook in Business Central on-premises","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/setting-up-office-add-ins-outlook-inbox/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/setting-up-office-add-ins-outlook-inbox, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/setting-up-office-add-ins-outlook-inbox","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn how to configure your Business Central on-premises solution so that users can work with Business Central data in Outlook.","date":"2026-03-16","meta":{"topic":"how-to"},"outline":[{"level":1,"title":"Set up the add-ins for Outlook in Business Central on-premises","slug":"set-up-the-add-ins-for-outlook-in-business-central-on-premises","at":0,"chars":20431},{"level":2,"title":"Overview","slug":"overview","at":938,"chars":3138},{"level":3,"title":"About the add-in","slug":"about-the-add-in","at":950,"chars":975},{"level":3,"title":"About deployment","slug":"about-deployment","at":1925,"chars":977},{"level":3,"title":"Mail server","slug":"mail-server","at":2902,"chars":329},{"level":3,"title":"Authentication and authorization","slug":"authentication-and-authorization","at":3231,"chars":845},{"level":4,"title":"Exchange Online<#tab/exchangeonline>","slug":"exchange-onlinetabexchangeonline","at":3390,"chars":462},{"level":4,"title":"Exchange Server<#tab/exchangeserver>","slug":"exchange-servertabexchangeserver","at":3852,"chars":224},{"level":2,"title":"Prepare for deployment","slug":"prepare-for-deployment","at":4076,"chars":11213},{"level":3,"title":"Deploying to Exchange Online<#tab/m356>","slug":"deploying-to-exchange-onlinetabm356","at":4224,"chars":2691},{"level":3,"title":"Deploying to Exchange Server<#tab/exchange>","slug":"deploying-to-exchange-servertabexchange","at":6915,"chars":1172},{"level":3,"title":"Register an app that connects Outlook and Business Central","slug":"register-an-app-that-connects-outlook-and-business-central","at":8087,"chars":2346},{"level":4,"title":"Permissions for Exchange Online<#tab/exchange-onl-perms>","slug":"permissions-for-exchange-onlinetabexchange-onl-perms","at":9503,"chars":544},{"level":4,"title":"Permissions for Exchange Server<#tab/exchange-srv-perms>","slug":"permissions-for-exchange-servertabexchange-srv-perms","at":10047,"chars":386},{"level":3,"title":"Configure the Business Central server instance to work with add-ins","slug":"configure-the-business-central-server-instance-to-work-with-add-ins","at":10433,"chars":3165},{"level":3,"title":"Configure the Business Central web server instance to work with Exchange Online","slug":"configure-the-business-central-web-server-instance-to-work-with-exchange-online","at":13598,"chars":1691},{"level":2,"title":"Centralized Deployment","slug":"centralized-deployment","at":15289,"chars":2690},{"level":2,"title":"Automated individual deployment","slug":"automated-individual-deployment","at":17979,"chars":1375},{"level":3,"title":"Register an application in Microsoft Entra ID","slug":"register-an-application-in-microsoft-entra-id","at":18639,"chars":476},{"level":3,"title":"Get the add-in (users)","slug":"get-the-add-in-users","at":19115,"chars":239},{"level":2,"title":"Manual individual deployment","slug":"manual-individual-deployment","at":19354,"chars":648},{"level":3,"title":"Get the add-in (users)","slug":"get-the-add-in-users-1","at":19763,"chars":239},{"level":2,"title":"Related information","slug":"related-information","at":20002,"chars":429}],"text":"# Set up the add-ins for Outlook in Business Central on-premises\n> APPLIES TO: Business Central on-premises. For Business Central online, learn more in Get the add-in for Outlook</admin-outlook>\nIf your organization uses Exchange Server or Exchange Online (alone or as part of a Microsoft 365 subscription), Business Central on-premises supports integration with Outlook that enables users to complete Business Central business tasks from their Outlook inbox. As the admin, you can configure Business Central so that users can connect to Business Central data from Outlook.\n> IMPORTANT\n> From February 1, 2025, Microsoft Exchange Online requires all Outlook add-ins to use Nested App Authentication (NAA). If you have an existing setup for the Outlook add-in, you have to modify it to ensure it continues to work. See Modify existing Outlook add-in setup to support Nested App Authentication (NAA)<outlook-addins-setup-naa-modification>.\n## Overview\n### About the add-in\nBusiness Central add-in for Outlook consists of two add-ins:\n Contact Insights\n  The add-in provides users with Business Central customer or vendor information in Outlook emails and calendar appointments. It also enables users to create and send Business Central business documents, such sales quotes and invoices to a contact. To support these tasks, the add-in adds actions to the Outlook ribbon, in the Business Central group.\n Document View\n  When a business document is sent as an email, this add-in provides a direct link from email to the actual business document in Business Central.\nEach add-in is provided as an XML manifest file, which must be installed in Outlook client of any user that wants this functionality. These files describe how to activate the add-ins and connect to Business Central when they're used in Outlook.\nLearn more about using the add-ins in Using Business Central as your Business Inbox in Outlook</work-outlook-addin>.\n### About deployment\nThere are different options for deploying the add-ins. The option you choose depends on your organization's security policies, the Business Central environment, and how much control over installing the add-in you want to give users. For example, you can install the add-ins automatically for all users in your organization or targeted users only. Or, you can allow users to install the add-ins themselves. Learn more in the following sections of this article:\n #centralized-deployment\n #automated-individual-deployment\n #manual-individual-deployment\n> IMPORTANT\n> Working with multiple environments? The Business Central add-in for Outlook works with a single Business Central environment. When installed, the environment name is included in the add-in's manifest. With this configuration, the add-in only connects to the environment it was installed from. To use the add-in with a different environment, open the environment and install the add-in again.\n### Mail server\nThe add-in deployment works with Exchange Online, Exchange Online as part of Microsoft 365, and Exchange Server 2019. The add-in uses Exchange Web Services (EWS) to access mailbox data from Exchange Server, while Microsoft Entra Identity Provider and Microsoft Graph are used to access data from Exchange Online.\n### Authentication and authorization\nThe authentication and authorization that can be used depends on whether you're using Exchange Online or Exchange Server.\n#### Exchange Online<#tab/exchangeonline>\nTo use Exchange Online, configure Business Central to use Microsoft Entra authentication. See Configure Microsoft Entra authentication with OpenID Connect<authenticating-users-with-azure-ad-openid-connect>.\nThe Business Central add-in uses NAA (Nested App Authentication) for secure single sign-on with Outlook and Microsoft Entra ID accounts. It also supports multifactor authentication if configured in Microsoft 365.\n#### Exchange Server<#tab/exchangeserver>\nWith Exchange Server, EWS and Autodiscover try to find the local Exchange Server. Business Central can be configured to use either NavUserPassword or Microsoft Entra authentication.\n## Prepare for deployment\nThe steps to prepare for deploying the add-in depend on whether you plan to deploy to Exchange Online or Exchange Server.\n### Deploying to Exchange Online<#tab/m356>\n1. Prepare Microsoft 365\n  Assign users a Microsoft 365 license.\n  Make sure your Microsoft 365 account has at least the Exchange Administrator role.\n1. Set up Business Central for Microsoft Entra authentication.\n See Configure Microsoft Entra authentication with OpenID Connect<authenticating-users-with-azure-ad-openid-connect>.\n In the app registration, expose the Business Central API with a scope requiring admin and user consent:\n 1. Sign in to Microsoft Entra admin center<https://entra.microsoft.com> and open the app registration.\n 1. Select Expose an API.\n 1. If there's no value for Application ID URI, select Add > Save. Make note of the Application ID URI for later.\n 1. On the Expose an API page, select Add a scope and configure these settings:\n  |Setting|Value|Example|\n  |-|-|-|\n  |Scope name|Specify a meaningful name for a permission scope.|BusinessCentralOnPrem.Access|\n  |Consent|Choose Admins and users.||\n  |Admin consent display name|Specify a meaningful name for admin consent.|Access Business Central as the signed-in user|\n  |Admin consent description|Specify a meaningful description.|Business Central is a business management solution that helps organizations work smarter, adapt faster, and perform better.|\n  |User consent display name|Specify a meaningful name for user consent.|Have full access to Business Central|\n  |User consent description|Specify a meaningful description.|Allow the application full access to Dynamics 365 on your behalf.|\n 1. Make a note of the scope's name on the Expose an API page and app registration's display name on the Overview page. You might need this information later.\n See Configure an application to expose a web API<https://learn.microsoft.com/entra/identity-platform/quickstart-configure-app-expose-web-apis#add-a-scope>.\n1. Configure Business Central Web Server to use SSL (https).\n See Configure SSL to secure the connection to web client<../deployment/configure-ssl-web-client-connection>.\n1. Configure the Business Central Server instance to work with the Office Add-ins.\n See #configure-the-business-central-server-instance-to-work-with-add-ins.\n1. Register an application in Microsoft Entra ID for connecting Outlook and Business Central\n See #register-an-app-that-connects-outlook-and-business-central.\n1. Configure the Business Central web server instance to work with Exchange Online\n See #configure-the-business-central-web-server-instance-to-work-with-exchange-online.\n1. Set the authentication email on user accounts to the user's Microsoft 365 email address.\n See Create Users According to Licenses</ui-how-users-permissions> in the business functionality help.\n### Deploying to Exchange Server<#tab/exchange>\n1. Prepare Exchange Server\n  Enable access to EWS. See https://learn.microsoft.com/exchange/client-developer/exchange-web-services/how-to-control-access-to-ews-in-exchange\n  Make sure your Exchange account has the Organization Management role or the Org Apps admin role\n1. Set up Business Central for Microsoft Entra authentication or NavUserPassword.\n See Authenticating users with Microsoft Entra ID<authenticating-users-with-azure-ad-openid-connect> or authenticating-users-with-navuserpassword\n1. Configure Business Central Web Server to use SSL (https).\n See Configure SSL to Secure the Connection to Web Client<../deployment/configure-ssl-web-client-connection>.\n1. Configure the Business Central Server instance to work with the Office Add-ins.\n See Configure the server instance to work with the Office Add-ins<#configure-the-business-central-server-instance-to-work-with-add-ins>\n1. Register an application in Microsoft Entra ID for connecting Outlook and Business Central (optional)\n This step only applies when using Microsoft Entra authentication. See #register-an-app-that-connects-outlook-and-business-central\n### Register an app that connects Outlook and Business Central\n> APPLIES TO: Connecting to Exchange Online and Exchange Server\n1. Sign in to the Microsoft Entra admin center<https://entra.microsoft.com>.\n1. Create a new app registration on your tenant with the following settings:\n |Setting|Value|Example|\n |-|-|-|\n |Name|Specify a meaningful name for the app|Business Central on-premises Outlook Add-in Connector|\n |Supported account types|Set to Accounts in the organizational directory only (Single tenant). If you need multitenant access, select Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant)||\n |Redirect URI - Select a platform box|Single-Page application (SPA)||\n |Redirect URI - URI box|Enter the base URL for your Business Central on-premises web client.<br/><br /> For Exchange Online, the URL has the format:<br />`brk-multihub://<web server hostname>` <br /><br />For Exchange Server, the URL has the format:<br />`https://<web server hostname>`|Exchange Online:<br />`brk-multihub://MyBCWebServer`<br /><br />Exchange Server:<br />`https://MyBCWebServer`|\n See register-app-azure#register-an-application-in-microsoft-entra-id.\n1. Add the following API permissions the new registered app.\n With the new registered app open, select API permissions > Add a permission. The required permissions are different for connecting to Exchange Online and Exchange Server:\n#### Permissions for Exchange Online<#tab/exchange-onl-perms>\n In the Microsoft APIs tab, select Microsoft Graph, and Delegated permissions. From the list of available permissions, select User.Read, Mail.ReadWrite, and Calendars.Read.\n In the APIs my organization uses tab, search for the name of the registered app that authenticates Microsoft Entra ID users with Business Central and add the scope you created earlier. This app isn't the app you registered to connect Outlook and Business Central.\nSelect Add permissions to save the changes.\n#### Permissions for Exchange Server<#tab/exchange-srv-perms>\nIn the Microsoft APIs tab, select Microsoft Graph > Delegated permissions. From the list of available permissions, select EWS.AccessAsUser.All. Select Add permissions to save changes.\nSee https://learn.microsoft.com/azure/active-directory/develop/quickstart-configure-app-access-web-apis#add-permissions-to-access-web-apis.\n### Configure the Business Central server instance to work with add-ins\n> APPLIES TO: Connecting to Exchange Online and Exchange Server\nFor this task, use the Set-NAVServerConfiguration cmdlet<https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/set-navserverconfiguration> cmdlet in the Business Central Administration Shell.\n1. Start the Business Central Administration Shell as an administrator.\n1. Run the Set-NAVServerConfiguration cmdlet to set the PublicWebBaseUrl key to the base URL of the Business Central Web client.\n The base URL is the public URL that Outlook clients use to access Business Central. The base URL is the root portion of all URLs that are used to access pages in the web client. It must have the format `https://[hostname:port]/[instance]`, such as `https://MyBCWebServer:443/BC280`.\n ```powershell\n Set-NavServerConfiguration -ServerInstance BC280 -KeyName PublicWebBaseUrl -Keyvalue \"https://MyBCWebServer:443/BC280\"\n ```\n1. Run the Set-NAVServerConfiguration cmdlet to set the ValidAudiences key to the host name of the Business Central Web client. The value is the web client base URL without the port number and server instance, like `https://MyBCWebServer`.\n ```powershell\n Set-NavServerConfiguration -ServerInstance BC280 -KeyName ValidAudiences -Keyvalue \"https://MyBCWebServer\"\n ```\n If you have a multitenant deployment with different host names for tenants, like `https://tenant1.cronusinternational.com`, register each host name as a valid audience. You can do this task in two ways:\n  On the server-level, use the Set-NavServerConfiguration cmdlet to add each host name to Valid Audiences setting of the Business Central Server instance. separate each host name with a semi-colon.\n   ```powershell\n   Set-NavServerConfiguration -ServerInstance BC -KeyName ValidAudiences -Keyvalue \"<host name 1>;<host name 1>\"\n   ```\n  On the tenant-level, add the host names to the Valid Audiences setting when you mount the tenant by using the Mount-NAVTenant cmdlet<https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/mount-navtenant>.\n   ```powershell\n   Mount-NavTenant -ServerInstance <BC server instance> -Tenant <tenant_ID> -ValidAudiences \"<host name 1>\"\n   ```\n> NOTE\n> If there's more than one host name, separate each host name with a semicolon. Specify the host names at the server level, tenant level, or both.\n1. (Optional) Run the `Set-NAVServerConfiguration` cmdlet to set the ExchangeAuthenticationMetadataLocation key.\n ```powershell\n Set-NavServerConfiguration -ServerInstance <BC server instance> -KeyName ExchangeAuthenticationMetadataLocation -Keyvalue <metadata document URL>\n ```\n This setting is used to confirm the identity of the signing authority when using Exchange authentication. In part, the value includes the URL of the Exchange mail server. The field accepts a wild-card URL. So for example, if the URL of the Exchange mail server is `https://mail.cronus.com`, then you can set the field to `https://mail.cronus.com*`. The default value is `https://outlook.office365.com/`. Complete this step only if you want to use a value other than the default.\n### Configure the Business Central web server instance to work with Exchange Online\n> APPLIES TO: Connecting to Exchange Online\nThis task is only required when working with Exchange Online. To complete this task, you need the application (client) ID of the registered application used for Business Central authentication in Microsoft Entra.\nUse the https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/set-navwebserverinstanceconfiguration in the Business Central Administration Shell to configure the following web server instance settings:\nKeyName|KeyValue|Example\n-|-|-\nExchangeOnlineAppId|Use the Application (client) ID for the application you registered that connects Outlook and Business Central.|00001111-aaaa-2222-bbbb-3333cccc4444\nExchangeOnlineAppScope|Use the Scope from the application you registered that authenticates Microsoft Entra ID users with Business Central. The value has the format: \\<BC OnPrem app ID>\\/\\<scope\\>|11112222-bbbb-3333-cccc-4444dddd5555/BusinessCentralOnPrem.Access\nRun the cmdlet for each setting using the following syntax:\n```powershell\nSet-NAVWebServerInstanceConfiguration -ServerInstance <BC server instance> -Tenant <tenant_ID> -KeyName <KeyName> -KeyValue <KeyValue>\n```\nFor example:\n```powershell\nSet-NAVWebServerInstanceConfiguration -ServerInstance BC280 -Tenant default -KeyName ExchangeOnlineAppId -KeyValue \"00001111-aaaa-2222-bbbb-3333cccc4444\"\nSet-NAVWebServerInstanceConfiguration -ServerInstance BC280 -Tenant default -KeyName ExchangeOnlineAppScope -KeyValue \"11112222-bbbb-3333-cccc-4444dddd5555/BusinessCentralOnPrem.Access\"\n```\nRestart the web server instance when you're done.\n```powershell\niireset\n```\n## Centralized Deployment\nCentralized Deployment is a feature in Microsoft 365 admin center and Exchange admin center that lets you automatically install add-ins in users' Office apps, like Outlook. It's the recommended way for admins to deploy for Office add-ins to users and groups within your organization. See https://learn.microsoft.com/microsoft-365/admin/manage/centralized-deployment-faq.\nComplete the following steps:\n1. Verify that Centralized Deployment works for your organization.\n See Determine if Centralized Deployment of add-ins works for your organization<https://learn.microsoft.com/microsoft-365/admin/manage/centralized-deployment-of-add-ins>.\n1. In Business Central, choose the ![Lightbulb that opens the Tell Me feature.] icon, enter Assisted Setup, and then choose the related link.\n1. Choose Outlook Add-in Centralized Deployment > Next.\n1. In the Deploy column, select the check box for the add-ins that you want to deploy, then choose Download and Continue.\n A file named OutlookAddins.zip is downloaded to your device.\n1. On the Where do you want to deploy to? page, set Deploy Add-in to to either Microsoft 365 or Exchange Server, then choose Next.\n1. At this point, you're finished with the work you need to do in Business Central, so you can choose Done.\n> TIP\n> Before you choose Next, select the Go to Microsoft 365 (opens in a new window) or Learn more about the add-in for Outlook in Exchange Server link to open or get help on the admin center.\n1. Go the folder where the OutlookAddins.zip file was downloaded, and extract the Content Insights.xml and Document View.xml files from the .zip to a folder of your choice.\n See Zip and Unzip files and folders<https://support.microsoft.com/en-us/windows/zip-and-unzip-files-8d28fa72-f2f9-712f-67df-f80cf89fd4e5>.\n1. For Microsoft 365 deployment, sign in to the Microsoft 365 admin center<https://go.microsoft.com/fwlink/?linkid=2163967>. For Exchange Server deployment, sign in to Exchange admin center.\n1. Upload the add-in files as custom add-ins in the admin center you're working with:\n  For Microsoft 365 admin center, follow the steps at Deploy add-ins in the admin center<https://learn.microsoft.com/microsoft-365/admin/manage/manage-deployment-of-add-ins>.\n  For Exchange admin center, follow the steps at Install or remove add-ins for Outlook for your Exchange organization<https://learn.microsoft.com/exchange/install-or-remove-outlook-add-ins-2013-help>.\n   This step assigns users and deploys the add-ins.\n> IMPORTANT\n> An add-in can take up to 24 hours before users see the add-in in Outlook app.\nAfter you finish, you can always change the deployment in admin center, like assigning more users.\n## Automated individual deployment\nWith this deployment option, users install the Business Central add-in for Outlook themselves. This option uses a registered application in Microsoft Entra ID with Exchange web service permission, so users don't have to upload the add-ins manually in Outlook. Users don't have to sign in to Business Central to use the add-ins, because authentication against Exchange or Microsoft 365 is done using an authentication token.\nIf you prepared for deployment as described earlier, as an admin, the only remaining task is to set up an application registration in Microsoft Entra ID. Then, users can install the add-in in Outlook.\n### Register an application in Microsoft Entra ID\nIn the Azure portal, add an application registration for Business Central in your Microsoft Entra tenant. Give the registered app delegated permission to Exchange web service (EWS). After you add the registered app in Microsoft Entra ID, set up Business Central to use it by using the Set up your Microsoft Entra accounts assisted setup.\nSee Registering Business Central on-premises in Microsoft Entra ID<register-app-azure>.\n### Get the add-in (users)\nAfter you complete the Business Central setup, users deploy the add-in by using Get Outlook Add-in assisted setup in Business Central. See Install the Business Central Add-in for Outlook</admin-outlook#install>.\n## Manual individual deployment\nWith this deployment option, users install the Business Central add-in for Outlook for themselves only. Unlike the individual acquisition (automated) deployment option, users have to download the add-in files from Business Central, then manually add them in Outlook. If you prepared your deployment as described earlier, the only step remaining is for users to get the add-in.\n### Get the add-in (users)\nAfter you complete the Business Central setup, users deploy the add-in by using Get Outlook Add-in assisted setup in Business Central. See Install the Business Central Add-in for Outlook</admin-outlook#install>.\n## Related information\nDeploying Business Central<../deployment/deployment>\nUsing Business Central as your Business Inbox in Outlook</admin-outlook?toc=/dynamics365/business-central/dev-itpro/toc.json>\nmount-dismount-tenant\nConfiguring Business Central Web Server to Accept Host Names for Tenants<configure-web-server-to-accept-host-names-for-tenants>\nhttps://learn.microsoft.com/dynamics365/business-central/ui-outlook-addin-faq"}