πŸ“‹ Microsoft Entra Documentation Changes

Daily summary for changes since October 9th 2025, 7:59 PM PDT

Report generated on October 10th 2025, 7:59 PM PDT

πŸ“Š Summary

20
Total Commits
1
New Files
12
Modified Files
1
Deleted Files
9
Contributors

πŸ†• New Documentation Files

+22 lines added
Commit: [Secure Entra] Additions

πŸ“ Modified Documentation Files

Modified by John Flores on Oct 10, 2025 6:01 PM
πŸ“– View on learn.microsoft.com
+9 / -10 lines changed
Commit: Revise secure recommendations for guest access control
Changes:
Before
After
---
title: Allow/Deny lists of domains to restrict external collaboration are configured
ms.author: sarahlipsey
author: shlipsey3
ms.service: entra-id
ms.topic: include
ms.date: 07/07/2025
ms.custom: Identity-Secure-Recommendation
# sfipillar: Protect tenants and isolate production systems
# category: External collaboration
# risklevel: Medium
# userimpact: Medium
# implementationcost: Medium
---
Without configured domain allow/deny lists for external collaboration, organizations lack essential domain-level access controls that act as the frontline defense in their security model. Domain allow/deny lists operate at the tenant level and take precedence over Cross-Tenant Access Policies (XTAP), blocking invitations from domains on the deny list regardless of cross-tenant access settings. While XTAP enables granular controls for specific trusted tenants, domain restrictions are critical for preventing invitations from unknown or unverified domains that haven't been explicitly allowed.
 
Without these restrictions, internal users can invite external accounts from any domainβ€”including potentially compromised or attacker-controlled domains. Threat actors can register domains that appear legitimate to conduct social engineering attacks, tricking users into sending collaboration invitations that circumvent XTAP's targeted protections. Once granted access, these external guest accounts can be used for reconnaissance, mapping internal resources, user relationships, and collaboration patterns.
 
These invited accounts provide persistent access that appears legitimate in audit logs and security monitoring systems. Attackers can maintain a long-term presence to collect data, access shared resources, documents, and applications configured for external collaboration, and potentially exfiltrate data through authorized channels without triggering alerts.
 
---
title: Limit guest access to approved tenants
ms.author: joflore
author: MicrosoftGuyJFlo
ms.service: entra-id
ms.topic: include
ms.date: 10/10/2025
ms.custom: Identity-Secure-Recommendation
# sfipillar: Protect tenants and isolate production systems
# category: External collaboration
# risklevel: Medium
# userimpact: Medium
# implementationcost: High
---
Limiting guest access to a known and approved list of tenants helps to prevent threat actors from exploiting unrestricted guest access to establish initial access through compromised external accounts or by creating accounts in untrusted tenants. Threat actors who gain access through an unrestricted domain can discover internal resources, users, and applications to perform additional attacks.
 
Organizations should take inventory and configure an allowlist or blocklist to control B2B collaboration invitations from specific organizations. Without these controls, threat actors might use social engineering techniques to obtain invitations from legitimate internal users.
 
**Remediation action**
 
Modified by John Flores on Oct 10, 2025 1:47 PM
πŸ“– View on learn.microsoft.com
+4 / -1 lines changed
Commit: [Secure Entra] Additions
Changes:
Before
After
### All privileged role assignments are activated just in time and not permanently active
[!INCLUDE [21815](../includes/secure-recommendations/21815.md)]
 
### Privileged accounts have phishing-resistant methods registered
[!INCLUDE [21782](../includes/secure-recommendations/21782.md)]
 
### Privileged Microsoft Entra built-in roles are targeted with Conditional Access policies to enforce phishing-resistant methods
[!INCLUDE [21783](../includes/secure-recommendations/21783.md)]
 
 
 
### All privileged role assignments are activated just in time and not permanently active
[!INCLUDE [21815](../includes/secure-recommendations/21815.md)]
 
### Passkey authentication method enabled
[!INCLUDE [21815](../includes/secure-recommendations/21815.md)]
 
### Privileged accounts have phishing-resistant methods registered
[!INCLUDE [21839](../includes/secure-recommendations/21839.md)]
 
### Privileged Microsoft Entra built-in roles are targeted with Conditional Access policies to enforce phishing-resistant methods
[!INCLUDE [21783](../includes/secure-recommendations/21783.md)]
+2 / -2 lines changed
Commit: Fix typos and update date in hybrid identity docs
Changes:
Before
After
author: omondiatieno
ms.service: entra-id
ms.topic: Include
ms.date: 10/09/2025
ms.author: jomondi
ms.custom: Include file
---
4. At the top, switch **Object type** to **Group**.
5. Add a new attribute mapping.
- Mapping type: Direct
- Source attribute: distinguishedName (the on-prem group’s DN)
- Target attribute: `extension_<appIdWithoutHyphens>_GroupDN`
6. Save the schema to trigger a sync.
 
author: omondiatieno
ms.service: entra-id
ms.topic: Include
ms.date: 10/10/2025
ms.author: jomondi
ms.custom: Include file
---
4. At the top, switch **Object type** to **Group**.
5. Add a new attribute mapping.
- Mapping type: Direct
- Source attribute: distinguishedName (the on-premises group’s DN)
- Target attribute: `extension_<appIdWithoutHyphens>_GroupDN`
6. Save the schema to trigger a sync.
 
Modified by John Flores on Oct 10, 2025 5:17 PM
πŸ“– View on learn.microsoft.com
+1 / -2 lines changed
Commit: blocker fixes
Changes:
Before
After
---
Without Local Admin Password Solution (LAPS) deployed, threat actors exploit static local administrator passwords to establish initial access. After threat actors compromise a single device with a shared local administrator credential, they can move laterally across the environment and authenticate to other systems sharing the same password. Compromised local administrator access gives threat actors system-level privileges, letting them disable security controls, install persistent backdoors, exfiltrate sensitive data, and establish command and control channels.
 
The automated password rotation and centralized management of LAPS closes this security gap and adds controls to help manage who has access to these critical accounts. Without soultions like LAPS, you can't detect or respond to unauthorized use of local administrator accounts, giving threat actors extended dwell time to achieve their objectives while remaining undetected.
 
**Remediation action**
 
- [Configure Windows Local Administrator Password Solution](/entra/identity/devices/howto-manage-local-admin-passwords).
 
---
Without Local Admin Password Solution (LAPS) deployed, threat actors exploit static local administrator passwords to establish initial access. After threat actors compromise a single device with a shared local administrator credential, they can move laterally across the environment and authenticate to other systems sharing the same password. Compromised local administrator access gives threat actors system-level privileges, letting them disable security controls, install persistent backdoors, exfiltrate sensitive data, and establish command and control channels.
 
The automated password rotation and centralized management of LAPS closes this security gap and adds controls to help manage who has access to these critical accounts. Without solutions like LAPS, you can't detect or respond to unauthorized use of local administrator accounts, giving threat actors extended dwell time to achieve their objectives while remaining undetected.
 
**Remediation action**
 
- [Configure Windows Local Administrator Password Solution](/entra/identity/devices/howto-manage-local-admin-passwords).
 
Modified by John Flores on Oct 10, 2025 6:13 PM
πŸ“– View on learn.microsoft.com
+1 / -1 lines changed
Commit: WIP
Changes:
Before
After
| Check | Minimum required license |
|---|---|
| [Permissions to create new tenants are limited to the Tenant Creator role](zero-trust-protect-tenants.md#permissions-to-create-new-tenants-are-limited-to-the-tenant-creator-role) | Microsoft Entra ID Free |
| [Guest access limited to approved tenants](zero-trust-protect-tenants.md#allowdeny-lists-of-domains-to-restrict-external-collaboration-are-configured) | Microsoft Entra ID Free |
| [Guests are not assigned high privileged directory roles](zero-trust-protect-tenants.md#guests-are-not-assigned-high-privileged-directory-roles) | Microsoft Entra ID Free<br>Microsoft Entra ID P2 or Microsoft ID Governance for PIM |
| [Guests can't invite other guests](zero-trust-protect-tenants.md#guests-cant-invite-other-guests) | Microsoft Entra ID Free |
| [Guests have restricted access to directory objects](zero-trust-protect-tenants.md#guests-have-restricted-access-to-directory-objects) | Microsoft Entra ID Free |
| Check | Minimum required license |
|---|---|
| [Permissions to create new tenants are limited to the Tenant Creator role](zero-trust-protect-tenants.md#permissions-to-create-new-tenants-are-limited-to-the-tenant-creator-role) | Microsoft Entra ID Free |
| [Guest access is limited to approved tenants](zero-trust-protect-tenants.md#guest-access-is-limited-to-approved-tenants) | Microsoft Entra ID Free |
| [Guests are not assigned high privileged directory roles](zero-trust-protect-tenants.md#guests-are-not-assigned-high-privileged-directory-roles) | Microsoft Entra ID Free<br>Microsoft Entra ID P2 or Microsoft ID Governance for PIM |
| [Guests can't invite other guests](zero-trust-protect-tenants.md#guests-cant-invite-other-guests) | Microsoft Entra ID Free |
| [Guests have restricted access to directory objects](zero-trust-protect-tenants.md#guests-have-restricted-access-to-directory-objects) | Microsoft Entra ID Free |
Modified by John Flores on Oct 10, 2025 6:13 PM
πŸ“– View on learn.microsoft.com
+1 / -1 lines changed
Commit: WIP
Changes:
Before
After
### Protected actions are enabled for high-impact management tasks
[!INCLUDE [21831](../includes/secure-recommendations/21831.md)]
 
### Guest access limited to approved tenants
[!INCLUDE [21874](../includes/secure-recommendations/21874.md)]
 
### Guests are not assigned high privileged directory roles
### Protected actions are enabled for high-impact management tasks
[!INCLUDE [21831](../includes/secure-recommendations/21831.md)]
 
### Guest access is limited to approved tenants
[!INCLUDE [21874](../includes/secure-recommendations/21874.md)]
 
### Guests are not assigned high privileged directory roles
+1 / -1 lines changed
Commit: blocker fixes
Changes:
Before
After
[!INCLUDE [21869](../includes/secure-recommendations/21869.md)]
 
### Limit the maximum number of devices per user to 10
[!INCLUDE [21869](../includes/secure-recommendations/21869.md)]
 
### Conditional Access policies for Privileged Access Workstations are configured
[!INCLUDE [21830](../includes/secure-recommendations/21830.md)]
[!INCLUDE [21869](../includes/secure-recommendations/21869.md)]
 
### Limit the maximum number of devices per user to 10
[!INCLUDE [21837](../includes/secure-recommendations/21837.md)]
 
### Conditional Access policies for Privileged Access Workstations are configured
[!INCLUDE [21830](../includes/secure-recommendations/21830.md)]
Modified by John Flores on Oct 10, 2025 5:17 PM
πŸ“– View on learn.microsoft.com
+1 / -1 lines changed
Commit: blocker fixes
Changes:
Before
After
ms.topic: include
ms.date: 09/26/2025
ms.custom: Identity-Secure-Recommendation
# sfipillar:
# category: External collaboration
# risklevel: Medium
# userimpact: Medium
ms.topic: include
ms.date: 09/26/2025
ms.custom: Identity-Secure-Recommendation
# sfipillar: Protect tenants and isolate production systems
# category: External collaboration
# risklevel: Medium
# userimpact: Medium
Modified by John Flores on Oct 10, 2025 5:17 PM
πŸ“– View on learn.microsoft.com
+1 / -1 lines changed
Commit: blocker fixes
Changes:
Before
After
 
**Remediation action**
 
- Learn how to [limit the maximum number of devices per user](/entra/identity/devices/manage-device-identities#configure-device-settings)..
 
**Remediation action**
 
- Learn how to [limit the maximum number of devices per user](/entra/identity/devices/manage-device-identities#configure-device-settings).
+1 / -1 lines changed
Commit: Fix typos and clarify wording in cloud sync docs
Changes:
Before
After
 
|Method|Description|URL|
|-----|-----|-----|
|MS Graph|Create extensions using GRAPH|[Create extensionProperty](/graph/api/application-post-extensionproperty?view=graph-rest-1.0&tabs=http&preserve-view=true)|
|PowerShell|Create extensions using PowerShell|[New-MgApplicationExtensionProperty](/powershell/module/microsoft.graph.applications/new-mgapplicationextensionproperty)|
Using cloud sync and Microsoft Entra Connect|Create extensions using Microsoft Entra Connect|[Create an extension attribute using Microsoft Entra Connect](../../app-provisioning/user-provisioning-sync-attributes-for-mapping.md#create-an-extension-attribute-using-azure-ad-connect)|
|Customizing attributes to sync|Information on customizing, which attributes to synch|[Customize which attributes to synchronize with Microsoft Entra ID](../connect/how-to-connect-sync-feature-directory-extensions.md#select-which-attributes-to-synchronize-with-microsoft-entra-id)
 
|Method|Description|URL|
|-----|-----|-----|
|MS Graph|Create extensions using Microsoft Graph|[Create extensionProperty](/graph/api/application-post-extensionproperty?view=graph-rest-1.0&tabs=http&preserve-view=true)|
|PowerShell|Create extensions using PowerShell|[New-MgApplicationExtensionProperty](/powershell/module/microsoft.graph.applications/new-mgapplicationextensionproperty)|
Using cloud sync and Microsoft Entra Connect|Create extensions using Microsoft Entra Connect|[Create an extension attribute using Microsoft Entra Connect](../../app-provisioning/user-provisioning-sync-attributes-for-mapping.md#create-an-extension-attribute-using-azure-ad-connect)|
|Customizing attributes to sync|Information on customizing, which attributes to synch|[Customize which attributes to synchronize with Microsoft Entra ID](../connect/how-to-connect-sync-feature-directory-extensions.md#select-which-attributes-to-synchronize-with-microsoft-entra-id)
+1 / -1 lines changed
Commit: Fix typos and clarify wording in cloud sync docs
Changes:
Before
After
 
9. There are two possible approaches to set the OU:
 
- You can use custom expressions ensure the group is re-created with the same OU. Us the following expression for ParentDistinguishedName value:
 
```https
IIF(
 
9. There are two possible approaches to set the OU:
 
- You can use custom expressions ensure the group is re-created with the same OU. Use the following expression for ParentDistinguishedName value:
 
```https
IIF(
Modified by Justinha on Oct 10, 2025 2:10 PM
πŸ“– View on learn.microsoft.com
+1 / -1 lines changed
Commit: Fix typos and update date in hybrid identity docs
Changes:
Before
After
>
>These permissions aren't applied to AdminSDHolder objects by default. For more information, see [Microsoft Entra provisioning agent gMSA PowerShell cmdlets](../cloud-sync/how-to-gmsa-cmdlets.md#grant-permissions-to-a-specific-domain).
 
- The provisioning agent must beinstalled on a server that runs Windows Server 2022, Windows Server 2019, or Windows Server 2016.
- The provisioning agent must be able to communicate with one or more domain controllers on ports TCP/389 (LDAP) and TCP/3268 (Global Catalog).
- Required for Global Catalog lookup to filter out invalid membership references
- Microsoft Entra Connect Sync with build version [2.22.8.0](../connect/reference-connect-version-history.md#2280)
>
>These permissions aren't applied to AdminSDHolder objects by default. For more information, see [Microsoft Entra provisioning agent gMSA PowerShell cmdlets](../cloud-sync/how-to-gmsa-cmdlets.md#grant-permissions-to-a-specific-domain).
 
- The provisioning agent must be installed on a server that runs Windows Server 2022, Windows Server 2019, or Windows Server 2016.
- The provisioning agent must be able to communicate with one or more domain controllers on ports TCP/389 (LDAP) and TCP/3268 (Global Catalog).
- Required for Global Catalog lookup to filter out invalid membership references
- Microsoft Entra Connect Sync with build version [2.22.8.0](../connect/reference-connect-version-history.md#2280)

πŸ—‘οΈ Deleted Documentation Files

DELETED docs/includes/secure-recommendations/21822.md
Deleted by John Flores on Oct 10, 2025 6:02 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/includes/secure-recommendations/21822
-19 lines removed
Commit: Delete docs/includes/secure-recommendations/21822.md