πŸ“‹ Microsoft Entra Documentation Changes

Changes for April 24th 2025

Period: April 23rd 2025, 12:00 AM to April 24th 2025, 12:00 AM

πŸ“š Historical Report: This report shows documentation changes that occurred during the 24-hour period ending on April 24th 2025.

πŸ“Š Summary

22
Total Commits
1
New Files
19
Modified Files
4
Deleted Files
12
Contributors

πŸ†• New Documentation Files

+247 lines added
Commit: Breaking article into two, adding new article to the TOC, fixing broken links

πŸ“ Modified Documentation Files

+10 / -242 lines changed
Commit: Breaking article into two, adding new article to the TOC, fixing broken links
Changes:
Before
After
---
title: Understanding Tokens and How to Protect them in Microsoft Entra
description: To protect against token theft and replay attacks, explore the types of tokens used in Microsoft Entra, their role in authentication, and strategies.
ms.service: entra-id
ms.subservice: devices
ms.reviewer: jbley
---
 
# Understanding tokens in Microsoft Entra
 
As attackers increasingly use sophisticated attacks, it's crucial to guard against data exfiltration by hardening your environment against token theft and token replay. Although challenging, there are simple steps you can take to reduce your attack surface and increase the cost for attackers to successfully steal and replay tokens. A robust strategy to protect your tokens requires a multi-layered defense-in-depth approach, which should include:
 
- Hardening your devices against malware-based attacks
- Using Device-based and Risk-based Conditional Access
- Deploying phishing-resistant credentials
- Enforcing device-bound tokens where possible
- Implementing network-based enforcements
 
This document summarizes the basics of what tokens are, how tokens are stolen, and provide concrete steps you can take to mitigate the risk of successful attacks in your environment. Due to the complexity and wide variety of tokens in Microsoft Entra, some topics are generalized for simplicity and may not cover all edge cases. However, this guidance covers most scenarios for public clients. Confidential client scenarios aren't in scope.
 
---
title: Understanding Tokens in Microsoft Entra ID
description: To protect against token theft and replay attacks, explore the types of tokens used in Microsoft Entra, their role in authentication, and strategies.
ms.service: entra-id
ms.subservice: devices
ms.reviewer: jbley
---
 
# Understanding tokens in Microsoft Entra ID
 
As attackers increasingly use sophisticated attacks, it's crucial to guard against data exfiltration by hardening your environment against token theft and token replay. Although challenging, there are simple steps you can take to reduce your attack surface and increase the cost for attackers to successfully steal and replay tokens. A robust strategy to protect your tokens requires a multi-layered defense-in-depth approach, which should include:
 
- Deploying phishing-resistant credentials
- Hardening your devices against malware-based attacks
- Using Device-based and Risk-based Conditional Access
- Enforcing device-bound tokens where possible
- Implementing network-based enforcements
 
This document summarizes the basics of what tokens are, how tokens are stolen, and provide concrete steps you can take to mitigate the risk of successful attacks in your environment. Due to the complexity and wide variety of tokens in Microsoft Entra, some topics are generalized for simplicity and may not cover all edge cases. However, this guidance covers most scenarios for public clients. [Confidential client](../../identity-platform/msal-client-applications.md#public-client-and-confidential-client-authorization) scenarios aren't in scope.
 
+29 / -29 lines changed
Commit: Fixing invalid links
Changes:
Before
After
- [Conditional Access](../conditional-access/overview.md#license-requirements)
- [Microsoft Entra Internet Access for Microsoft services](../../global-secure-access/overview-what-is-global-secure-access.md#licensing-overview)
- [Microsoft Entra ID Protection](../../id-protection/overview-identity-protection.md#license-requirements)
- [Token Protection](../conditional-access/concept-token-protection.md#licensing-requirements)
- [Microsoft Intune (minimum Plan 1)](~/mem/intune/fundamentals/licenses.md#microsoft-intune-plan-1)
- [Microsoft Defender for Endpoint XDR](~/defender-xdr/prerequisites.md#licensing-requirements)
 
## Defense-in-depth strategy against token theft
 
 
- Harden your devices
 
Perform the following configurations and deployments to harden all devices/endpoints as frontline of defense against malware-based token theft. Before you get started, ensure that your devices are enrolled with Intune, and that [Microsoft Defender for Endpoint](~/defender-endpoint/mde-planning-guide.md) is deployed.
 
|Control | Windows 10/11 | macOS | Linux|
|------|------|------|------|
| [Enable Microsoft Defender Antivirus always-on protection](~/defender-endpoint/configure-real-time-protection-microsoft-defender-antivirus.md) for real-time protection, behavior monitoring, and heuristics to identify malware based on known suspicious and malicious activities. | X | X | X |
| [Enable Microsoft Defender Antivirus cloud protection](~/defender-endpoint/enable-cloud-protection-microsoft-defender-antivirus.md) to help protect against malware on your endpoints and across your network. | X | X | X |
| [Enable network protection in Microsoft Defender for Endpoint](~/defender-endpoint/network-protection.md) to protect devices from certain Internet-based events by preventing connections to malicious or suspicious sites. | X | X | X |
| [Enable tamper protection in Microsoft Defender for Endpoint](~/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection.md) to protect certain security settings, such as virus and threat protection, from being disabled or changed. | X | X | - |
- [Conditional Access](../conditional-access/overview.md#license-requirements)
- [Microsoft Entra Internet Access for Microsoft services](../../global-secure-access/overview-what-is-global-secure-access.md#licensing-overview)
- [Microsoft Entra ID Protection](../../id-protection/overview-identity-protection.md#license-requirements)
- [Token Protection](../conditional-access/concept-token-protection.md#requirements)
- [Microsoft Intune (minimum Plan 1)](/intune/fundamentals/licenses##microsoft-intune-plan-1)
- [Microsoft Defender for Endpoint XDR](/defender-xdr/prerequisites#licensing-requirements)
 
## Defense-in-depth strategy against token theft
 
 
- Harden your devices
 
Perform the following configurations and deployments to harden all devices/endpoints as frontline of defense against malware-based token theft. Before you get started, ensure that your devices are enrolled with Intune, and that [Microsoft Defender for Endpoint](/defender-endpoint/mde-planning-guide) is deployed.
 
|Control | Windows 10/11 | macOS | Linux|
|------|------|------|------|
| [Enable Microsoft Defender Antivirus always-on protection](/defender-endpoint/configure-real-time-protection-microsoft-defender-antivirus) for real-time protection, behavior monitoring, and heuristics to identify malware based on known suspicious and malicious activities. | X | X | X |
| [Enable Microsoft Defender Antivirus cloud protection](/defender-endpoint/enable-cloud-protection-microsoft-defender-antivirus) to help protect against malware on your endpoints and across your network. | X | X | X |
| [Enable network protection in Microsoft Defender for Endpoint](/defender-endpoint/network-protection) to protect devices from certain Internet-based events by preventing connections to malicious or suspicious sites. | X | X | X |
| [Enable tamper protection in Microsoft Defender for Endpoint](/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection) to protect certain security settings, such as virus and threat protection, from being disabled or changed. | X | X | - |
Modified by ShawnJackson on Apr 23, 2025 4:33 AM
πŸ“– View on learn.microsoft.com
+21 / -23 lines changed
Commit: edit pass: microsoft-entra-dynamic-groups
Changes:
Before
After
| `mobile` |Any string value or `null` | ```user.mobile -eq "value"```|
| `objectId` |GUID of the user object | ```user.objectId -eq "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb"```|
| `onPremisesDistinguishedName` | Any string value or `null` | ```user.onPremisesDistinguishedName -eq "value"```|
| `onPremisesSecurityIdentifier` | On-premises security identifier (SID) for users who were synchronized from on-premises to the cloud. | ```user.onPremisesSecurityIdentifier -eq "S-1-1-11-1111111111-1111111111-1111111111-1111111"``` |
| `passwordPolicies` |`None`, `DisableStrongPassword`, `DisablePasswordExpiration`, `DisablePasswordExpiration`, `DisableStrongPassword` | ```user.passwordPolicies -eq "DisableStrongPassword"``` |
| `physicalDeliveryOfficeName` |Any string value or `null` | ```user.physicalDeliveryOfficeName -eq "value"``` |
| `postalCode` |Any string value or `null` | ```user.postalCode -eq "value"``` |
The following table lists all the supported operators and their syntax for a single expression. You can use operators with or without the hyphen (`-`) prefix. The `Contains` operator does partial string matches but not matches for items in a collection.
 
> [!CAUTION]
> For best results, minimize the use of `Match` or `Contains` as much as possible. The article [Create simpler, more efficient rules for dynamic membership groups](groups-dynamic-rule-more-efficient.md) provides guidance on how to create rules that result in better dynamic group processing times. The [`memberOf`](groups-dynamic-rule-member-of.md) operator is in preview and should be used with caution, because it has some limitations.
 
| Operator | Syntax |
| --- | --- |
 
If you want to compare the value of a user attribute against multiple values, you can use the `-in` or `-notIn` operator. Use the bracket symbols (`[` and `]`) to begin and end the list of values.
 
In the following example, the expression evaluates to `true` if the value of `user.department` equals any of the values in the list:
 
```
| `mobile` |Any string value or `null` | ```user.mobile -eq "value"```|
| `objectId` |GUID of the user object | ```user.objectId -eq "aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb"```|
| `onPremisesDistinguishedName` | Any string value or `null` | ```user.onPremisesDistinguishedName -eq "value"```|
| `onPremisesSecurityIdentifier` | On-premises security identifier (SID) for users who were synchronized from on-premises to the cloud | ```user.onPremisesSecurityIdentifier -eq "S-1-1-11-1111111111-1111111111-1111111111-1111111"``` |
| `passwordPolicies` |`None`, `DisableStrongPassword`, `DisablePasswordExpiration`, `DisablePasswordExpiration`, `DisableStrongPassword` | ```user.passwordPolicies -eq "DisableStrongPassword"``` |
| `physicalDeliveryOfficeName` |Any string value or `null` | ```user.physicalDeliveryOfficeName -eq "value"``` |
| `postalCode` |Any string value or `null` | ```user.postalCode -eq "value"``` |
The following table lists all the supported operators and their syntax for a single expression. You can use operators with or without the hyphen (`-`) prefix. The `Contains` operator does partial string matches but not matches for items in a collection.
 
> [!CAUTION]
> For best results, minimize the use of `Match` or `Contains` as much as possible. The article [Create simpler, more efficient rules for dynamic membership groups](groups-dynamic-rule-more-efficient.md) provides guidance on how to create rules that result in better dynamic group processing times. The [`memberOf`](groups-dynamic-rule-member-of.md) operator is in preview and has some limitations, so use it with caution.
 
| Operator | Syntax |
| --- | --- |
 
If you want to compare the value of a user attribute against multiple values, you can use the `-in` or `-notIn` operator. Use the bracket symbols (`[` and `]`) to begin and end the list of values.
 
In the following example, the expression evaluates to `true` if the value of `user.department` equals any of the values in the list:
 
```
+14 / -18 lines changed
Commit: Update authenticate-application-id.md
Changes:
Before
After
2. [Bring Your Own Certificate (BYOC)](#bring-your-own-certificate-byoc)
 
## Managed by Microsoft Entra Connect (Recommended)
Microsoft Entra Connect manages the application and certificate including creation, rotation and deletion of the certificate. The certificate is stored in the Local Machine store. For optimal protection of the certificate’s private key, it is recommended that the machine employs a Trusted Platform Module (TPM) solution to establish a hardware-based security boundary. When a TPM is available, key service operations are performed within a dedicated hardware environment. In contrast, if a TPM cannot be used, Entra Connect defaults to storing the certificate in the Local Machine store and marks the private key as non-exportable for additional protection. However, without the hardware isolation provided by a TPM, the private key is secured solely by software safeguards and does not achieve the same level of protection. For more information on TPM, see [Trusted Platform Module Technology Overview](/windows/security/hardware-security/tpm/trusted-platform-module-overview).
 
:::image type="content" source="media/authenticate-application-id/auth-1.png" alt-text="Diagram of authentication with application id." lightbox="media/authenticate-application-id/auth-1.png":::
 
Microsoft recommendeds the Microsoft Entra Connect certificate management option as we manage the keys and automatically roll-over the certificate on expiry.
 
## Bring Your Own Certificate (BYOC)
 
Microsoft Entra Connect Sync manages the application identity that will be used by Entra Connect Sync to authenticate to Microsoft Entra ID, and you manage the certificate credential used by the application. Your administrator is responsible for creating the certificate, rotation and deletion of unused/expired certificates. The certificate should be stored in the Local Machine store. You are responsible for securing the private key of the certificate and ensuring only Microsoft Azure AD Sync service can access the private key for signing.
 
## Prerequisites
The following prerequisites are required to implement authentication using application identity.
- Microsoft Entra account with at least a [Hybrid Identity Administrator](../../role-based-access-control/permissions-reference.md#hybrid-identity-administrator) role.
- On-premises Active Directory Domain Services environment with Windows Server 2016 operating system or later.
 
The following are additional requirements depending on which certificate management option you select.
 
2. [Bring Your Own Certificate (BYOC)](#bring-your-own-certificate-byoc)
 
## Managed by Microsoft Entra Connect (Recommended)
Microsoft Entra Connect manages the application and certificate including creation, rotation and deletion of the certificate. The certificate is stored in the Current User store. For optimal protection of the certificate’s private key, it is recommended that the machine employs a Trusted Platform Module (TPM) solution to establish a hardware-based security boundary. When a TPM is available, key service operations are performed within a dedicated hardware environment. In contrast, if a TPM cannot be used, Entra Connect defaults to storing the certificate in the Current User store and marks the private key as non-exportable for additional protection. However, without the hardware isolation provided by a TPM, the private key is secured solely by software safeguards and does not achieve the same level of protection. For more information on TPM, see [Trusted Platform Module Technology Overview](/windows/security/hardware-security/tpm/trusted-platform-module-overview).
 
:::image type="content" source="media/authenticate-application-id/auth-1.png" alt-text="Diagram of authentication with application id." lightbox="media/authenticate-application-id/auth-1.png":::
 
Microsoft recommendeds the Microsoft Entra Connect certificate management option as we manage the keys and automatically rotate the certificate on expiry.
 
## Bring Your Own Certificate (BYOC)
 
Microsoft Entra Connect Sync manages the application identity that will be used by Entra Connect Sync to authenticate to Microsoft Entra ID, and you manage the certificate credential used by the application. Your administrator is responsible for creating the certificate, rotation and deletion of unused/expired certificates. The certificate should be stored in the Current User store. You are responsible for securing the private key of the certificate and ensuring only Microsoft Azure AD Sync service can access the private key for signing.
> [!NOTE]
> - It is recommended to use the TPM to provide a hardware-based security boundary, as opposed to the Current User store. To check the status of your TPM use the [Get-TPM](/powershell/module/trustedplatformmodule/get-tpm?view=windowsserver2025-ps) PowerShell cmdlet. If using Hyper-V VMs, the TPM can be enabled by checking Security > Enable Trusted Platform Module. This can only be done on a generation 2 virtual machines. Generation 1 virtual machines can't be converted to a generation 2 virtual machines. For more information see [Generation 2 virtual machine security settings for Hyper-V](/windows-server/virtualization/hyper-v/learn-more/generation-2-virtual-machine-security-settings-for-hyper-v) and [Enable Trusted launch on existing Azure Gen2 VMs](/azure/virtual-machines/trusted-launch-existing-vm)
 
 
## Prerequisites
The following prerequisites are required to implement authentication using application identity.
- Microsoft Entra account with at least a [Hybrid Identity Administrator](../../role-based-access-control/permissions-reference.md#hybrid-identity-administrator) role.
- On-premises Active Directory Domain Services environment with Windows Server 2016 operating system or later.
+7 / -6 lines changed
Commit: Adding links to KeyVault
Changes:
Before
After
Policies can be applied to all applications in your organization or to specific applications. In this tutorial, you learn:
 
> [!div class="checklist"]
> * Learn about recommend restrictions for secrets and certificates.
> * Read the current application management policy for your tenant.
> * Update that policy to enforce restrictions.
> * Confirm that the policy has been applied.
 
> [!Important]
 
* **Disable symmetric key usage in applications**: Symmetric keys are similar to client secrets in that they're shared between the application and the resource it accesses. This means that if an attacker gains access to the symmetric key, they can impersonate the application and access the resource. Symmetric keys are also more difficult to manage than asymmetric keys, as they require both parties to share the same key.
 
* **Limit asymmetric key (certificate) lifetime to 180 days**: Certificates provide a more secure way to authenticate applications than client secrets. However, they can still be compromised if not managed properly. By limiting the lifetime of certificates, you can reduce the risk of long-lived certificates being exploited by attackers. Certificates should be rotated regularly to ensure that they aren't compromised. The recommended maximum lifetime for certificates is 180 days. This means that you should rotate your certificates at least every 180 days. Setting a shorter lifetime for highly sensitive applications can further reduce the risk of compromise.
 
To learn more about recommended security practices for Microsoft Entra tenants, see [Configure Microsoft Entra for increased security](https://aka.ms/EntraSecurityRecommendations).
 
 
Before you create a new application management policy, you can read your existing policy to see if it meets your needs. The following example shows how to read the default application management policy for your tenant. You can also reuse this API request to confirm the policy has been applied later in this tutorial.
 
> [!Important]
Policies can be applied to all applications in your organization or to specific applications. In this tutorial, you learn:
 
> [!div class="checklist"]
> * Learn about recommended restrictions for secrets and certificates.
> * Read the current application management policy for your tenant.
> * Update the application policy to enforce restrictions.
> * Confirm that the policy has been applied.
 
> [!Important]
 
* **Disable symmetric key usage in applications**: Symmetric keys are similar to client secrets in that they're shared between the application and the resource it accesses. This means that if an attacker gains access to the symmetric key, they can impersonate the application and access the resource. Symmetric keys are also more difficult to manage than asymmetric keys, as they require both parties to share the same key.
 
* **Limit asymmetric key (certificate) lifetime to 180 days**: Certificates provide a more secure way to authenticate applications than client secrets. However, they can still be compromised if not managed properly. By limiting the lifetime of certificates, you can reduce the risk of long-lived certificates being exploited by attackers. Certificates should be rotated regularly to ensure that they aren't compromised. The recommended maximum lifetime for certificates is 180 days. This means that you should rotate your certificates at least every 180 days. Setting a shorter lifetime for highly sensitive applications can further reduce the risk of compromise. We also recommend you configure automatic rotation of certificates using Azure Key Vault. To learn more, see[Automate the rotation of a secret for resources that use one set of authentication credentials](/azure/key-vault/secrets/tutorial-rotation)
 
To learn more about recommended security practices for Microsoft Entra tenants, see [Configure Microsoft Entra for increased security](https://aka.ms/EntraSecurityRecommendations).
 
 
Before you create a new application management policy, you can read your existing policy to see if it meets your needs. The following example shows how to read the default application management policy for your tenant. You can also reuse this API request to confirm the policy has been applied later in this tutorial.
 
### Example
Modified by ShawnJackson on Apr 23, 2025 4:33 AM
πŸ“– View on learn.microsoft.com
+5 / -5 lines changed
Commit: edit pass: microsoft-entra-dynamic-groups
Changes:
Before
After
 
Microsoft Entra ID provides a rule builder to create and update your important rules more quickly. The rule builder supports the construction of up to five expressions.
 
The rule builder makes it easier to form a rule with a few simple expressions. However, it can't be used to reproduce every rule. If the rule builder doesn't support the rule that you want to create, you can use the text box.
 
Here are some examples of advanced rules or syntax for which we recommend that you use the text box:
> [!NOTE]
> The rule builder might not be able to display some rules constructed in the text box. You might see a message when the rule builder can't display the rule. The rule builder doesn't change the supported syntax, validation, or processing of rules for dynamic membership groups in any way.
 
:::image type="content" source="./media/groups-create-rule/update-dynamic-group-rule.png" alt-text="Screenshot that shows the rule builder, with the action for adding an expression highlighted.":::
 
For examples of syntax, supported properties, operators, and values for a membership rule, see [Manage rules for dynamic membership groups in Microsoft Entra ID](groups-dynamic-membership.md).
 
## Create a rule for a dynamic membership group
 
- **Not started**: Processing hasn't started.
 
> [!NOTE]
> This page now has a **Pause processing** option. Previously, this option was available only through the modification of the `membershipRuleProcessingState` property. Someone who has at least the [Groups Administrator](/entra/identity/role-based-access-control/permissions-reference#groups-administrator) role can manage this setting and can pause and resume dynamic membership group processing. Group owners who don't have the correct roles don't have the necessary rights to edit this setting.
 
 
Microsoft Entra ID provides a rule builder to create and update your important rules more quickly. The rule builder supports the construction of up to five expressions.
 
:::image type="content" source="./media/groups-create-rule/update-dynamic-group-rule.png" alt-text="Screenshot that shows the rule builder, with the action for adding an expression highlighted.":::
 
The rule builder makes it easier to form a rule with a few simple expressions. However, it can't be used to reproduce every rule. If the rule builder doesn't support the rule that you want to create, you can use the text box.
 
Here are some examples of advanced rules or syntax for which we recommend that you use the text box:
> [!NOTE]
> The rule builder might not be able to display some rules constructed in the text box. You might see a message when the rule builder can't display the rule. The rule builder doesn't change the supported syntax, validation, or processing of rules for dynamic membership groups in any way.
 
For examples of syntax and supported properties, operators, and values for a membership rule, see [Manage rules for dynamic membership groups in Microsoft Entra ID](groups-dynamic-membership.md).
 
## Create a rule for a dynamic membership group
 
- **Not started**: Processing hasn't started.
 
> [!NOTE]
> This page now has a **Pause processing** option. Previously, this option was available only through the modification of the `membershipRuleProcessingState` property. Someone who has at least the [Groups Administrator](/entra/identity/role-based-access-control/permissions-reference#groups-administrator) role can manage this setting and can pause and resume the processing of dynamic membership groups. Group owners who don't have the correct roles don't have the necessary rights to edit this setting.
 
+5 / -5 lines changed
Commit: removed preview for trusts
Changes:
Before
After
---
title: Tutorial - Create a forest trust in Microsoft Entra Domain Services (Preview) | Microsoft Learn
description: Learn how to create a one-way outbound forest to an on-premises AD DS domain in the Microsoft Entra admin center for Microsoft Entra Domain Services
services: active-directory-ds
author: justinha
ms.subservice: domain-services
ms.workload: identity
ms.topic: tutorial
ms.date: 02/19/2025
ms.author: justinha
 
#Customer intent: As an identity administrator, I want to create a one-way outbound forest from a Microsoft Entra Domain Services forest to an on-premises Active Directory Domain Services forest to provide authentication and resource access between forests.
---
 
# Tutorial: Create a two-way forest trust in Microsoft Entra Domain Services with an on-premises domain (Preview)
 
You can create a forest trust between Microsoft Entra Domain Services and on-premises AD DS environments. The forest trust relationship lets users, applications, and computers authenticate against an on-premises domain from the Domain Services managed domain, or vice versa. A forest trust can help users access resources in scenarios such as:
 
 
Trust direction | User access
---
title: Tutorial - Create a forest trust in Microsoft Entra Domain Services | Microsoft Learn
description: Learn how to create a one-way outbound forest to an on-premises AD DS domain in the Microsoft Entra admin center for Microsoft Entra Domain Services
services: active-directory-ds
author: justinha
ms.subservice: domain-services
ms.workload: identity
ms.topic: tutorial
ms.date: 04/22/2025
ms.author: justinha
 
#Customer intent: As an identity administrator, I want to create a one-way outbound forest from a Microsoft Entra Domain Services forest to an on-premises Active Directory Domain Services forest to provide authentication and resource access between forests.
---
 
# Tutorial: Create a two-way forest trust in Microsoft Entra Domain Services with an on-premises domain
 
You can create a forest trust between Microsoft Entra Domain Services and on-premises AD DS environments. The forest trust relationship lets users, applications, and computers authenticate against an on-premises domain from the Domain Services managed domain, or vice versa. A forest trust can help users access resources in scenarios such as:
 
 
Trust direction | User access
+6 / -2 lines changed
Commit: Update concept-certificate-based-authentication-certificateuserids.md
Changes:
Before
After
`[[-Certificate] <System.Security.Cryptography.X509Certificates.X509Certificate2> [-CertificateMapping] <string>]`
`[<CommonParameters>]`
 
>[!NOTE] If the values from the certificate are too long, you can send the output to a file and copy from there.
> Use Get-EntraUserCertificateUserIdsFromCertificate -Path C:\Downloads\test.pem | Format-List | Out-File -FilePath ".\certificateUserIds.txt"
 
**Example 1: Retrieve certificate object from a certificate path**
 
 
 
 
 
`[[-Certificate] <System.Security.Cryptography.X509Certificates.X509Certificate2> [-CertificateMapping] <string>]`
`[<CommonParameters>]`
 
If the values from the certificate are too long, you can send the output to a file and copy from there.
 
```powershell
Connect-Entra -Scopes 'User.Read.All'
Get-EntraUserCertificateUserIdsFromCertificate -Path C:\Downloads\test.pem | Format-List | Out-File -FilePath ".\certificateUserIds.txt"
```
 
**Example 1: Retrieve certificate object from a certificate path**
 
Modified by ShawnJackson on Apr 23, 2025 4:33 AM
πŸ“– View on learn.microsoft.com
+4 / -4 lines changed
Commit: edit pass: microsoft-entra-dynamic-groups
Changes:
Before
After
 
### Optimize rule efficiency
 
- **Avoid Match**: Avoid the use of the `Match` operator in rules as much as possible. Instead, use the `StartsWith`, `Equals`, or `EndsWith` operator.
 
- **Avoid Contains**: Similar to the use of `Match`, avoid the use of the `Contains` operator in rules as much as possible. It can lead to increased processing time.
 
- **Use fewer OR operators**: Instead, use the `-in` operator to group rules into a single criterion. Grouping rules makes them easier to evaluate.
 
- **Minimize the use of MemberOf (at this time)**: [`memberOf`](groups-dynamic-rule-member-of.md) is currently in preview. It can introduce more complexity, particularly if a tenant has a large number of groups or frequent updates. Avoid using this operator if possible, because it comes with bugs and limitations. The recommendation is to delete existing `MemberOf` groups in your tenant.
 
For more help with optimizing dynamic group processing, review [Create simpler, more efficient rules for dynamic membership groups in Microsoft Entra ID](groups-dynamic-rule-more-efficient.md).
 
 
### Optimize rule efficiency
 
- Avoid the use of the `Match` operator in rules as much as possible. Instead, use the `StartsWith`, `Equals`, or `EndsWith` operator.
 
- Avoid the use of the `Contains` operator in rules as much as possible. It can lead to increased processing time.
 
- Use fewer `-or` operators. Instead, use the `-in` operator to group rules into a single criterion. Grouping rules makes them easier to evaluate.
 
- Avoid the use of the [`memberOf`](groups-dynamic-rule-member-of.md) operator if possible. It's currently in preview, and it comes with bugs and limitations. It can also introduce more complexity, particularly if a tenant has a large number of groups or frequent updates. The recommendation is to delete existing `MemberOf` groups in your tenant.
 
For more help with optimizing dynamic group processing, review [Create simpler, more efficient rules for dynamic membership groups in Microsoft Entra ID](groups-dynamic-rule-more-efficient.md).
 
+3 / -3 lines changed
Commit: edit pass: microsoft-entra-dynamic-groups
Changes:
Before
After
 
# Create simpler, more efficient rules for dynamic membership groups in Microsoft Entra ID
 
This article also discusses the most common methods that you can use to simplify your rules for dynamic membership groups. Rules that are simpler and more efficient result in better processing times for dynamic groups.
 
When you're writing membership rules for dynamic membership groups, follow the tips in this article to ensure that you create these rules as efficiently as possible.
 
 
Minimize your use of the `-match` operator in rules as much as possible. Instead, explore if it's possible to use the `-startswith` or `-eq` operator. Consider using other properties that allow you to write rules to select the users for a group without using the `-match` operator.
 
For example, if you want a rule for the group that contains all users whose city is Lagos, don't use a rule like this one:
 
- `user.city -match "ago"`
- `user.city -match ".*?ago.*"`
 
## Avoid redundant criteria
 
Ensure that you aren't using redundant criteria in your rule. For example, instead of using a rule like this one:
 
- `user.city -eq "Lagos" or user.city -startswith "Lag"`
 
# Create simpler, more efficient rules for dynamic membership groups in Microsoft Entra ID
 
This article discusses the most common methods that you can use to simplify your rules for dynamic membership groups. Rules that are simpler and more efficient result in better processing times for dynamic groups.
 
When you're writing membership rules for dynamic membership groups, follow the tips in this article to ensure that you create these rules as efficiently as possible.
 
 
Minimize your use of the `-match` operator in rules as much as possible. Instead, explore if it's possible to use the `-startswith` or `-eq` operator. Consider using other properties that allow you to write rules to select the users for a group without using the `-match` operator.
 
For example, if you want a rule for the group that contains all users whose city is Lagos, don't use a rule like these:
 
- `user.city -match "ago"`
- `user.city -match ".*?ago.*"`
 
## Avoid redundant criteria
 
Ensure that you aren't using redundant criteria in your rule. For example, don't use a rule like this one:
 
- `user.city -eq "Lagos" or user.city -startswith "Lag"`
+3 / -3 lines changed
Commit: removed preview for trusts
Changes:
Before
After
---
title: How trusts work for Microsoft Entra Domain Services (Preview) | Microsoft Learn
description: Learn more about how forest trust work with Microsoft Entra Domain Services
author: justinha
manager: femila
ms.service: entra-id
ms.subservice: domain-services
ms.topic: conceptual
ms.date: 01/27/2025
ms.author: justinha
---
 
# How trust relationships work for forests in Active Directory (Preview)
 
Active Directory Domain Services (AD DS) provides security across multiple domains or forests through domain and forest trust relationships. Before authentication can occur across trusts, Windows must first check if the domain being requested by a user, computer, or service has a trust relationship with the domain of the requesting account.
 
---
title: How trusts work for Microsoft Entra Domain Services | Microsoft Learn
description: Learn more about how forest trust work with Microsoft Entra Domain Services
author: justinha
manager: femila
ms.service: entra-id
ms.subservice: domain-services
ms.topic: conceptual
ms.date: 04/22/2025
ms.author: justinha
---
 
# How trust relationships work for forests in Active Directory
 
Active Directory Domain Services (AD DS) provides security across multiple domains or forests through domain and forest trust relationships. Before authentication can occur across trusts, Windows must first check if the domain being requested by a user, computer, or service has a trust relationship with the domain of the requesting account.
 
+3 / -3 lines changed
Commit: removed preview for trusts
Changes:
Before
After
---
title: Create a Microsoft Entra Domain Services forest trust using Azure PowerShell (Preview) | Microsoft Learn
description: In this article, learn how to create and configure a Microsoft Entra Domain Services forest trust to an on-premises Active Directory Domain Services environment using Azure PowerShell.
author: justinha
manager: femila
ms.service: entra-id
ms.subservice: domain-services
ms.topic: conceptual
ms.date: 01/26/2025
ms.author: justinha
ms.reviewer: wanjikumugo
ms.custom: devx-track-azurepowershell, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
#Customer intent: As an identity administrator, I want to create a Microsoft Entra Domain Services forest and one-way outbound trust from a Microsoft Entra Domain Services forest to an on-premises Active Directory Domain Services forest using Azure PowerShell to provide authentication and resource access between forests.
---
 
# Create a Microsoft Entra Domain Services forest trust to an on-premises domain using Azure PowerShell (Preview)
 
Organizations often create a trust to improve user collaboration when they might manage identities in a hybrid environment, or they plan for a merger or acquisition. Microsoft Entra Domain Services always supported one-way, outbound trusts from a managed domain to another domain. Currently in preview, you can also create one-way inbound trusts or two-way trusts.
 
---
title: Create a Microsoft Entra Domain Services forest trust using Azure PowerShell | Microsoft Learn
description: In this article, learn how to create and configure a Microsoft Entra Domain Services forest trust to an on-premises Active Directory Domain Services environment using Azure PowerShell.
author: justinha
manager: femila
ms.service: entra-id
ms.subservice: domain-services
ms.topic: conceptual
ms.date: 04/22/2025
ms.author: justinha
ms.reviewer: wanjikumugo
ms.custom: devx-track-azurepowershell, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
#Customer intent: As an identity administrator, I want to create a Microsoft Entra Domain Services forest and one-way outbound trust from a Microsoft Entra Domain Services forest to an on-premises Active Directory Domain Services forest using Azure PowerShell to provide authentication and resource access between forests.
---
 
# Create a Microsoft Entra Domain Services forest trust to an on-premises domain using Azure PowerShell
 
Organizations often create a trust to improve user collaboration when they might manage identities in a hybrid environment, or they plan for a merger or acquisition. Microsoft Entra Domain Services always supported one-way, outbound trusts from a managed domain to another domain. Currently in preview, you can also create one-way inbound trusts or two-way trusts.
 
Modified by ShawnJackson on Apr 23, 2025 4:33 AM
πŸ“– View on learn.microsoft.com
+2 / -2 lines changed
Commit: edit pass: microsoft-entra-dynamic-groups
Changes:
Before
After
 
1. On the **Properties** page for the group, select a **Membership type** value of **Assigned (static)**, **Dynamic User**, or **Dynamic Device**, depending on your desired membership type. For dynamic membership groups, you can use the rule builder to select options for a simple rule or write a membership rule yourself.
 
The following steps are an example of changing a group from static to dynamic membership groups for a group of users:
 
1. Select a **Membership type** of **Dynamic User**. In the dialog that explains the changes to the dynamic membership groups, select **Yes** to continue.
 
:::image type="content" source="./media/groups-change-type/select-group-to-convert.png" alt-text="Screenshot of selecting a membership type of dynamic user.":::
 
1. On the **Properties** page for the group, select a **Membership type** value of **Assigned (static)**, **Dynamic User**, or **Dynamic Device**, depending on your desired membership type. For dynamic membership groups, you can use the rule builder to select options for a simple rule or write a membership rule yourself.
 
The following steps are an example of changing a group of users from static to dynamic membership groups:
 
1. For **Membership type**, select **Dynamic User**. In the dialog that explains the changes to the dynamic membership groups, select **Yes** to continue.
 
:::image type="content" source="./media/groups-change-type/select-group-to-convert.png" alt-text="Screenshot of selecting a membership type of dynamic user.":::
+2 / -2 lines changed
Commit: edit pass: sspr-articles
Changes:
Before
After
---
# Customize the user experience for Microsoft Entra self-service password reset
 
Self-service password reset (SSPR) gives users in Microsoft Entra ID the ability to change or reset their password, with no administrator or help desk involvement. If a user's account is locked or they forget their password, they can follow prompts to unblock themselves and get back to work. This ability reduces help-desk calls and loss of productivity when a user can't sign in to their device or an application.
 
To improve the SSPR experience for users, you can customize the look and feel of the password reset page, email notifications, or sign-in pages. Customization options help to make it clear to users that they're in the right place and give them confidence that they're accessing company resources.
 
 
If your organization doesn't want to notify administrators about password reset requests, you can use the following configuration options:
 
* Customize the help-desk link to provide a web URL address that users can use to get assistance. This option is under **Password Reset** > **Customization** > **Custom helpdesk email or URL**.
* Enable self-service password reset for all users. This option is under **Password Reset** > **Properties**. If you don't want users to reset their own passwords, you can scope access to an empty group. *We don't recommend this option.*
 
## Customize the sign-in page and access panel
---
# Customize the user experience for Microsoft Entra self-service password reset
 
Self-service password reset (SSPR) gives users in Microsoft Entra ID the ability to change or reset their password, with no administrator or helpdesk involvement. If a user's account is locked or they forget their password, they can follow prompts to unblock themselves and get back to work. This ability reduces helpdesk calls and loss of productivity when a user can't sign in to their device or an application.
 
To improve the SSPR experience for users, you can customize the look and feel of the password reset page, email notifications, or sign-in pages. Customization options help to make it clear to users that they're in the right place and give them confidence that they're accessing company resources.
 
 
If your organization doesn't want to notify administrators about password reset requests, you can use the following configuration options:
 
* Customize the helpdesk link to provide a web URL address that users can use to get assistance. This option is under **Password Reset** > **Customization** > **Custom helpdesk email or URL**.
* Enable self-service password reset for all users. This option is under **Password Reset** > **Properties**. If you don't want users to reset their own passwords, you can scope access to an empty group. *We don't recommend this option.*
 
## Customize the sign-in page and access panel
+2 / -2 lines changed
Commit: edit pass: sspr-articles
Changes:
Before
After
---
# Enable Microsoft Entra self-service password reset on the Windows sign-in screen
 
By using self-service password reset (SSPR) in Microsoft Entra ID, users can change or reset their password with no administrator or help desk involvement. Typically, users open a web browser on another device to access the [SSPR portal](https://aka.ms/sspr). To improve the experience on computers that run Windows 7, 8, 8.1, 10, and 11, you can enable users to reset their password on the Windows sign-in screen.
 
![Screenshot that shows examples of Windows sign-in screens with the SSPR link.](./media/howto-sspr-windows/windows-reset-password.png)
 
This article shows administrators how to enable SSPR for Windows devices in an enterprise.
 
If your IT team hasn't enabled the ability to use SSPR from your Windows device or you have problems during sign-in, reach out to your help desk for more assistance.
 
## General limitations
 
---
# Enable Microsoft Entra self-service password reset on the Windows sign-in screen
 
By using self-service password reset (SSPR) in Microsoft Entra ID, users can change or reset their password with no administrator or helpdesk involvement. Typically, users open a web browser on another device to access the [SSPR portal](https://aka.ms/sspr). To improve the experience on computers that run Windows 7, 8, 8.1, 10, and 11, you can enable users to reset their password on the Windows sign-in screen.
 
![Screenshot that shows examples of Windows sign-in screens with the SSPR link.](./media/howto-sspr-windows/windows-reset-password.png)
 
This article shows administrators how to enable SSPR for Windows devices in an enterprise.
 
If your IT team hasn't enabled the ability to use SSPR from your Windows device or you have problems during sign-in, reach out to your helpdesk for more assistance.
 
## General limitations
 

πŸ—‘οΈ Deleted Documentation Files

DELETED docs/identity-platform/saml-claims-customization.md
Deleted by Gearoid O'Donnell on Apr 23, 2025 8:49 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity-platform/saml-claims-customization
-273 lines removed
Commit: Cleaning up old how tos
DELETED docs/identity-platform/migrate-off-email-claim-authorization.md
Deleted by Gearoid O'Donnell on Apr 23, 2025 8:49 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity-platform/migrate-off-email-claim-authorization
-123 lines removed
Commit: Cleaning up old how tos
DELETED docs/identity-platform/v2-howto-get-appsource-certified.md
Deleted by Gearoid O'Donnell on Apr 23, 2025 8:49 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity-platform/v2-howto-get-appsource-certified
-108 lines removed
Commit: Cleaning up old how tos
DELETED docs/identity-platform/howto-build-services-resilient-to-metadata-refresh.md
Deleted by Gearoid O'Donnell on Apr 23, 2025 8:49 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity-platform/howto-build-services-resilient-to-metadata-refresh
-82 lines removed
Commit: Cleaning up old how tos