Merge pull request #250941 from MicrosoftGuyJFlo/UpdateInclude

[Microsoft Entra] Update include

Author: v-dirichards

articles/global-secure-access/how-to-compliant-network.md

@@ -82,7 +82,7 @@ After administrators confirm the policy settings using [report-only mode](/azure
 
 ### User exclusions
 
-[!INCLUDE [active-directory-policy-exclusions](../../includes/active-directory-policy-exclude-user.md)]
+[!INCLUDE [active-directory-policy-exclusions](./includes/conditional-access-recommended-exclusions.md)]
 
 ## Try your compliant network policy
 

articles/global-secure-access/how-to-target-resource-microsoft-365-profile.md

@@ -52,7 +52,7 @@ After administrators confirm the policy settings using [report-only mode](/azure
 
 ### User exclusions
 
-[!INCLUDE [active-directory-policy-exclusions](../../includes/active-directory-policy-exclude-user.md)]
+[!INCLUDE [active-directory-policy-exclusions](./includes/conditional-access-recommended-exclusions.md)]
 
 ## Next steps
 

articles/global-secure-access/how-to-target-resource-private-access-apps.md

@@ -67,7 +67,7 @@ After administrators confirm the policy settings using [report-only mode](/azure
 
 ### User exclusions
 
-[!INCLUDE [active-directory-policy-exclusions](../../includes/active-directory-policy-exclude-user.md)]
+[!INCLUDE [active-directory-policy-exclusions](./includes/conditional-access-recommended-exclusions.md)]
 
 ## Next steps
 

articles/global-secure-access/includes/conditional-access-recommended-exclusions.md

@@ -0,0 +1,16 @@
+---
+ms.service: active-directory
+ms.subservice: conditional-access
+ms.topic: include
+ms.date: 09/11/2023
+
+ms.author: joflore
+author: MicrosoftGuyJFlo
+manager: amycolannino
+---
+Conditional Access policies are powerful tools, we recommend excluding the following accounts from your policies:
+
+- **Emergency access** or **break-glass** accounts to prevent tenant-wide account lockout. In the unlikely scenario all administrators are locked out of your tenant, your emergency-access administrative account can be used to log into the tenant to take steps to recover access.
+   - More information can be found in the article, [Manage emergency access accounts in Azure AD](/azure/active-directory/roles/security-emergency-access).
+- **Service accounts** and **service principals**, such as the Azure AD Connect Sync Account. Service accounts are non-interactive accounts that aren't tied to any particular user. They're normally used by back-end services allowing programmatic access to applications, but are also used to sign in to systems for administrative purposes. Service accounts like these should be excluded since MFA can't be completed programmatically. Calls made by service principals won't be blocked by Conditional Access policies scoped to users. Use Conditional Access for workload identities to define policies targeting service principals.
+   - If your organization has these accounts in use in scripts or code, consider replacing them with [managed identities](/azure/active-directory/managed-identities-azure-resources/overview). As a temporary workaround, you can exclude these specific accounts from the baseline policy.