{"title":"Business Central security (online deployment)","url":"https://jonas-paprotka.de/docs/dev-itpro/security/security-online/","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/security/security-online, 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/security/security-online","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 about the main aspects of security in your online deployment of Dynamics 365 Business Central.","date":"2026-01-14","meta":{"topic":"article"},"outline":[{"level":1,"title":"Business Central security (online deployment)","slug":"business-central-security-online-deployment","at":0,"chars":11832},{"level":2,"title":"Authentication and identity","slug":"authentication-and-identity","at":397,"chars":2662},{"level":3,"title":"Configure Microsoft Entra ID to allow or deny authentications","slug":"configure-microsoft-entra-id-to-allow-or-deny-authentications","at":1356,"chars":864},{"level":3,"title":"Require multifactor authentication (MFA)","slug":"require-multifactor-authentication-mfa","at":2220,"chars":298},{"level":3,"title":"Monitor sign-in attempts to detect threats","slug":"monitor-sign-in-attempts-to-detect-threats","at":2518,"chars":541},{"level":2,"title":"Access control","slug":"access-control","at":3059,"chars":931},{"level":3,"title":"Per-environment access restrictions","slug":"per-environment-access-restrictions","at":3077,"chars":661},{"level":3,"title":"Manage environment access","slug":"manage-environment-access","at":3738,"chars":252},{"level":2,"title":"Privileged access management","slug":"privileged-access-management","at":3990,"chars":1470},{"level":3,"title":"Use Privileged Identity Management","slug":"use-privileged-identity-management","at":4022,"chars":691},{"level":3,"title":"Use secure admin devices","slug":"use-secure-admin-devices","at":4713,"chars":397},{"level":3,"title":"Enforce separation of duties for sensitive operations","slug":"enforce-separation-of-duties-for-sensitive-operations","at":5110,"chars":350},{"level":2,"title":"Data protection","slug":"data-protection","at":5460,"chars":4851},{"level":3,"title":"Data isolation and encryption","slug":"data-isolation-and-encryption","at":5479,"chars":634},{"level":3,"title":"Customer-managed encryption key","slug":"customer-managed-encryption-key","at":6113,"chars":2737},{"level":4,"title":"Customer-managed encryption key for copied or restored environments","slug":"customer-managed-encryption-key-for-copied-or-restored-environments","at":8325,"chars":525},{"level":3,"title":"Customer Lockbox","slug":"customer-lockbox","at":8850,"chars":1461},{"level":2,"title":"Service integration","slug":"service-integration","at":10311,"chars":438},{"level":2,"title":"Auditing administrative actions","slug":"auditing-administrative-actions","at":10749,"chars":778},{"level":2,"title":"Related information","slug":"related-information","at":11527,"chars":305}],"text":"# Business Central security (online deployment)\nThis section helps you understand and improve the security of your Business Central tenant. In the links below you find information, guidance, and recommended practices related to authentication, data encryption, and safely integrating with other services. You can also find information on Business Central certifications and regulatory compliance.\n## Authentication and identity\nBusiness Central uses Microsoft Entra ID as the authentication method, which is automatically set up and managed for you.\n> TIP\n> Before Business Central online logs authorization attempts to telemetry, a successful authentication (sign-in) must happen against Microsoft Entra ID. With the information in the Microsoft Entra sign-in log, you can figure out what happened if a user sign-in failed. See Analyze sign-ins with the Microsoft Entra sign-in log<https://learn.microsoft.com/entra/identity/monitoring-health/quickstart-analyze-sign-in>.\n> If you want to track, monitor, or alert on successful and failed sign-in attempts against Microsoft Entra ID, configure integration to Azure Monitor on Microsoft Entra and analyze further with KQL. See Integrate Microsoft Entra logs with Azure Monitor<https://learn.microsoft.com/entra/identity/monitoring-health/howto-access-activity-logs#integrate-logs-with-azure-monitor-logs>.\n### Configure Microsoft Entra ID to allow or deny authentications\nIt's possible to configure Microsoft Entra ID to allow or deny authentications to Business Central only if certain extra conditions are met using Conditional Access to further improve security of your environments. Administrators can apply Microsoft Entra ID Conditional Access policies to enforce conditions like MFA on every sign in, restrict sign-ins to trusted locations or compliant devices, for Business Central. For example, you might apply the 'Require MFA for all users' policy template to Business Central. See Conditional Access<https://learn.microsoft.com/entra/identity/conditional-access/overview>.\n> NOTE\n> Introducing new CA policies prompts users to reauthenticate; plan such changes to minimize disruption (for example, inform users, update background job credentials if needed).\n### Require multifactor authentication (MFA)\nAlways require MFA for Business Central sign-in. We recommend using modern authentication options (such as Authenticator apps or FIDO2 keys) and disabling basic auth methods. See Setting up Multifactor Authentication (MFA)l<multifactor-authentication>.\n### Monitor sign-in attempts to detect threats\nAdmins can monitor failed sign-in attempts to Business Central through Microsoft Entra sign-in logs<https://learn.microsoft.com/entra/identity/conditional-access/troubleshoot-conditional-access#microsoft-entra-sign-in-events> or Business Central authorization trace telemetry<../administration/telemetry-authorization-trace>. Frequent authentication failures might indicate an attacker trying to guess passwords or an integration using incorrect credentials, so active monitoring is important.\n## Access control\n### Per-environment access restrictions\nBusiness Central allows environment-specific access control for partners. An internal administrator can configure an allowlist of external Microsoft Entra tenant IDs (such as partners or ISVs) that are permitted to access a given environment (via Delegated Admin or OAuth apps). This practice adds an extra layer on top of tenant-wide delegation (GDAP) and app consent - if an environment is restricted, only the specified partner tenants can gain access with their accounts or apps. You can configure up to 10 allowed tenants per environment in the Admin Center. See ../administration/tenant-admin-center-manage-access.\n### Manage environment access\nAccess can be controlled per Business Central environment for internal users, delegated administrators, and multitenant applications. See Manage Access to Environments<../administration/tenant-admin-center-manage-access>.\n## Privileged access management\n### Use Privileged Identity Management\nConsider using Microsoft Entra ID Privileged Identity Management (PIM) for Business Central administrators. PIM ensures that high-privilege roles (like Dynamics 365 Business Central Administrator) are only activated when needed, reducing the risk of always-on admin accounts. This incorporation emphasizes best practice for cloud admins: don't leave admin privileges permanent - require on-demand activation. See What is Microsoft Entra Privileged Identity Management?<https://learn.microsoft.com/entra/id-governance/privileged-identity-management/pim-configure>.\nIn addition to using PIM, physical device security is crucial for administrator access.\n### Use secure admin devices\nPerform Business Central administration from a highly secure, isolated workstation. For example, have a dedicated PC (or Azure Virtual Desktop/Cloud PC) for admin use only, with hardened configuration (up-to-date OS, limited software, full disk encryption, and mandatory MFA). Avoid doing daily work or general browsing on the same machine used for privileged access.\n### Enforce separation of duties for sensitive operations\nIn Business Central, use built-in features like Approval Workflows</across-set-up-workflows> to ensure critical transactions (like large payments, purchase orders, or journal postings) require approval by a second person. This practice reduces the risk of fraud or mistakes by a single user.\n## Data protection\n### Data isolation and encryption\nData belonging to a single tenant is stored in an isolated database and is never mixed with data from other tenants. This setup ensures complete isolation of data in day-to-day use and in backup/restore scenarios. Furthermore, Business Central uses encryption to help protect tenant data in the following ways:\n Data at rest is encrypted by using Transparent Data Encryption (TDE) and backup encryption. See Data Encryption at Rest<transparent-data-encryption>.\n Data backups are always encrypted.\n All network traffic inside the service is encrypted by using industry-standard encryption protocols.\n### Customer-managed encryption key\nAll customer data in Business Central is encrypted at-rest with strong Microsoft-managed encryption keys. Microsoft stores and manages the database encryption key for all your data so you don't have to. However, Business Central provides customer-managed encryption key (CMK) functionality to self-manage the database encryption key associated with your environment. This capability allows you to rotate or swap the encryption key on demand. It also allows you to prevent Microsoft's access to your customer data when you revoke the key access to our services at any time.\nThe customer-managed encryption key used to encrypt your customer data in Business Central at rest is administered in the Power Platform Admin Center and requires the Business Central environment to be ../administration/tenant-admin-center-environments#linked-power-platform-environment. If the Business Central environment is linked to a Power Platform environment to which a customer-managed encryption key is applied, this key also automatically applies to the linked Business Central environment. Unlinking an environment encrypted with a customer-managed encryption key or removing the customer-managed encryption key from the linked Power Platform environment automatically reverts encryption of the Business Central environment to the Microsoft-managed encryption key. Learn more about administering customer-managed encryption keys in Power Platform admin center documentation<https://learn.microsoft.com/power-platform/admin/customer-managed-key>.\n> IMPORTANT\n> Business Central and Power Platform environments can currently be linked across Azure geographies as Power Platform environments are created for Macro Region Geographies<https://learn.microsoft.com/power-platform/admin/macro-regions>. However, customer-managed encryption keys require the linked environments to reside in the same geography. If no Power Platform environment exists in the geography of your Business Central environment, purchase Microsoft 365 Advanced Data Residency<https://learn.microsoft.com/microsoft-365/enterprise/advanced-data-residency> to create a new Power Platform environment in the required geography.\n#### Customer-managed encryption key for copied or restored environments\nSometimes a new Business Central environment is created from an environment that's encrypted with a customer-managed encryption key using a copy or restore operation. In this case, the newly created environment is encrypted using the Microsoft-managed encryption key. To encrypt the newly created environment using a customer-managed encryption key, link it to a Power Platform environment that has the desired customer-managed encryption key applied.\n### Customer Lockbox\nMost of the operations, support, and troubleshooting performed by Microsoft personnel (including subprocessors) don't require access to customer data. Customer Lockbox provides an interface for the customers to review and approve (or reject) data access requests in rare occasions that require access to customer data. It's used in cases where a Microsoft engineer needs to access customer data, whether in response to a customer-initiated support ticket or a problem identified by Microsoft. Customer Lockbox approvals expire after 8 hours, so any needed support access beyond that would require a new request.\nCustomer Lockbox for Business Central is administered in the Power Platform Admin Center and requires the Business Central environment to be ../administration/tenant-admin-center-environments#linked-power-platform-environment. Learn more about administering Customer Lockbox in the Power Platform Admin Center https://learn.microsoft.com/power-platform/admin/about-lockbox. If the Business Central environment is linked to a Power Platform for which Lockbox is enabled, Lockbox is also automatically enabled for the linked Business Central environment. Lockbox requests for the Business Central environment can only be approved or rejected in the Power Platform Admin Center by users with at least the https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#power-platform-administrator role.\n## Service integration\nWe recommend that you use encrypted network protocols to connect to the Power BI server and Business Central web services. Learn more in the following articles:\nConnect to Business Central with Power BI<https://learn.microsoft.com/power-bi/service-connect-to-microsoft-dynamics-nav>\nUsing Security Certificates with Business Central on-premises<../deployment/implement-security-certificates-production-environment>\n## Auditing administrative actions\nBusiness Central Online automatically logs various administrative and high-level events to your Microsoft Purview audit log, such as:\n Creating or deleting an environment\n Installing an app extension\n Changing a user's permissions or settings\n Changing tenant-level or system configurations\nBy default, audit logs are kept for 180 days or longer, if your organization purchased extended retention.\nAdmins can search Business Central audit events in the Microsoft Purview portal just as they would for Exchange or SharePoint audit data. You can also use PowerShell or the Graph API (Management Activity API) to retrieve and filter these logs programmatically for analysis.\nSee Auditing in Microsoft Purview<../auditing/audit-events-in-purview>\n## Related information\nMicrosoft Trust Center (what we do to make the service secure)<https://www.microsoft.com/trustcenter/security/default.aspx>\nMicrosoft Dynamics 365 Cloud Services Compliance<https://aka.ms/d365-compliance-list>\nsecurity-and-protection\nSecurity tips for business users<security-users>"}