πŸ“‹ Microsoft Entra Documentation Changes

Changes for June 6th 2025

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

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

πŸ“Š Summary

57
Total Commits
2
New Files
208
Modified Files
3
Deleted Files
23
Contributors

πŸ†• New Documentation Files

+237 lines added
Commit: slimming Overview, removed seperate new feeautre docs, collating into single doc for all scenarios
+84 lines added
Commit: WIP

πŸ“ Modified Documentation Files

Modified by Chris Werner on Jun 5, 2025 10:48 PM
πŸ“– View on learn.microsoft.com
+58 / -77 lines changed
Commit: patch up
Changes:
Before
After
---
title: Microsoft Security Copilot scenarios
description: Learn how to use Microsoft Security Copilot with Microsoft Entra identity scenarios
keywords: null
author: cilwerner
ms.author: cwerner
# Customer intent: As an identity administrator, I want to learn how to use Microsoft Security Copilot for a variety of Microsoft Entra scenarios so I can improve my organization's security posture.
---
 
# Microsoft Security Copilot capabilities
 
Microsoft Security Copilot is a powerful tool that can help you manage and secure your Microsoft Entra identity environment. This article describes how to use Microsoft Security Copilot with Microsoft Entra identity scenarios to enhance your identity protection efforts. Using this feature requires a tenant with Microsoft Security Copilot enabled.
 
## Key features
 
> [!NOTE]
>
> PLACEHOLDER FOR KEY FEATURES
 
The following key features are available in Microsoft Security Copilot with Microsoft Entra:
---
title: Microsoft Security Copilot scenarios in Microsoft Entra
description: Learn how to use Microsoft Security Copilot in the Microsoft Entra admin center for identity and security scenarios.
keywords: null
author: cilwerner
ms.author: cwerner
# Customer intent: As an identity administrator, I want to learn how to use Microsoft Security Copilot for a variety of Microsoft Entra scenarios so I can improve my organization's security posture.
---
 
# Microsoft Security Copilot scenarios in Microsoft Entra
 
Microsoft Security Copilot is a powerful tool that can help you manage and secure your Microsoft Entra identity environment. This article describes how to use Microsoft Security Copilot with Microsoft Entra in identity related scenarios to enhance your identity protection efforts. Using this feature requires a tenant with Microsoft Security Copilot enabled.
 
## Create Security Copilot prompts in the Microsoft Entra admin center (preview)
 
Security Copilot is a part of the Microsoft Entra admin center, and you can use it to create your own prompts. Security Copilot is launched from a globally available button in the menu bar. Choose from a set of starter prompts that appear at the top of the Security Copilot window or enter your own in the prompt bar to get started. Suggested prompts can appear after a response, which are predefined prompts that Security Copilot selects based on the prior response.
 
:::image type="content" source="./media/copilot-security-entra/security-copilot-entra-admin-center.png" alt-text="Screenshot that shows Security Copilot in the Microsoft Entra admin center.":::
 
Specific scenarios supported by Security Copilot embedded in Microsoft Entra skills include:
+28 / -16 lines changed
Commit: cleanup-images
Changes:
Before
After
---
# Microsoft Entra Conditional Access optimization agent with Microsoft Security Copilot
 
[!INCLUDE [copilot-security-optimization-agent](../../includes/copilot-security-optimization-agent.md)]
 
The Conditional Access optimization agent helps you ensure all users are protected by policy. It recommends policies and changes based on best practices aligned with [Zero Trust](/security/zero-trust/deploy/identity) and Microsoft's learnings.
 
In preview, the agent evaluates policies requiring multifactor authentication (MFA), enforces device based controls (device compliance, app protection policies, and Domain Joined Devices), and blocks legacy authentication and device code flow.
 
The agent also evaluates all existing enabled policies to propose potential consolidation of similar policies.
 
- On average, each agent run consumes less than one SCU.
- To activate the agent the first time, you need the [Security Administrator](../role-based-access-control/permissions-reference.md#security-administrator) or [Global Administrator](../role-based-access-control/permissions-reference.md#global-administrator) role during the preview.
- To interact with the agent and apply suggestions, you need the [Conditional Access Administrator](../role-based-access-control/permissions-reference.md#conditional-access-administrator) role.
 
- Device-based controls require [Microsoft Intune licenses](/intune/intune-service/fundamentals/licenses).
 
 
 
 
---
# Microsoft Entra Conditional Access optimization agent with Microsoft Security Copilot
 
 
The Conditional Access optimization agent helps you ensure all users are protected by policy. It recommends policies and changes based on best practices aligned with [Zero Trust](/security/zero-trust/deploy/identity) and Microsoft's learnings.
 
In preview, the Security Copilot agent evaluates policies requiring multifactor authentication (MFA), enforces device based controls (device compliance, app protection policies, and Domain Joined Devices), and blocks legacy authentication and device code flow.
 
The agent also evaluates all existing enabled policies to propose potential consolidation of similar policies.
 
- On average, each agent run consumes less than one SCU.
- To activate the agent the first time, you need the [Security Administrator](../role-based-access-control/permissions-reference.md#security-administrator) or [Global Administrator](../role-based-access-control/permissions-reference.md#global-administrator) role during the preview.
- To interact with the agent and apply suggestions, you need the [Conditional Access Administrator](../role-based-access-control/permissions-reference.md#conditional-access-administrator) role.
- For more information, see [Understand authentication in Microsoft Security Copilot](/copilot/security/authentication)
- Device-based controls require [Microsoft Intune licenses](/intune/intune-service/fundamentals/licenses).
- Review [Privacy and data security in Microsoft Security Copilot](/copilot/security/privacy-data-security)
 
### Limitations
 
- During the preview, avoid using an account to set up the agent that requires role activation with Privileged Identity Management (PIM). Using an account that doesn't have standing permissions might cause authentication failures for the agent.
Modified by Chris Werner on Jun 5, 2025 1:50 AM
πŸ“– View on learn.microsoft.com
+2 / -36 lines changed
Commit: slimming Overview, removed seperate new feeautre docs, collating into single doc for all scenarios
Changes:
Before
After
 
# Copilot in Microsoft Entra
 
**Applies to:**
 
- Microsoft Entra
 
[Microsoft Security Copilot](/security-copilot/microsoft-security-copilot) is a platform that brings together the power of AI and human expertise to help administrators and security teams respond to attacks faster and more effectively. Security Copilot is embedded in Microsoft Entra so you can investigate and resolve identity risks, assess identities and access with AI-driven intelligence, and complete complex tasks quickly. Copilot in Microsoft Entra (Copilot) gets insights from your Microsoft Entra users, groups, sign-in logs, audit logs, and more.
 
 
## Key features
 
Microsoft Entra brings the capabilities of Security Copilot to the Microsoft Entra admin center, enabling administrators and security teams to respond to identity threats quickly. Bringing AI to Microsoft Entra allows teams to understand risks immediately and determine remediation steps in a timely manner.
 
### Create Security Copilot prompts in the Microsoft Entra admin center (preview)
 
Security Copilot is a part of the Microsoft Entra admin center, use it to create your own prompts. Launch Security Copilot from a globally available button in the menu bar. Choose from a set of starter prompts that appear at the top of the Security Copilot window or enter your own in the prompt bar to get started. Suggested prompts may also appear after a response, these are predefined prompts that Security Copilot selects based on the prior response.
 
:::image type="content" source="./media/copilot-security-entra/security-copilot-entra-admin-center.png" alt-text="Screenshot that shows Security Copilot in the Microsoft Entra admin center.":::
 
 
# Copilot in Microsoft Entra
 
**Applies to:** Microsoft Entra ![Green circle with a white check mark symbol.](../media/common/applies-to-yes.png)
 
[Microsoft Security Copilot](/security-copilot/microsoft-security-copilot) is a platform that brings together the power of AI and human expertise to help administrators and security teams respond to attacks faster and more effectively. Security Copilot is embedded in Microsoft Entra so you can investigate and resolve identity risks, assess identities and access with AI-driven intelligence, and complete complex tasks quickly. Copilot in Microsoft Entra (Copilot) gets insights from your Microsoft Entra users, groups, sign-in logs, audit logs, and more.
 
 
## Key features
 
Microsoft Entra brings the capabilities of Security Copilot to the Microsoft Entra admin center, enabling administrators and security teams to respond to identity threats quickly. Bringing AI to Microsoft Entra allows teams to understand risks immediately and determine remediation steps in a timely manner. For more information about the key features, see [Copilot in Microsoft Entra](/entra/copilot-entra-security-scenarios).
 
## Enable the Security Copilot integration in Microsoft Entra
 
 
 
 
 
 
 
Modified by omondiatieno on Jun 5, 2025 12:44 AM
πŸ“– View on learn.microsoft.com
+20 / -1 lines changed
Commit: Add clarity or authorization and app consent policies
Changes:
Before
After
 
- A user account. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
- A [Privileged Role Administrator](~/identity/role-based-access-control/permissions-reference.md#privileged-role-administrator) role.
 
## Configure user consent settings
 
 
To configure user consent settings through the Microsoft Entra admin center:
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as a [Privileged Role Administrator](~/identity/role-based-access-control/permissions-reference.md#privileged-role-administrator).
 
1. Browse to **Entra ID** > **Enterprise apps** > **Consent and permissions** > **User consent settings**.
 
 
:::zone pivot="ms-powershell"
 
To choose which app consent policy governs user consent for applications, use the [Microsoft Graph PowerShell](/powershell/microsoftgraph/get-started?view=graph-powershell-1.0&preserve-view=true) module. The cmdlets used here are included in the [Microsoft.Graph.Identity.SignIns](https://www.powershellgallery.com/packages/Microsoft.Graph.Identity.SignIns) module.
 
Connect to Microsoft Graph PowerShell using the least-privilege permission needed. For reading the current user consent settings, use *Policy.Read.All*. For reading and changing the user consent settings, use *Policy.ReadWrite.Authorization*. You need to sign in as a [Privileged Role Administrator](~/identity/role-based-access-control/permissions-reference.md#privileged-role-administrator).
 
 
- A user account. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
- A [Privileged Role Administrator](~/identity/role-based-access-control/permissions-reference.md#privileged-role-administrator) role.
- A [Global Administrator](~/identity/role-based-access-control/permissions-reference.md#global-administrator) role is only required when using the Microsoft Entra admin center.
 
## Configure user consent settings
 
 
To configure user consent settings through the Microsoft Entra admin center:
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as a [Global Administrator](~/identity/role-based-access-control/permissions-reference.md#global-administrator).
 
1. Browse to **Entra ID** > **Enterprise apps** > **Consent and permissions** > **User consent settings**.
 
 
:::zone pivot="ms-powershell"
 
## Understand authorization and permission grant policies in Microsoft Graph PowerShell
 
To configure user consent settings programmatically using Microsoft Graph PowerShell, it's important to understand the distinction between the tenant-wide **authorization policy** and individual **permission grant policies**. The `authorizationPolicy`, retrieved using [Update-MgPolicyAuthorizationPolicy](https://learn.microsoft.com/powershell/module/microsoft.graph.identity.signins/update-mgpolicyauthorizationpolicy?view=graph-powershell-1.0) governs global settings such as whether users can consent to apps and which permission grant policies are assigned to the default user role. For example, you can disable user consent while still allowing developers to manage permissions for the apps they own by assigning only `ManagePermissionGrantsForOwnedResource.DeveloperConsent` in the `permissionGrantPoliciesAssigned` collection.
+17 / -2 lines changed
Commit: Updates
Changes:
Before
After
 
## Configure the logic app and corresponding business logic
 
With the Azure Logic App given the access package assignment manager role for the catalog, you must now go to logic app to edit it to communicate with Microsoft Entra and add your business logic. To do this, you'd do the following steps:
 
1. On the logic app created, go to **Development Tools** > **Logic app designer**.
 
1. On the Add an Action pane, select **HTTP**.
 
1. On the **HTTP** pane under Parameters, enter the following parameters:
- URI: https://graph.microsoft.com/beta@{triggerBody()?['CallbackUriPath']}
- Method: POST
- Body: Your own custom logic data based on the parameters you want to query for. For more information, see: [Call external HTTP or HTTPS endpoints from workflows in Azure Logic Apps](/azure/connectors/connectors-native-http?tabs=standard). For an example of the body action see: [HTTP action example](entitlement-management-dynamic-approval.md#http-action-example).
- Authentication Type: Managed identity
:::image type="content" source="media/entitlement-management-dynamic-approval/disable-asynchronous-pattern.png" alt-text="Screenshot of disabling asynchronous pattern in a logic app http call.":::
1. After you've made changes to the HTTP trigger, select **Save**.
 
## Verify the extension worked
 
To verify that the custom extension works, you can request access to the access package, and view the request details via **Requests** on the access package page by following these steps:
 
## Configure the logic app and corresponding business logic
 
With the Azure Logic App given the access package assignment manager role for the catalog, you must now go to logic app to edit it to communicate with Microsoft Entra. To do this, you'd do the following steps:
 
1. On the logic app created, go to **Development Tools** > **Logic app designer**.
 
1. On the Add an Action pane, select **HTTP**.
 
1. On the **HTTP** pane under Parameters, enter the following parameters:
- URI: https://graph.microsoft.com/v1.0@{triggerBody()?['CallbackUriPath']}
- Method: POST
- Body: Your own custom logic data based on the parameters you want to query for. For more information, see: [Call external HTTP or HTTPS endpoints from workflows in Azure Logic Apps](/azure/connectors/connectors-native-http?tabs=standard). For an example of the body action see: [HTTP action example](entitlement-management-dynamic-approval.md#http-action-example).
- Authentication Type: Managed identity
:::image type="content" source="media/entitlement-management-dynamic-approval/disable-asynchronous-pattern.png" alt-text="Screenshot of disabling asynchronous pattern in a logic app http call.":::
1. After you've made changes to the HTTP trigger, select **Save**.
 
## Add business logic to the logic app
 
With the logic app configured for communication with Microsoft Entra, you can now add what you want the app to do. Logic app actions are added to the body of the **HTTP** section you configured for the logic app. To edit this, do the following:
Modified by Jennifer Fields on Jun 5, 2025 6:53 AM
πŸ“– View on learn.microsoft.com
+2 / -10 lines changed
Commit: Removing mention of Microsoft Entra Permissions Management
Changes:
Before
After
ms.service: entra
ms.subservice: fundamentals
ms.topic: overview
ms.date: 04/25/2025
ms.author: barclayn
ms.custom: sfi-image-nochange
#Customer intent: As a user, I want an overview of the products and features available in the Microsoft Entra admin center and then be able to easily navigate to learn more about those products and features.
 
* [Credentials](~/verified-id/verifiable-credentials-configure-tenant-quick.md)
 
### Permissions Management
 
**Permissions Management** gives administrators and developers access to [Microsoft Entra Permissions Management](~/permissions-management/overview.md) solutions, including user identities, actions, and resources across multicloud infrastructure environments.
 
:::image type="content" source="./media/entra-admin-center/entra-admin-permissions-management.png" alt-text="Screenshot of the Microsoft Entra admin center Permissions Management menu.":::
 
For more information about configuring and managing Microsoft Entra Permissions Management solutions, see the [Quickstart guide to Microsoft Entra Permissions Management](~/permissions-management/permissions-management-quickstart-guide.md).
 
### Global Secure Access
 
ms.service: entra
ms.subservice: fundamentals
ms.topic: overview
ms.date: 06/04/2025
ms.author: barclayn
ms.custom: sfi-image-nochange
#Customer intent: As a user, I want an overview of the products and features available in the Microsoft Entra admin center and then be able to easily navigate to learn more about those products and features.
 
* [Credentials](~/verified-id/verifiable-credentials-configure-tenant-quick.md)
 
### Global Secure Access
 
**Global Secure Access** gives administrators and developers access to [Microsoft Entra Private Access](~/global-secure-access/overview-what-is-global-secure-access.md#microsoft-entra-private-access) and [Microsoft Entra Internet Access](~/global-secure-access/overview-what-is-global-secure-access.md#microsoft-entra-internet-access) solutions, including the Global Secure Access dashboard, clients, connectors, and monitoring.
## Related content
 
* [Find your tenant](./how-to-find-tenant.yml)
* [Create a new tenant](./create-new-tenant.md)
 
 
 
+3 / -7 lines changed
Commit: removing preview tag and updating table
Changes:
Before
After
---
title: Restricted management administrative units in Microsoft Entra ID (Preview)
description: Use restricted management administrative units for more sensitive resources in Microsoft Entra ID.
author: barclayn
manager: pmwongera
ms.service: entra-id
ms.topic: conceptual
ms.subservice: role-based-access-control
ms.date: 05/24/2025
ms.author: barclayn
ms.custom: oldportal, it-pro;, sfi-ga-nochange
---
 
# Restricted management administrative units in Microsoft Entra ID (Preview)
 
> [!IMPORTANT]
> Restricted management administrative units are currently in PREVIEW.
> See the [Product Terms](https://aka.ms/EntraPreviewsTermsOfUse) for legal terms that apply to features that are in beta, preview, or otherwise not yet released into general availability.
 
Restricted management administrative units allow you to protect specific objects in your tenant from modification by anyone other than a specific set of administrators that you designate. This allows you to meet security or compliance requirements without having to remove tenant-level role assignments from your administrators.
---
title: Restricted management administrative units in Microsoft Entra ID
description: Use restricted management administrative units for more sensitive resources in Microsoft Entra ID.
author: barclayn
manager: pmwongera
ms.service: entra-id
ms.topic: conceptual
ms.subservice: role-based-access-control
ms.date: 06/04/2025
ms.author: barclayn
ms.custom: oldportal, it-pro;, sfi-ga-nochange
---
 
# Restricted management administrative units in Microsoft Entra ID
 
Restricted management administrative units allow you to protect specific objects in your tenant from modification by anyone other than a specific set of administrators that you designate. This allows you to meet security or compliance requirements without having to remove tenant-level role assignments from your administrators.
 
 
 
 
Modified by Rhythm Mishra (HCL Technologies Corporate Services) on Jun 5, 2025 7:39 PM
πŸ“– View on learn.microsoft.com
+7 / -1 lines changed
Commit: changes made
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.
+6 / -1 lines changed
Commit: Update retire-service-principal-less-authentication.md
Changes:
Before
After
 
You must act **before March 31, 2026**, to avoid authentication failure of applications.
 
If you identified traffic using service principal-less authentication between **February 11th and March 11th, 2025**, it will continue to work until **March 2026**. However, any traffic that wasn't detected during this period or any new traffic starting after **March 11, 2025** will be blocked starting **April 2025**.
 
## Use sign-in logs to find service principal-less applications
 
First, you'll need to verify that access by the named applications to the resources listed is necessary. The application’s sign-in activity can be reviewed by the resource tenant’s administrator via [sign-in logs](../identity/monitoring-health/concept-sign-ins.md). The service principal ID of an application making a service principal-less authentication is shown as `00000000-0000-0000-0000-000000000000` in the sign-in logs of the resource tenant.β€―
 
1. Navigate to the [Microsoft Entra admin center](https://entra.microsoft.com/#home).
 
 
 
 
 
 
You must act **before March 31, 2026**, to avoid authentication failure of applications.
 
In February-March 2025, we froze most resource apps accessed by service principal-less client apps. We allowed traffic where the client app home tenant and resource tenant matched if it was observed between **February 11th and March 11th, 2025**, which will continue to work until March 2026. However, any traffic that was not identified during this period or new traffic after March 11th was blocked starting April 2025.
 
We are now addressing the remaining client apps. Starting late June/July 2025, service principal-less traffic observed between **June 16th and 27th, 2025** will be allowed until March 2026. Low-volume traffic will be excluded. This change only applies to a small set of first-party and third-party resource apps, including first-party apps such as EXO, AADGraph, and ARM.
 
## Use sign-in logs to find service principal-less applications
 
> [!NOTE]
> Action is only required for apps authenticating without a service principal found in the "Service principal sign-ins" (app-only) sign-in logs. *User* sign-in logs will include Microsoft applications and services that are authenticating without a service principal. Sign-ins and authentication without a service principal by Microsoft apps is expected, and no action is required by customers.
 
First, you'll need to verify that access by the named applications to the resources listed is necessary. The application’s sign-in activity can be reviewed by the resource tenant’s administrator via [sign-in logs](../identity/monitoring-health/concept-sign-ins.md). The service principal ID of an application making a service principal-less authentication is shown as `00000000-0000-0000-0000-000000000000` in the sign-in logs of the resource tenant.β€―
 
1. Navigate to the [Microsoft Entra admin center](https://entra.microsoft.com/#home).
+3 / -3 lines changed
Commit: Updates author/ms.author.
Changes:
Before
After
title: 'Microsoft Entra on-premises application provisioning architecture'
description: Presents an overview of on-premises application provisioning architecture.
 
author: billmath
manager: femila
ms.service: entra-id
ms.topic: overview
ms.date: 04/09/2025
ms.subservice: hybrid
ms.author: billmath
ms.collection: M365-identity-device-management
---
 
title: 'Microsoft Entra on-premises application provisioning architecture'
description: Presents an overview of on-premises application provisioning architecture.
 
author: kenwith
manager: dougeby
ms.service: entra-id
ms.topic: overview
ms.date: 04/09/2025
ms.subservice: hybrid
ms.author: kenwith
ms.collection: M365-identity-device-management
---
 
+3 / -3 lines changed
Commit: Updates author/ms.author.
Changes:
Before
After
title: Microsoft Entra provisioning to applications using custom connectors
description: This document describes how to configure Microsoft Entra ID to provision users with external systems that offer REST and SOAP APIs.
 
author: billmath
manager: femila
ms.service: entra-id
ms.subservice: app-provisioning
ms.topic: how-to
ms.date: 04/09/2025
ms.author: billmath
ms.reviewer: arvinh
---
 
title: Microsoft Entra provisioning to applications using custom connectors
description: This document describes how to configure Microsoft Entra ID to provision users with external systems that offer REST and SOAP APIs.
 
author: kenwith
manager: dougeby
ms.service: entra-id
ms.subservice: app-provisioning
ms.topic: how-to
ms.date: 04/09/2025
ms.author: kenwith
ms.reviewer: arvinh
---
 
+3 / -3 lines changed
Commit: Updates author/ms.author.
Changes:
Before
After
title: 'Troubleshooting issues with provisioning to on-premises applications'
description: Describes how to troubleshoot various issues you might encounter when you install and use the ECMA Connector Host.
 
author: billmath
manager: femila
ms.service: entra-id
ms.topic: troubleshooting
ms.date: 04/09/2025
ms.subservice: hybrid
ms.author: billmath
ms.collection: M365-identity-device-management
---
 
title: 'Troubleshooting issues with provisioning to on-premises applications'
description: Describes how to troubleshoot various issues you might encounter when you install and use the ECMA Connector Host.
 
author: kenwith
manager: dougeby
ms.service: entra-id
ms.topic: troubleshooting
ms.date: 04/09/2025
ms.subservice: hybrid
ms.author: kenwith
ms.collection: M365-identity-device-management
---
 
+3 / -3 lines changed
Commit: Updates author/ms.author.
Changes:
Before
After
title: Microsoft Entra provisioning to LDAP directories
description: This document describes how to configure Microsoft Entra ID to provision users into an LDAP directory.
 
author: billmath
manager: femila
ms.service: entra-id
ms.subservice: app-provisioning
ms.topic: how-to
ms.date: 04/09/2025
ms.author: billmath
ms.reviewer: arvinh
---
 
title: Microsoft Entra provisioning to LDAP directories
description: This document describes how to configure Microsoft Entra ID to provision users into an LDAP directory.
 
author: kenwith
manager: dougeby
ms.service: entra-id
ms.subservice: app-provisioning
ms.topic: how-to
ms.date: 04/09/2025
ms.author: kenwith
ms.reviewer: arvinh
---
 
+3 / -3 lines changed
Commit: Updates author/ms.author.
Changes:
Before
After
title: Preparing for Microsoft Entra provisioning to Active Directory Lightweight Directory Services
description: This document describes how to configure Microsoft Entra ID to provision users into Active Directory Lightweight Directory Services as an example of an LDAP directory.
 
author: billmath
manager: femila
ms.service: entra-id
ms.subservice: app-provisioning
ms.topic: how-to
ms.date: 04/09/2025
ms.author: billmath
ms.reviewer: arvinh
---
 
title: Preparing for Microsoft Entra provisioning to Active Directory Lightweight Directory Services
description: This document describes how to configure Microsoft Entra ID to provision users into Active Directory Lightweight Directory Services as an example of an LDAP directory.
 
author: kenwith
manager: dougeby
ms.service: entra-id
ms.subservice: app-provisioning
ms.topic: how-to
ms.date: 04/09/2025
ms.author: kenwith
ms.reviewer: arvinh
---
 
+3 / -3 lines changed
Commit: Updates author/ms.author.
Changes:
Before
After
title: 'Export a Microsoft Identity Manager connector for use with the Microsoft Entra ECMA Connector Host'
description: Describes how to create and export a connector from MIM Sync to be used with the Microsoft Entra ECMA Connector Host.
 
author: billmath
manager: femila
ms.service: entra-id
ms.topic: how-to
ms.date: 04/09/2025
ms.subservice: hybrid
ms.author: billmath
ms.collection: M365-identity-device-management
---
 
title: 'Export a Microsoft Identity Manager connector for use with the Microsoft Entra ECMA Connector Host'
description: Describes how to create and export a connector from MIM Sync to be used with the Microsoft Entra ECMA Connector Host.
 
author: kenwith
manager: dougeby
ms.service: entra-id
ms.topic: how-to
ms.date: 04/09/2025
ms.subservice: hybrid
ms.author: kenwith
ms.collection: M365-identity-device-management
---
 

πŸ—‘οΈ Deleted Documentation Files

DELETED docs/fundamentals/copilot-entra-recommendations.md
Deleted by Chris Werner on Jun 5, 2025 1:50 AM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/fundamentals/copilot-entra-recommendations
-63 lines removed
Commit: slimming Overview, removed seperate new feeautre docs, collating into single doc for all scenarios
DELETED docs/fundamentals/copilot-entra-access-reviews.md
Deleted by Chris Werner on Jun 5, 2025 1:50 AM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/fundamentals/copilot-entra-access-reviews
-54 lines removed
Commit: slimming Overview, removed seperate new feeautre docs, collating into single doc for all scenarios
DELETED docs/fundamentals/copilot-entra-entitlement-management.md
Deleted by Chris Werner on Jun 5, 2025 1:50 AM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/fundamentals/copilot-entra-entitlement-management
-53 lines removed
Commit: slimming Overview, removed seperate new feeautre docs, collating into single doc for all scenarios