๐Ÿ“‹ Microsoft Entra Documentation Changes

Changes for May 6th 2025

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

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

๐Ÿ“Š Summary

26
Total Commits
0
New Files
7
Modified Files
0
Deleted Files
7
Contributors

๐Ÿ“ Modified Documentation Files

Modified by Yoel Horvitz on May 5, 2025 3:40 PM
๐Ÿ“– View on learn.microsoft.com
+31 / -18 lines changed
Commit: Update custom-extension-overview.md
Changes:
Before
After
 
## Custom authentication event types
 
This section lists the custom authentication events in Microsoft Entra ID. For detailed information about the events, refer to the respective documentation.
 
### Token issuance start event
 
The token issuance start event, **OnTokenIssuanceStart** is triggered when a token is about to be issued to an application. It is an event type set up within a custom claims provider. The custom claims provider is a custom authentication extension that calls a REST API to fetch claims from external systems. A custom claims provider maps claims from external systems into tokens and can be assigned to one or many applications in your directory.
 
This video outlines the procedure of mapping claims from external systems into security tokens using Microsoft Entra custom claims provider.
 
> [!VIDEO https://www.youtube.com/embed/_CD3shvqpx4?si=cYvAO8CyXuI9YPiS]
 
For details, see [custom claims providers](custom-claims-provider-overview.md).
 
### Attribute collection start
 
Attribute collection start events can be used with custom authentication extensions to add logic before attributes are collected from a user. The **OnAttributeCollectionStart** event occurs at the beginning of the attribute collection step, before the attribute collection page renders. It lets you add actions such as prefilling values and displaying a blocking error.
 
> [!NOTE]
 
## Custom authentication event types
 
This section lists the custom authentication extensions events available in Microsoft Entra ID workforce and external tenants. For detailed information about the events, refer to the respective documentation.
 
|Event |Workforce tenant|External tenant|
|---------|---------|---------|
| [Token issuance start](#token-issuance-start-event) | :::image type="icon" source="./media/common/yes.png" border="false"::: | :::image type="icon" source="./media/common/yes.png" border="false"::: |
| [Attribute collection start](#attribute-collection-start)||:::image type="icon" source="./media/common/yes.png" border="false":::|
| [Attribute collection submit](#attribute-collection-submit)||:::image type="icon" source="./media/common/yes.png" border="false":::|
| [One time passcode send](#one-time-passcode-send)||:::image type="icon" source="./media/common/yes.png" border="false":::|
 
### Token issuance start
 
The token issuance start event, **OnTokenIssuanceStart** is triggered when a token is about to be issued to an application. It is an event type set up within a [custom claims provider](custom-claims-provider-overview.md). The custom claims provider is a custom authentication extension that calls a REST API to fetch claims from external systems. A custom claims provider maps claims from external systems into tokens and can be assigned to one or many applications in your directory.
 
> [!TIP]
> [![Try it now](./media/common/try-it-now.png)](https://woodgrovedemo.com/#usecase=TokenAugmentation)
>
> To try out this feature, go to the Woodgrove Groceries demo and start the โ€œAdd claims to security tokens from a REST APIโ€ use case.
+20 / -29 lines changed
Commit: Cross-cloud overview and configure updates
Changes:
Before
After
 
#### Clouds
 
Which clouds can cross-tenant synchronization be used in?
 
- Cross-tenant synchronization is supported within the commercial cloud and Azure Government.
- Cross-tenant synchronization isn't supported within the Microsoft Azure operated by 21Vianet cloud.
- Synchronization is only supported between two tenants in the same Azure cloud. For information about the relationship between the Azure Cloud environments and Microsoft 365 (GCC, GCCH), see [Microsoft 365 integration](/azure/security/fundamentals/feature-availability#microsoft-365-integration). Synchronization between commercial and GCC is supported.
- Cross-cloud synchronization (such as public cloud to Azure Government) isn't supported. This capability is currently being deployed in stages. You might see cross-cloud synchronization settings in the Microsoft Entra admin center or Azure portal. These settings are not yet functional and you shouldn't try to select these settings.
 
What cloud pairs are supported for cross-tenant synchronization?
 
 
[!INCLUDE [cross-tenant-synchronization-cloud-pairs-include](../../includes/cross-tenant-synchronization-cloud-pairs-include.md)]
 
#### Existing B2B users
 
Will cross-tenant synchronization manage existing B2B users?
 
- No. No changes are made to the external users previously managed by cross-tenant synchronization if the relationship is severed (for example, if the cross-tenant synchronization policy is deleted).
 
#### Clouds
 
Within the same cloud, which clouds can cross-tenant synchronization be used in?
 
- Cross-tenant synchronization is supported within the commercial cloud and Azure Government.
- Cross-tenant synchronization isn't supported within the Microsoft Azure operated by 21Vianet cloud.
 
What cloud pairs are supported for cross-tenant synchronization?
 
 
[!INCLUDE [cross-tenant-synchronization-cloud-pairs-include](../../includes/cross-tenant-synchronization-cloud-pairs-include.md)]
 
#### Cross-cloud synchronization
 
Is [cross-cloud synchronization](cross-tenant-synchronization-configure.md?pivots=cross-cloud-synchronization) supported?
 
- Cross-cloud synchronization (such as public cloud to Azure Government) is supported and is currently in preview.
- Cross-cloud synchronization is supported in the Azure commercial cloud, Azure Government cloud, and Azure operated by 21Vianet (Azure in China) cloud.
- For information about the relationship between the Azure Cloud environments and Microsoft 365 (GCC, GCCH), see [Microsoft 365 integration](/azure/security/fundamentals/feature-availability#microsoft-365-integration). Synchronization between commercial and GCC is supported.
+10 / -10 lines changed
Commit: Update custom-extension-email-otp-get-started.md
Changes:
Before
After
- A familiarity and understanding of the concepts covered in [custom authentication extensions](/entra/identity-platform/custom-extension-overview).
- An Azure subscription. If you don't have an existing Azure account, sign up for a [free trial](https://azure.microsoft.com/free/dotnet/) or use your [Visual Studio Subscription](https://visualstudio.microsoft.com/subscriptions/) benefits when you [create an account](https://account.windowsazure.com/Home/Index).
- A Microsoft Entra ID [external tenant](../external-id/customers/quickstart-tenant-setup.md).
- A mail relay service providers:
 
### [Azure Communication Services](#tab/azure-communication-services)
 
 
### 1.1 Create an HTTP trigger function
 
After the Azure Function app is created, create an HTTP trigger function. The HTTP trigger lets you invoke a function with an HTTP request. This HTTP trigger is referenced by your Microsoft Entra custom authentication extension.
 
1. Within your **Function App**, from the menu select **Functions**.
1. Select **Create function**.
 
## Step 2: Add connection strings to the Azure Function
 
Connection strings enable the Communication Services SDKs to connect and authenticate to Azure. For both Azure Communication Services and SendGrid You'll then need to add these connection strings to your Azure Function app as environment variables.
 
### [Azure Communication Services](#tab/azure-communication-services)
- A familiarity and understanding of the concepts covered in [custom authentication extensions](/entra/identity-platform/custom-extension-overview).
- An Azure subscription. If you don't have an existing Azure account, sign up for a [free trial](https://azure.microsoft.com/free/dotnet/) or use your [Visual Studio Subscription](https://visualstudio.microsoft.com/subscriptions/) benefits when you [create an account](https://account.windowsazure.com/Home/Index).
- A Microsoft Entra ID [external tenant](../external-id/customers/quickstart-tenant-setup.md).
- A mail relay service provider:
 
### [Azure Communication Services](#tab/azure-communication-services)
 
 
### 1.1 Create an HTTP trigger function
 
After the Azure Function app is created, create an HTTP trigger function. The HTTP trigger lets you invoke a function with an HTTP request. Your Microsoft Entra custom authentication extension links to this HTTP trigger function.
 
1. Within your **Function App**, from the menu select **Functions**.
1. Select **Create function**.
 
## Step 2: Add connection strings to the Azure Function
 
Connection strings enable your function app to connect and authenticate to the mail relay service. For both Azure Communication Services and SendGrid, add these connection strings to your Azure Function app as environment variables.
 
### [Azure Communication Services](#tab/azure-communication-services)
+12 / -4 lines changed
Commit: Cross-cloud overview and configure updates
Changes:
Before
After
 
::: zone-end
 
::: zone pivot="cross-cloud-synchronization"
 
> [!IMPORTANT]
> Cross-cloud synchronization is currently in PREVIEW.
> This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.
 
:::image type="content" source="./media/cross-tenant-synchronization-configure/configure-cross-cloud-diagram.png" alt-text="Diagram that shows cross-cloud synchronization between source tenant and target tenant." lightbox="./media/cross-tenant-synchronization-configure/configure-cross-cloud-diagram.png":::
 
## Supported cloud pairs
 
Cross-cloud synchronization supports these cloud pairs:
 
[!INCLUDE [cross-cloud-synchronization-pairs-include](../../includes/cross-cloud-synchronization-pairs-include.md)]
 
::: zone-end
 
## Learning objectives
 
::: zone-end
 
> [!IMPORTANT]
> Cross-cloud synchronization is currently in PREVIEW.
> This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.
 
:::image type="content" source="./media/cross-tenant-synchronization-configure/configure-cross-cloud-diagram.png" alt-text="Diagram that shows cross-cloud synchronization between source tenant and target tenant." lightbox="./media/cross-tenant-synchronization-configure/configure-cross-cloud-diagram.png":::
 
::: zone-end
 
## Supported cloud pairs
 
::: zone pivot="same-cloud-synchronization"
Cross-tenant synchronization supports these cloud pairs:
 
[!INCLUDE [cross-tenant-synchronization-cloud-pairs-include](../../includes/cross-tenant-synchronization-cloud-pairs-include.md)]
::: zone-end
 
::: zone pivot="cross-cloud-synchronization"
Modified by Pratik Jadhav on May 5, 2025 8:19 PM
๐Ÿ“– View on learn.microsoft.com
+2 / -2 lines changed
Commit: (AzureCXP) fixes MicrosoftDocs/entra-docs#427216
Changes:
Before
After
To configure the integration of Citrix ShareFile into Microsoft Entra ID, you need to add Citrix ShareFile from the gallery to your list of managed SaaS apps.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
1. In the **Add from the gallery** section, type **Citrix ShareFile** in the search box.
1. Select **Citrix ShareFile** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
 
 
## Related content
 
Once you configure Citrix ShareFile you can enforce session control, which protects exfiltration and infiltration of your organizationโ€™s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app).
To configure the integration of Citrix ShareFile into Microsoft Entra ID, you need to add Citrix ShareFile from the gallery to your list of managed SaaS apps.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
1. Browse to **Identity** > **Applications** > **Enterprise applications** > **New application**.
1. In the **Add from the gallery** section, type **Citrix ShareFile** in the search box.
1. Select **Citrix ShareFile** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
 
 
## Related content
 
Once you configure Citrix ShareFile you can enforce session control, which protects exfiltration and infiltration of your organizationโ€™s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app).
Modified by Arpad Gulyas on May 5, 2025 12:33 AM
๐Ÿ“– View on learn.microsoft.com
+2 / -2 lines changed
Commit: Update how-to-enable-multi-geo.md
Changes:
Before
After
Content-type: application/json
 
{
"name": "<Connector Group Name>"
"region: "japan"
}
```
## Related content
Content-type: application/json
 
{
"name": "<Connector Group Name>",
"region": "Japan"
}
```
## Related content
+1 / -1 lines changed
Commit: (AzureCXP) fixes MicrosoftDocs/entra-docs#427251
Changes:
Before
After
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com).
 
1. Browse to **Entra ID** > **Roles & admins**.
 
1. Use the **Service** filter to narrow down the list of roles.
 
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com).
 
1. Navigate to **Identity** > **Roles & admins** > **All roles**.
 
1. Use the **Service** filter to narrow down the list of roles.