📋 Microsoft Entra Documentation Changes

Changes for June 5th 2025

Period: June 4th 2025, 12:00 AM to June 5th 2025, 12:00 AM

📚 Historical Report: This report shows documentation changes that occurred during the 24-hour period ending on June 5th 2025.

📊 Summary

41
Total Commits
0
New Files
167
Modified Files
0
Deleted Files
18
Contributors

📝 Modified Documentation Files

Modified by csmulligan on Jun 4, 2025 12:51 AM
📖 View on learn.microsoft.com
+1 / -81 lines changed
Commit: Remove AAD references.
Changes:
Before
After
---
title: Allow or Block Invitations
description: Learn how an administrator create a list to allow or block B2B collaboration with specific domains by using the Microsoft Entra admin center or PowerShell.
 
ms.service: entra-external-id
This article discusses two ways to configure an allow or blocklist for B2B collaboration:
 
- In the portal by configuring collaboration restrictions in your organization's [External collaboration settings](external-collaboration-settings-configure.md)
- Through PowerShell
 
## Important considerations
 
 
Switching from one policy to another discards the existing policy configuration. Make sure to back up details of your configuration before you perform the switch.
 
## Set the allow or blocklist policy using PowerShell
 
### Prerequisite
 
---
title: Allow or Block Invitations
description: Learn how an administrator create a list to allow or block B2B collaboration with specific domains by using the Microsoft Entra admin center.
 
ms.service: entra-external-id
This article discusses two ways to configure an allow or blocklist for B2B collaboration:
 
- In the portal by configuring collaboration restrictions in your organization's [External collaboration settings](external-collaboration-settings-configure.md)
 
## Important considerations
 
 
Switching from one policy to another discards the existing policy configuration. Make sure to back up details of your configuration before you perform the switch.
 
 
## Next steps
 
 
 
Modified by shlipsey3 on Jun 4, 2025 2:43 AM
📖 View on learn.microsoft.com
+15 / -11 lines changed
Commit: Update copilot-entra-recommendations.md
Changes:
Before
After
>
> The following roles can use this feature: Global Administrator, Application Administrator, IT Governance Administrator, Privileged Role Administrator, Identity Governance Administrator, Conditional Access Administrator, Security Administrator, Hybrid Identity Administrator, Authentication Policy Administrator, Authentication Administrator.
 
Recommendations in Microsoft Entra help you improve the status and security of your tenant by providing actionable insights and guidance. These recommendations cover various areas, including secure score, best practices, conditional access policies, and more. Using the capabilities of Microsoft Security Copilot, you can now interact with these recommendations using natural language, enabling your security team to quickly investigate how to evolve your tenant to a secure and healthy state.
 
This article describes how to use Microsoft Security Copilot to investigate recommendations in Microsoft Entra. This feature is available using a free Microsoft Entra ID license, or a Microsoft Entra ID P1 or P2 license. It is also available in Microsoft Entra Workload ID. You also need to have a cloud tenant with recommendations for maximizing your license on it.
 
## Investigate recommendations in Microsoft Entra
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/) as at least a [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator).
1. Navigate to {ADDME}
 
> [!NOTE]
> This space is being reserved for an image showing the Copilot experience in the Microsoft Entra admin center.
 
You cab use the following example prompts to investigate recommendations in Microsoft Entra:
 
- *List all Entra recommendations*
- *Show me the Entra recommendations*
- *Show Entra recommendation "example” and its details*
>
> The following roles can use this feature: Global Administrator, Application Administrator, IT Governance Administrator, Privileged Role Administrator, Identity Governance Administrator, Conditional Access Administrator, Security Administrator, Hybrid Identity Administrator, Authentication Policy Administrator, Authentication Administrator.
 
Recommendations in Microsoft Entra help you improve the security posture of your tenant by providing actionable insights and guidance. These recommendations cover the many features, best practices, and settings of Microsoft Entra, such as using least privileged administrator roles, configuring Self-Service Password Reset, and protecting your tenant with Conditional Access policies. Some recommendations factor into your Identity Secure Score, which can help you monitor and improve the security of your tenant. Using the capabilities of Microsoft Security Copilot, you can now interact with these recommendations using natural language, enabling your security team to quickly investigate how to evolve your tenant to a secure and healthy state.
 
This article describes how to use Microsoft Security Copilot to investigate recommendations in Microsoft Entra. This feature is available using a free Microsoft Entra ID license, or a Microsoft Entra ID P1 or P2 license. It is also available in Microsoft Entra Workload ID. You also need to have a cloud tenant with recommendations for maximizing your license on it.
 
## Investigate recommendations in Microsoft Entra
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/) as at least a [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator).
1. Browse to **Entra ID** > **Overview** > **Recommendations**.
1. {Copilot steps}.
 
 
 
> [!NOTE]
> This space is being reserved for an image showing the Copilot experience in the Microsoft Entra admin center.
 
You cab use the following example prompts to investigate recommendations in Microsoft Entra:
 
Modified by Sumeet Mittal on Jun 4, 2025 4:52 AM
📖 View on learn.microsoft.com
+18 / -0 lines changed
Commit: Update concept-connectors.md
Changes:
Before
After
 
For more information about optimizing your network, see [Network topology considerations when using Microsoft Entra application proxy](../identity/app-proxy/application-proxy-network-topology.md).
 
## Specifications and Sizing Requirements
The following specifications are recommended for each Entra Private Network Connector:
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
For more information about optimizing your network, see [Network topology considerations when using Microsoft Entra application proxy](../identity/app-proxy/application-proxy-network-topology.md).
 
## Expanding Ephemeral Port Range
 
Private Network connectors initiate TCP/UDP connections to designated destination endpoints, requiring available source ports on the connector host machine. Expanding the ephemeral port range can improve the availability of source ports, particularly when managing a high volume of concurrent connections.
 
To view the current dynamic port range on a system, use the following netsh commands:
- netsh int ipv4 show dynamicport tcp
- netsh int ipv4 show dynamicport udp
- netsh int ipv6 show dynamicport tcp
- netsh int ipv6 show dynamicport udp
Sample netsh commands to increase the ports
- netsh int ipv4 set dynamicport tcp start=1025 num=64511
- netsh int ipv4 set dynamicport udp start=1025 num=64511
- netsh int ipv6 set dynamicport tcp start=1025 num=64511
- netsh int ipv6 set dynamicport udp start=1025 num=64511
 
These commands set the dynamic port range from 1025 to the maximum of 65535. The minimum start port is 1025.
+13 / -4 lines changed
Commit: Update concept-supported-features-customers.md
Changes:
Before
After
ms.service: entra-external-id
ms.subservice: external
ms.topic: concept-article
ms.date: 05/20/2025
ms.custom: it-pro, seo-july-2024, sfi-ropc-nochange
#Customer intent: As a dev, devops, or it admin, I want to learn about features supported in a CIAM tenant.
---
| **Authentication** > **Redirect URIs**| The URIs Microsoft Entra ID accepts as destinations when returning authentication responses (tokens) after successfully authenticating or signing out users. | Same as workforce.|
| **Authentication** > **Front-channel logout URL**| This URL is where Microsoft Entra ID sends a request to have the application clear the user's session data. The Front-channel logout URL is required for single sign-out to work correctly.| Same as workforce.|
| **Authentication** > **Implicit grant and hybrid flows**| Request a token directly from the authorization endpoint. | Same as workforce.|
| **Certificates & secrets** | <ul><li>[Certificate](../../identity-platform/how-to-add-credentials.md?tabs=certificate)</li><li>[Client secrets](../../identity-platform/how-to-add-credentials.md?tabs=client-secret)</li><li>[Federated credentials](../../identity-platform/how-to-add-credentials.md?tabs=federated-credential)</li></ul>| Same as workforce.|
| **Certificates & secrets** > **Rotation**| Update client credentials to ensure they remain valid and secure, while users can continue to sign-in. [Certificates](../../identity-platform/how-to-add-credentials.md?tabs=certificate), [secrets](../../identity-platform/how-to-add-credentials.md?tabs=client-secret), and [federated credentials](../../identity-platform/how-to-add-credentials.md?tabs=federated-credential) can be rotated by adding a new one and then removing the old one.|Same as workforce.|
|**Certificates & secrets** > **Policy** | Configure the [application management policies](~/identity/enterprise-apps/tutorial-enforce-secret-standards.md) to enforce secret and certificate restrictions. | Not available |
| **API permissions** | Add, remove, and replace permissions to an application. After permissions are added to your application, users or admins need to grant consent to the new permissions. Learn more about [updating an app's requested permissions in Microsoft Entra ID](../../identity-platform/howto-update-permissions.md). | The following are the allowed permissions: Microsoft Graph `offline_access`, `openid`, and `User.Read` and your **My APIs** delegated permissions. Only an admin can consent on behalf of the organization. |
| **Expose an API** | [Define custom scopes](../../identity-platform/quickstart-configure-app-expose-web-apis.md) to restrict access to data and functionality protected by the API. An application that requires access to parts of this API can request that a user or admin consent to one or more of these scopes. | Define custom scopes to restrict access to data and functionality protected by the API. An application that requires access to parts of this API can request that admin consent to one or more of these scopes. |
| **App roles**| App roles are [custom roles](../../identity-platform/howto-add-app-roles-in-apps.md) to assign permissions to users or apps. The application defines and publishes the app roles and interprets them as permissions during authorization.| Same as workforce. Learn more about [using role-based access control for applications](how-to-use-app-roles-customers.md) in an external tenant. |
| **Owners** | Application owners can view and edit the application registration. Additionally, any user (who might not be listed) with administrative privileges to manage any application (for example, [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator)) can view and edit the application registration. | Same as workforce. |
| **Roles and administrators** | [Administrative roles](~/identity/role-based-access-control/permissions-reference.md) are used for granting access for privileged actions in Microsoft Entra ID. | Only the [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator) role can be used for apps in external tenants. This role grants the ability to create and manage all aspects of application registrations and enterprise applications. |
| **Assigning users and groups to an app**| When user assignment is required, only those users you assign to the application (either through direct user assignment or based on group membership) are able to sign in. For more information, see [manage users and groups assignment to an application](~/identity/enterprise-apps/assign-user-or-group-access-portal.md)| Not available |
 
ms.service: entra-external-id
ms.subservice: external
ms.topic: concept-article
ms.date: 06/04/2025
ms.custom: it-pro, seo-july-2024, sfi-ropc-nochange
#Customer intent: As a dev, devops, or it admin, I want to learn about features supported in a CIAM tenant.
---
| **Authentication** > **Redirect URIs**| The URIs Microsoft Entra ID accepts as destinations when returning authentication responses (tokens) after successfully authenticating or signing out users. | Same as workforce.|
| **Authentication** > **Front-channel logout URL**| This URL is where Microsoft Entra ID sends a request to have the application clear the user's session data. The Front-channel logout URL is required for single sign-out to work correctly.| Same as workforce.|
| **Authentication** > **Implicit grant and hybrid flows**| Request a token directly from the authorization endpoint. | Same as workforce.|
| **Certificates & secrets** | Multiple credentials enable rotation with minimum downtime, easy migration from secrets to certificates (Microsoft recommends that you use certificates), and fallback options if a credential is compromised or expires: <ul><li>[Certificate](../../identity-platform/how-to-add-credentials.md?tabs=certificate)</li><li>[Client secrets](../../identity-platform/how-to-add-credentials.md?tabs=client-secret)</li><li>[Federated credentials](../../identity-platform/how-to-add-credentials.md?tabs=federated-credential)</li></ul> | Same as workforce.|
| **Certificates & secrets** > **Rotation**| Update client credentials to ensure they remain valid and secure, while users can continue to sign-in. [Certificates](../../identity-platform/how-to-add-credentials.md?tabs=certificate), [secrets](../../identity-platform/how-to-add-credentials.md?tabs=client-secret), and [federated credentials](../../identity-platform/how-to-add-credentials.md?tabs=federated-credential) can be rotated by adding a new one and then removing the old one.|Same as workforce.|
|**Certificates & secrets** > **Policy** | Configure the [application management policies](~/identity/enterprise-apps/tutorial-enforce-secret-standards.md) to enforce secret and certificate restrictions. | Not available |
| **API permissions** | Add, remove, and replace permissions to an application. After permissions are added to your application, users or admins need to grant consent to the new permissions. Learn more about [updating an app's requested permissions in Microsoft Entra ID](../../identity-platform/howto-update-permissions.md). | The following are the allowed permissions: Microsoft Graph `offline_access`, `openid`, and `User.Read` and your **My APIs** delegated permissions. Only an admin can consent on behalf of the organization. |
| **Expose an API** | [Define custom scopes](../../identity-platform/quickstart-configure-app-expose-web-apis.md) to restrict access to data and functionality protected by the API. An application that requires access to parts of this API can request that a user or admin consent to one or more of these scopes. | Define custom scopes to restrict access to data and functionality protected by the API. An application that requires access to parts of this API can request that admin consent to one or more of these scopes. |
| **Owners** | Application owners can view and edit the application registration. Additionally, any user (who might not be listed) with administrative privileges to manage any application (for example, [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator)) can view and edit the application registration. | Same as workforce. |
| **Roles and administrators** | [Administrative roles](~/identity/role-based-access-control/permissions-reference.md) are used for granting access for privileged actions in Microsoft Entra ID. | Only the [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator) role can be used for apps in external tenants. This role grants the ability to create and manage all aspects of application registrations and enterprise applications. |
 
### Application authorization
 
+8 / -8 lines changed
Commit: changed July 1 to September 1
Changes:
Before
After
ms.service: entra-id
ms.subservice: authentication
ms.topic: conceptual
ms.date: 04/25/2025
ms.author: justinha
author: justinha
manager: femila
### Applications
 
> [!NOTE]
> The date of enforcement for Phase 2 has changed to July 1, 2025.
 
The following table lists affected apps, app IDs, and URLs for Azure.
 
| [Azure portal](/azure/azure-portal/) | c44b4083-3bb0-49c1-b47d-974e53cbdf3c | Second half of 2024 |
| [Microsoft Entra admin center](https://aka.ms/MSEntraPortal) | c44b4083-3bb0-49c1-b47d-974e53cbdf3c | Second half of 2024 |
| [Microsoft Intune admin center](https://aka.ms/IntunePortal) | c44b4083-3bb0-49c1-b47d-974e53cbdf3c | Second half of 2024 |
| [Azure command-line interface (Azure CLI)](/cli/azure/) | 04b07795-8ddb-461a-bbee-02f9e1bf7b46 | July 1, 2025 |
| [Azure PowerShell](/powershell/azure/) | 1950a258-227b-4e31-a9cf-717495945fc2 | July 1, 2025 |
| [Azure mobile app](/azure/azure-portal/mobile-app/overview) | 0c1307d4-29d6-4389-a11c-5cbe7f65d7fa | July 1, 2025 |
ms.service: entra-id
ms.subservice: authentication
ms.topic: conceptual
ms.date: 06/03/2025
ms.author: justinha
author: justinha
manager: femila
### Applications
 
> [!NOTE]
> The date of enforcement for Phase 2 has changed to September 1, 2025.
 
The following table lists affected apps, app IDs, and URLs for Azure.
 
| [Azure portal](/azure/azure-portal/) | c44b4083-3bb0-49c1-b47d-974e53cbdf3c | Second half of 2024 |
| [Microsoft Entra admin center](https://aka.ms/MSEntraPortal) | c44b4083-3bb0-49c1-b47d-974e53cbdf3c | Second half of 2024 |
| [Microsoft Intune admin center](https://aka.ms/IntunePortal) | c44b4083-3bb0-49c1-b47d-974e53cbdf3c | Second half of 2024 |
| [Azure command-line interface (Azure CLI)](/cli/azure/) | 04b07795-8ddb-461a-bbee-02f9e1bf7b46 | September 1, 2025 |
| [Azure PowerShell](/powershell/azure/) | 1950a258-227b-4e31-a9cf-717495945fc2 | September 1, 2025 |
| [Azure mobile app](/azure/azure-portal/mobile-app/overview) | 0c1307d4-29d6-4389-a11c-5cbe7f65d7fa | September 1, 2025 |
+4 / -4 lines changed
Commit: [Conditional Access] First party apps in picker
Changes:
Before
After
ms.custom: has-azure-ad-ps-ref
ms.topic: conceptual
 
ms.date: 10/28/2024
 
ms.author: joflore
author: MicrosoftGuyJFlo
 
Many of the existing Microsoft cloud applications are included in the list of applications you can select from.
 
Administrators can assign a Conditional Access policy to these Microsoft cloud applications. Some apps like [Office 365](#office-365) and [Windows Azure Service Management API](#windows-azure-service-management-api) include multiple related child apps or services.
 
> [!IMPORTANT]
> Applications that are available to Conditional Access go through an onboarding and validation process. These applications don't include all Microsoft apps. Many applications are backend services that aren't meant to have policy directly applied to them. If you're looking for an application that is missing, you can contact the specific application team or make a request on [UserVoice](https://feedback.azure.com/d365community/forum/22920db1-ad25-ec11-b6e6-000d3a4f0789).
 
### Office 365
 
Create new authentication context definitions by selecting **New authentication context**. Organizations are limited to a total of 99 authentication context definitions **c1-c99**. Configure the following attributes:
 
- **Display name** is the name that is used to identify the authentication context in Microsoft Entra ID and across applications that consume authentication contexts. We recommend names that can be used across resources, like *trusted devices*, to reduce the number of authentication contexts needed. Having a reduced set limits the number of redirects and provides a better end to end-user experience.
ms.custom: has-azure-ad-ps-ref
ms.topic: conceptual
 
ms.date: 06/03/2025
 
ms.author: joflore
author: MicrosoftGuyJFlo
 
Many of the existing Microsoft cloud applications are included in the list of applications you can select from.
 
Administrators can assign a Conditional Access policy to cloud apps from Microsoft as long as the service principal appears in their tenant. Some apps like [Office 365](#office-365) and [Windows Azure Service Management API](#windows-azure-service-management-api) include multiple related child apps or services. When new supported Microsoft cloud applications are created, they appear in the app picker list.
 
> [!IMPORTANT]
> Applications that are available to Conditional Access have gone through an onboarding and validation process. This list doesn't include some backend services not meant to have policy directly applied to them. If you're looking for an application that is missing, you can contact the specific application team or make a request on [UserVoice](https://feedback.azure.com/d365community/forum/22920db1-ad25-ec11-b6e6-000d3a4f0789).
 
### Office 365
 
Create new authentication context definitions by selecting **New authentication context**. Organizations are limited to a total of 99 authentication context definitions **c1-c99**. Configure the following attributes:
 
- **Display name** is the name that is used to identify the authentication context in Microsoft Entra ID and across applications that consume authentication contexts. We recommend names that can be used across resources, like *trusted devices*, to reduce the number of authentication contexts needed. Having a reduced set limits the number of redirects and provides a better end to end-user experience.
Modified by shlipsey3 on Jun 4, 2025 3:04 AM
📖 View on learn.microsoft.com
+4 / -4 lines changed
Commit: Update copilot-entra-access-reviews.md
Changes:
Before
After
>
> This article is a work in progress. It will be updated with more information, methods, and examples before GA.
 
Access reviews in Microsoft Entra ID enable organizations to manage group memberships, application access, and role assignments effectively. Using the capabilities of Microsoft Security Copilot, administrators can now interact with access reviews data using natural language, enabling fast and actionable insights that reduce manual effort and enhance governance. This integration allows admins to explore, track, and analyze access reviews at scale by asking questions.
 
Specifically, this feature helps administrators;:
 
- Understand who approved access
- Identify reviewers who took no decisions
| Use Case | Example Prompts |
|----------|-----------------|
| Explore current configured access reviews in the tenant | *Show me top 10 access reviews with schedule, status, and metadata* |
| Get detailed info on a specific access review | *Get access review details for Finance M365 Groups Q2* |
| View access review decisions for a specific instance | *Who approved or denied access in the Q2 finance review?* |
| Track reviews assigned to a specific reviewer | *List reviews where Alex Chen is the assigned reviewer* |
| Identify decisions that went against AI recommendations | *Which access review decisions overrode AI-suggested actions?* |
 
- [What are access reviews?](/entra/id-governance/access-reviews-overview)
- [Create and manage downloadable access review history report in Microsoft Entra access reviews](/entra/id-governance/access-reviews-downloadable-review-history)
- [Prepare for an access review of users' access to an application](/entra/id-governance/access-reviews-application-preparation)
>
> This article is a work in progress. It will be updated with more information, methods, and examples before GA.
 
Access reviews in Microsoft Entra ID help organizations to more effectively manage group memberships, application access, and role assignments. Using the capabilities of Microsoft Security Copilot, administrators can now interact with access review data using natural language, enabling fast and actionable insights that reduce manual effort and enhance governance. This integration allows admins to explore, track, and analyze access reviews at scale by asking questions.
 
This feature helps administrators;:
 
- Understand who approved access
- Identify reviewers who took no decisions
| Use Case | Example Prompts |
|----------|-----------------|
| Explore current configured access reviews in the tenant | *Show me top 10 access reviews with schedule, status, and metadata* |
| Get detailed info on a specific access review | *Get access review details for Finance Microsoft 365 Groups Q2* |
| View access review decisions for a specific instance | *Who approved or denied access in the Q2 finance review?* |
| Track reviews assigned to a specific reviewer | *List reviews where Alex Chen is the assigned reviewer* |
| Identify decisions that went against AI recommendations | *Which access review decisions overrode AI-suggested actions?* |
 
- [What are access reviews?](/entra/id-governance/access-reviews-overview)
- [Create and manage downloadable access review history report in Microsoft Entra access reviews](/entra/id-governance/access-reviews-downloadable-review-history)
- [Prepare for an access review of users' access to an application](/entra/id-governance/access-reviews-application-preparation)
Modified by Shreya Goyal on Jun 4, 2025 7:50 PM
📖 View on learn.microsoft.com
+5 / -1 lines changed
Commit: Docs: clarify IDP/SP-initiated SSO and test setup for SD Worx gallery app
Changes:
Before
After
* Enable your users to be automatically signed-in to my.sdworx.com with their Microsoft Entra accounts.
* Manage your accounts in one central location.
 
You configure and test Microsoft Entra single sign-on for my.sdworx.com in a test environment. my.sdworx.com supports **IDP** initiated single sign-on.
 
> [!NOTE]
> Identifier of this application is a fixed string value so only one instance can be configured in one tenant.
 
 
 
 
* Enable your users to be automatically signed-in to my.sdworx.com with their Microsoft Entra accounts.
* Manage your accounts in one central location.
 
<!-- You configure and test Microsoft Entra single sign-on for my.sdworx.com in a test environment. my.sdworx.com supports **IDP** initiated single sign-on. -->
 
You configure and test Microsoft Entra single sign-on for my.sdworx.com in a test environment (my.acc.sdworx.com) but not by using this gallery app (import SP metadata, to be provided by your my.sdworx.com contact). my.sdworx.com supports **IDP** and **SP** initiated single sign-on.
When using **SP** initiated initiated single sign-on, only “email domain” realm discovery is supported, which means only company/enterprise email addresses are allowed (no private email addresses like hotmail.com, gmail.com, …)
 
> [!NOTE]
> Identifier of this application is a fixed string value so only one instance can be configured in one tenant.
Modified by John Flores on Jun 4, 2025 7:03 AM
📖 View on learn.microsoft.com
+4 / -2 lines changed
Commit: WIP
Changes:
Before
After
---
# Microsoft Security Copilot agents in Microsoft Entra
 
Microsoft Entra agents work seamlessly with [Microsoft Security Copilot](/copilot/security/microsoft-security-copilot). Microsoft Security Copilot agents automate repetitive tasks and reduce manual workloads. They enhance security and IT operations across cloud, data security and privacy, identity, and network security. These agents handle high-volume, time-consuming tasks by pairing data and code with an AI language model. They respond to user requests and system events, helping teams work more efficiently and focus on higher-impact tasks.
 
Agents fit naturally into existing workflows. You don't need special training or other licensing to use them. Agents utilize SCUs to operate just like other features in the product. They integrate seamlessly with Microsoft Security solutions and the broader supported partner ecosystem. Agents learn based on feedback and keep you in control on the actions it takes. They handle resource-intensive tasks like threat intelligence briefings, and Conditional Access optimization. With Microsoft Security Copilot agents, you can scale up your teams, people, and processes.
 
Microsoft Security Copilot agents offer significant benefits for security teams and IT operations by automating routine tasks and freeing up valuable time for teams to concentrate on strategic initiatives and complex problem-solving. This leads to improved operational efficiency, enhanced security and giving teams the ability to respond more swiftly to emerging threats. With Security Copilot agents, organizations can achieve greater scalability and resilience in their security and IT processes.
 
## Available agents
 
 
 
---
# Microsoft Security Copilot agents in Microsoft Entra
 
<!--- Microsoft Entra agents work seamlessly with [Microsoft Security Copilot](/copilot/security/microsoft-security-copilot). Microsoft Security Copilot agents automate repetitive tasks and reduce manual workloads. They enhance security and IT operations across cloud, data security and privacy, identity, and network security. These agents handle high-volume, time-consuming tasks by pairing data and code with an AI language model. They respond to user requests and system events, helping teams work more efficiently and focus on higher-impact tasks.
 
Agents fit naturally into existing workflows. You don't need special training or other licensing to use them. Agents utilize SCUs to operate just like other features in the product. They integrate seamlessly with Microsoft Security solutions and the broader supported partner ecosystem. Agents learn based on feedback and keep you in control on the actions it takes. They handle resource-intensive tasks like threat intelligence briefings, and Conditional Access optimization. With Microsoft Security Copilot agents, you can scale up your teams, people, and processes.
 
Microsoft Security Copilot agents offer significant benefits for security teams and IT operations by automating routine tasks and freeing up valuable time for teams to concentrate on strategic initiatives and complex problem-solving. This leads to improved operational efficiency, enhanced security and giving teams the ability to respond more swiftly to emerging threats. With Security Copilot agents, organizations can achieve greater scalability and resilience in their security and IT processes. --->
 
[!INCLUDE [agents-overview](~/../security-copilot/securityopilot.md]
 
## Available agents
 
Modified by Anna Huff on Jun 4, 2025 12:23 AM
📖 View on learn.microsoft.com
+3 / -3 lines changed
Commit: Apply suggestions from PR review
Changes:
Before
After
 
1. Set up Microsoft Entra Verified ID Service: using [Quick setup](verifiable-credentials-configure-tenant-quick.md) or [Advanced setup instructions](verifiable-credentials-configure-tenant.md).
>[!Note]
>For a multi-tenant model, IDV should explore setting up dedicated authorities if there is a 1:1 relationship required with the customer. Refer [Admin API](admin-api.md) section of the docs for creating authorities.
 
2. Set up a credential definition that defines what type of credentials you'll issue from the service – [Custom Credential](credential-design.md). Based on the scenario, select between ID token (for Open ID connect attestations from providers) or ID token hint (ISVs to use REST APIs to get the required attestations), self issued (user provided input), presentation or multiple attestations.
 
5. The end user starts the journey on the relying party application – in the example above, Contoso’s onboarding portal asks the user to prove their identity. If the user already has the required Verified ID for onboarding, they'll follow steps 1 through 4 in the diagram. If the user doesn’t have the required Verified ID, user has to launch the IDV offer URL from onboarding application to initiate the identity verification process.
The IDV and customer relying party need to build this redirection model. The IDV needs to identify that the user is coming to the IDV portal from a registered organization and isn't a SPAM request. The relying party needs to generate a “one-time” use url with a JWT token, for example: ```https://idvpartner.com/contoso/?token=jwt_token```
 
Note that The JWT token is signed with customer's relying party private key and the public key is shared with the IDV via an endpoint or via a scheduled process. The IDV needs to ensure that for the kickstart journey, it uses attributes from the JWT like org ID, request ID, mscv id, and expiry. Note [mscv](https://github.com/microsoft/CorrelationVector) is preferred for end-to-end troubleshooting. An example of the JWT could be as follows:
 
Header: Algorithm and Token type
```json
 
6. Upon successful completion, IDV kicks off Verified ID issuance flow and issues a Verified ID. At this point, user is presented with a deep link or QR code to **Add Card** in Microsoft Authenticator application. The IDV website receives a successful issuance callback from Verified ID service.
>[!Note]
> IDV partner must provide or build the required web experience where the identity of the user can be proofed in any way necessary as agreed between the relying party application and IDV partner. When the process is completed a list of values are collected according to the Verified ID Credential Type. These values (as “claims” parameter) are passed as part of the Verified ID issuance request API call. If the IDV is building this journey on a webapp, IDV needs to render it as a QR code or deep link. For further details, refer [Specify the Request Service REST API issuance request](issuance-request-api.md)
 
7. IDV redirects the user back to the customer’s relying party application.
 
1. Set up Microsoft Entra Verified ID Service: using [Quick setup](verifiable-credentials-configure-tenant-quick.md) or [Advanced setup instructions](verifiable-credentials-configure-tenant.md).
>[!Note]
>For a multi-tenant model, IDV should explore setting up dedicated authorities if there is a 1:1 relationship required with the customer. Refer to the [Admin API](admin-api.md) section of the docs for creating authorities.
 
2. Set up a credential definition that defines what type of credentials you'll issue from the service – [Custom Credential](credential-design.md). Based on the scenario, select between ID token (for Open ID connect attestations from providers) or ID token hint (ISVs to use REST APIs to get the required attestations), self issued (user provided input), presentation or multiple attestations.
 
5. The end user starts the journey on the relying party application – in the example above, Contoso’s onboarding portal asks the user to prove their identity. If the user already has the required Verified ID for onboarding, they'll follow steps 1 through 4 in the diagram. If the user doesn’t have the required Verified ID, user has to launch the IDV offer URL from onboarding application to initiate the identity verification process.
The IDV and customer relying party need to build this redirection model. The IDV needs to identify that the user is coming to the IDV portal from a registered organization and isn't a SPAM request. The relying party needs to generate a “one-time” use url with a JWT token, for example: ```https://idvpartner.com/contoso/?token=jwt_token```
 
Note that the JWT token is signed with customer's relying party private key and the public key is shared with the IDV via an endpoint or via a scheduled process. The IDV needs to ensure that for the kickstart journey, it uses attributes from the JWT like org ID, request ID, mscv ID, and expiry. Note that [mscv](https://github.com/microsoft/CorrelationVector) is preferred for end-to-end troubleshooting. An example of the JWT could be as follows:
 
Header: Algorithm and Token type
```json
 
6. Upon successful completion, IDV kicks off Verified ID issuance flow and issues a Verified ID. At this point, user is presented with a deep link or QR code to **Add Card** in Microsoft Authenticator application. The IDV website receives a successful issuance callback from Verified ID service.
>[!Note]
> IDV partner must provide or build the required web experience where the identity of the user can be proofed in any way necessary as agreed between the relying party application and IDV partner. When the process is completed a list of values are collected according to the Verified ID Credential Type. These values (as “claims” parameter) are passed as part of the Verified ID issuance request API call. If the IDV is building this journey on a webapp, IDV needs to render it as a QR code or deep link. For further details, refer to [Specify the Request Service REST API issuance request](issuance-request-api.md).
 
7. IDV redirects the user back to the customer’s relying party application.
Modified by Ortagus Winfrey on Jun 4, 2025 10:48 PM
📖 View on learn.microsoft.com
+1 / -1 lines changed
Commit: Dynamic Approval updates
Changes:
Before
After
 
# Externally determine the approval requirements for an access package using custom extensions (Preview)
 
In entitlement management, approvers for access package requests can either be directly assigned, or determined dynamically. While entitlement management natively supports dynamic approvers such as the requestor's manager, second-level manager, or sponsor from a connected organization, these options don't cover all scenarios. With [custom extensions](entitlement-management-logic-apps-integration.md) calling out to [Azure Logic Apps](/azure/logic-apps/logic-apps-overview), you're able to determine approval requirements for access packages at the time of request through an external system. With this external call, you're able to determine approval requirements based on each of the [ApprovalStage properties](/graph/api/resources/approvalstage?view=graph-rest-beta#properties). This article walks you through making a custom extension, its underlying Azure Logic App, setting its system-assigned identity and role in the catalog, editing the logic app action to perform business logic, and testing to see if it runs successfully.
 
 
## License requirements
 
# Externally determine the approval requirements for an access package using custom extensions (Preview)
 
In entitlement management, approvers for access package requests can either be directly assigned, or determined dynamically. While entitlement management natively supports dynamic approvers such as the requestor's manager, second-level manager, or sponsor from a connected organization, these options don't cover all scenarios. With [custom extensions](entitlement-management-logic-apps-integration.md) calling out to [Azure Logic Apps](/azure/logic-apps/logic-apps-overview), you're able to determine approval requirements for access packages at the time of request through an external system. For example, if the user requesting an access package is in a department where leadership has recently changed, dynamic approvals can query the system and assign the new department head as the approver. With this external call, you're able to determine approval requirements based on each of the [ApprovalStage properties](/graph/api/resources/approvalstage?view=graph-rest-beta#properties). This article walks you through making a custom extension, its underlying Azure Logic App, setting its system-assigned identity and role in the catalog, editing the logic app action to perform business logic, and testing to see if it runs successfully.
 
 
## License requirements
Modified by Alexander Filipin on Jun 4, 2025 11:44 AM
📖 View on learn.microsoft.com
+1 / -1 lines changed
Commit: Update cross-tenant-access-overview.md
Changes:
Before
After
 
- If you block access to all apps by default, users are unable to read emails encrypted with Microsoft Rights Management Service, also known as Office 365 Message Encryption (OME). To avoid this issue, we recommend configuring your outbound settings to allow your users to access this app ID: 00000012-0000-0000-c000-000000000000. If you allow only this application, access to all other apps is blocked by default.
 
- If an external organization requires MFA or Terms of Use (ToU) by Conditional Access policies, users might be blocked from registering MFA methods or consenting to ToU. To avoid this issue, configure outbound settings (home tenant) and inbound settings (resource tenant) to let users access app ID 0000000c-0000-0000-c000-000000000000 (Microsoft App Access Panel) for MFA registration and app ID d52792f4-ba38-424d-8140-ada5b883f293 (AAD Terms of Use) for ToU. The configuration of the outbound settings can be achieved via the Microsoft Entra admin center by selecting 'Add other applications' and providing the app ID. Due to a current user interface (UI) limitation the configuration of the inbound settings must be performed via [Microsoft Graph APIs](/graph/api/resources/crosstenantaccesspolicy-overview).
 
## Custom roles for managing cross-tenant access settings
<!--Added content as a reference. -->
 
- If you block access to all apps by default, users are unable to read emails encrypted with Microsoft Rights Management Service, also known as Office 365 Message Encryption (OME). To avoid this issue, we recommend configuring your outbound settings to allow your users to access this app ID: 00000012-0000-0000-c000-000000000000. If you allow only this application, access to all other apps is blocked by default.
 
- If an organization requires MFA or Terms of Use (ToU) by Conditional Access policies, users might be blocked from registering MFA methods or consenting to ToU. To avoid this issue, configure outbound settings (home tenant) and inbound settings (resource tenant) to let users access app ID 0000000c-0000-0000-c000-000000000000 (Microsoft App Access Panel) for MFA registration and app ID d52792f4-ba38-424d-8140-ada5b883f293 (AAD Terms of Use) for ToU. The configuration of the outbound settings can be achieved via the Microsoft Entra admin center by selecting 'Add other applications' and providing the app ID. Due to a current user interface (UI) limitation the configuration of the inbound settings must be performed via [Microsoft Graph APIs](/graph/api/resources/crosstenantaccesspolicy-overview).
 
## Custom roles for managing cross-tenant access settings
<!--Added content as a reference. -->
+1 / -1 lines changed
Commit: Learn Editor: Update reference-sla-performance.md
Changes:
Before
After
| February | 99.999% | 99.999% | 99.999% | 99.999% | 99.998% |
| March | 99.568% | 99.998% | 99.999% | 99.999% | 99.996% |
| April | 99.999% | 99.999% | 99.999% | 99.999% | 99.999%*|
| May | 99.999% | 99.999% | 99.999% | 99.999% | |
| June | 99.999% | 99.999% | 99.999% | 99.999% | |
| July | 99.999% | 99.999% | 99.999% | 99.999% | |
| August | 99.999% | 99.999% | 99.999% | 99.999% | |
| February | 99.999% | 99.999% | 99.999% | 99.999% | 99.998% |
| March | 99.568% | 99.998% | 99.999% | 99.999% | 99.996% |
| April | 99.999% | 99.999% | 99.999% | 99.999% | 99.999%*|
| May | 99.999% | 99.999% | 99.999% | 99.999% | 99.999%*|
| June | 99.999% | 99.999% | 99.999% | 99.999% | |
| July | 99.999% | 99.999% | 99.999% | 99.999% | |
| August | 99.999% | 99.999% | 99.999% | 99.999% | |
+1 / -1 lines changed
Commit: Update how-to-connect-health-agent-install.md
Changes:
Before
After
> If you have a highly locked-down and restricted environment, you need to add more URLs than the URLs the table lists for Internet Explorer enhanced security. Also add URLs that are listed in the table in the next section.
 
>[!IMPORTANT]
>If you installed Microsoft Entra Connect Sync using an account with the Hybrid Identity Administrator role, the agent will be in a disabled state. To activate the agent, you will need to re-install it using an account that is a Global Administrator.
 
### New versions of the agent and auto upgrade
 
> If you have a highly locked-down and restricted environment, you need to add more URLs than the URLs the table lists for Internet Explorer enhanced security. Also add URLs that are listed in the table in the next section.
 
>[!IMPORTANT]
>Microsoft Entra Connect Health now supports installation using the Hybrid Identity Administrator role. If you installed Microsoft Entra Connect Sync using an account with the role, the Entra Connect Health agent will automatically be in active state and you will not need to do a re-install using a Global Administrator account.
 
### New versions of the agent and auto upgrade
 
+1 / -1 lines changed
Commit: PIM Articles added
Changes:
Before
After
description: Learn how to troubleshoot system errors with roles in Microsoft Entra Privileged Identity Management (PIM).
 
author: billmath
manager: femila
ms.service: entra-id-governance
ms.topic: troubleshooting
ms.subservice: privileged-identity-management
description: Learn how to troubleshoot system errors with roles in Microsoft Entra Privileged Identity Management (PIM).
 
author: billmath
manager: pmwongera
ms.service: entra-id-governance
ms.topic: troubleshooting
ms.subservice: privileged-identity-management