πŸ“‹ Microsoft Entra Documentation Changes

Daily summary for changes since November 9th 2025, 7:19 PM PST

Report generated on November 10th 2025, 7:19 PM PST

πŸ“Š Summary

15
Total Commits
1
New Files
4
Modified Files
0
Deleted Files
8
Contributors

πŸ†• New Documentation Files

+50 lines added
Commit: sensitivity labels added

πŸ“ Modified Documentation Files

+7 / -1 lines changed
Commit: Update health alert notification configuration details
Changes:
Before
After
- The `Group.Read.All` permission is the least privileged permission required to *view groups*.
- The `HealthMonitoringAlert.Read.All` permission is required to *view the alerts using the Microsoft Graph API*.
- The `HealthMonitoringAlert.ReadWrite.All` permission is required to *view and modify the alerts using the Microsoft Graph API*.
- For a full list of roles, see [Least privileged role by task](../role-based-access-control/delegate-by-task.md#monitoring-and-health---audit-and-sign-in-logs-least-privileged-roles).
 
> [!NOTE]
> Newly onboarded tenants might not have enough data to generate alerts for about 30 days.
 
## Determine email notification recipients
 
To start receiving notifications, your application sends a `POST` request to the /`subscriptions` endpoint to subscribe to a specific resource, in this case, health monitoring alerts. Microsoft Graph then validates the request and confirms the subscription. Once the subscription is active, Microsoft Graph sends a notification to your designated endpoint whenever the subscribed resource is created. For more information, see [Microsoft Graph change notifications](/graph/change-notifications-overview).
 
After receiving a notification, you should investigate the alert either through the Microsoft Entra admin center or through the Microsoft Graph API. If you need to assess the alert's impact, we recommend either polling or introducing a short delay before calling the health monitoring alert API for impact assessment data to be available. For more information, see [How to investigate health scenario alerts](howto-investigate-health-scenario-alerts.md).
 
The following example shows a basic request to subscribe to changes to Health Monitoring alert changes.
## Related content
 
- [Set up notifications for changes in resource data](/graph/change-notifications-overview)
- [Configure email notifications for alerts](/graph/api/healthmonitoring-alertconfiguration-update?view=graph-rest-beta&preserve-view=true)
- The `Group.Read.All` permission is the least privileged permission required to *view groups*.
- The `HealthMonitoringAlert.Read.All` permission is required to *view the alerts using the Microsoft Graph API*.
- The `HealthMonitoringAlert.ReadWrite.All` permission is required to *view and modify the alerts using the Microsoft Graph API*.
- The `HealthMonitoringAlertConfig.Read.All` permission is required to *view the configured email notification using Microsoft Graph /reports/healthmonitoring/alertConfigurations/{alertType} API* or to *view the configured webhook notification using Microsoft Graph /subscriptions API*.
- The `HealthMonitoringAlertConfig.ReadWrite.All` permission is required to *view and modify email notification using Microsoft Graph /reports/healthmonitoring/alertConfigurations/{alertType} API* or to *view and modify the configured webhook notification using Microsoft Graph /subscriptions API*.
- For a full list of roles, see [Least privileged role by task](../role-based-access-control/delegate-by-task.md#monitoring-and-health---audit-and-sign-in-logs-least-privileged-roles).
 
> [!NOTE]
> Newly onboarded tenants might not have enough data to generate alerts for about 30 days.
> If you see error due to missing required Microsoft Graph permissions, to get more information about Micorosft Graph permisisons, see [Microsoft graph permissions](graph/permissions-overview).
 
## Determine email notification recipients
 
To start receiving notifications, your application sends a `POST` request to the /`subscriptions` endpoint to subscribe to a specific resource, in this case, health monitoring alerts. Microsoft Graph then validates the request and confirms the subscription. Once the subscription is active, Microsoft Graph sends a notification to your designated endpoint whenever the subscribed resource is created. For more information, see [Microsoft Graph change notifications](/graph/change-notifications-overview).
 
> [!NOTE]
> If you see error due to missing required Microsoft Graph permissions, to get more information about Micorosft Graph permisisons, see [Microsoft graph permissions](graph/permissions-overview).
 
After receiving a notification, you should investigate the alert either through the Microsoft Entra admin center or through the Microsoft Graph API. If you need to assess the alert's impact, we recommend either polling or introducing a short delay before calling the health monitoring alert API for impact assessment data to be available. For more information, see [How to investigate health scenario alerts](howto-investigate-health-scenario-alerts.md).
Modified by Ortagus Winfrey on Nov 10, 2025 6:23 PM
πŸ“– View on learn.microsoft.com
+2 / -2 lines changed
Commit: GA fix reprocess workflows
Changes:
Before
After
---
title: Reprocess workflow runs using Lifecycle Workflows (Preview)
description: This article guides a user on reprocessing workflow runs using Lifecycle Workflows
author: owinfreyATL
ms.author: owinfrey
#CustomerIntent: As a Lifecycle Workflow Administrator, I want to reprocess workflow runs so that I can quickly re-run workflows that may have failed.
---
 
# Reprocess workflow runs using Lifecycle Workflows (Preview)
 
Reprocessing workflows is a feature that allows workflows created using lifecycle workflows to be run again to ensure workflows operate as intended. This is useful when dealing with runs that failed for some reason. This article provides step-by-step instructions for reprocessing workflows using the Microsoft Entra admin center, enabling you to quickly and efficiently manage workflow runs for users or specific runs.
 
---
title: Reprocess workflow runs using Lifecycle Workflows
description: This article guides a user on reprocessing workflow runs using Lifecycle Workflows
author: owinfreyATL
ms.author: owinfrey
#CustomerIntent: As a Lifecycle Workflow Administrator, I want to reprocess workflow runs so that I can quickly re-run workflows that may have failed.
---
 
# Reprocess workflow runs using Lifecycle Workflows
 
Reprocessing workflows is a feature that allows workflows created using lifecycle workflows to be run again to ensure workflows operate as intended. This is useful when dealing with runs that failed for some reason. This article provides step-by-step instructions for reprocessing workflows using the Microsoft Entra admin center, enabling you to quickly and efficiently manage workflow runs for users or specific runs.
 
Modified by Stacy Chambers on Nov 10, 2025 7:35 PM
πŸ“– View on learn.microsoft.com
+1 / -1 lines changed
Commit: pencil edit
Changes:
Before
After
#CustomerIntent: As an identity governance administrator, I want to view sensitivity labels of groups so that I can maintain security of groups within my environment.
---
 
# Sensitivity Labels in Lifecycle Workflows
 
Maintaining and classifying secure data within your environment is an important part in maintaining a secure environment. Sensitivity labels from Microsoft Purview Information Protection let you classify and protect your organization's data, while making sure that user productivity and their ability to collaborate isn't hindered. With sensitivity labels in Lifecycle Workflows, administrators are able to quickly view the sensitivity labels of groups during creation, and editing, of workflow tasks.
 
#CustomerIntent: As an identity governance administrator, I want to view sensitivity labels of groups so that I can maintain security of groups within my environment.
---
 
# Sensitivity labels in Lifecycle Workflows
 
Maintaining and classifying secure data within your environment is an important part in maintaining a secure environment. Sensitivity labels from Microsoft Purview Information Protection let you classify and protect your organization's data, while making sure that user productivity and their ability to collaborate isn't hindered. With sensitivity labels in Lifecycle Workflows, administrators are able to quickly view the sensitivity labels of groups during creation, and editing, of workflow tasks.
 
+1 / -1 lines changed
Commit: Update docs/external-id/customers/how-to-configure-waf-integration.md
Changes:
Before
After
 
Once you’ve connected Cloudflare WAF with Microsoft Entra External ID, it’s important to test the configuration to ensure everything is working as expected.
 
:::image type="content" source="media\how-to-configure-cloudflare-integration\configuration-test.png" alt-text="Screenshot showing configuration test results":::
 
## Troubleshooting
 
 
Once you’ve connected Cloudflare WAF with Microsoft Entra External ID, it’s important to test the configuration to ensure everything is working as expected.
 
:::image type="content" source="media\how-to-configure-cloudflare-integration\configuration-test.png" alt-text="Screenshot showing configuration test results.":::
 
## Troubleshooting