πŸ“‹ Microsoft Entra Documentation Changes

Changes for June 11th 2025

Period: June 10th 2025, 12:00 AM to June 11th 2025, 12:00 AM

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

πŸ“Š Summary

71
Total Commits
2
New Files
55
Modified Files
7
Deleted Files
25
Contributors

πŸ†• New Documentation Files

+534 lines added
Commit: Adds initial draft.
+97 lines added
Commit: Updates which file is removed. Coexistence updated, integration is different and added it back.

πŸ“ Modified Documentation Files

+73 / -47 lines changed
Commit: Puts policy name in code tags.
Changes:
Before
After
 
1. **[Configuration 1: Microsoft Entra Private Access with Netskope Internet Access](#configuration-1-microsoft-entra-private-access-with-netskope-internet-access)**
 
In this scenario Global Secure Access handles private application traffic. Netskope only capture Internet traffic.
 
1. **[Configuration 2: Microsoft Entra Private Access with Netskope Private Access and Netskope Internet Access](#configuration-2-microsoft-entra-private-access-with-netskope-private-access-and-netskope-internet-access)**
 
 
1. **[Configuration 3: Microsoft Entra Microsoft Access with Netskope Private Access and Netskope Internet Access](#configuration-3-microsoft-entra-microsoft-access-with-netskope-private-access-and-netskope-internet-access)**
 
In this scenario Global Secure Access handles all Microsoft 365 traffic. Netskope handles private application and Internet traffic.
 
1. **[Configuration 4: Microsoft Entra Internet Access and Microsoft Entra Microsoft Access with Netskope Private Access](#configuration-4-microsoft-entra-internet-access-and-microsoft-entra-microsoft-access-and-with-netskope-private-access)**
 
 
## Prerequisites
 
To configure Microsoft and Netskope for a unified SASE solution, start by setting up Microsoft Entra Internet Access and Microsoft Entra Private Access. Next, configure Netskope Private Access and Internet Access. Finally, make sure to establish the required FQDN and IP bypasses to ensure smooth integration between the two platforms.
 
- Set up Microsoft Entra Internet Access and Microsoft Entra Private Access. These products make up the Global Secure Access solution.
 
1. **[Configuration 1: Microsoft Entra Private Access with Netskope Internet Access](#configuration-1-microsoft-entra-private-access-with-netskope-internet-access)**
 
In this scenario, Global Secure Access handles private application traffic. Netskope only capture Internet traffic.
 
1. **[Configuration 2: Microsoft Entra Private Access with Netskope Private Access and Netskope Internet Access](#configuration-2-microsoft-entra-private-access-with-netskope-private-access-and-netskope-internet-access)**
 
 
1. **[Configuration 3: Microsoft Entra Microsoft Access with Netskope Private Access and Netskope Internet Access](#configuration-3-microsoft-entra-microsoft-access-with-netskope-private-access-and-netskope-internet-access)**
 
In this scenario, Global Secure Access handles all Microsoft 365 traffic. Netskope handles private application and Internet traffic.
 
1. **[Configuration 4: Microsoft Entra Internet Access and Microsoft Entra Microsoft Access with Netskope Private Access](#configuration-4-microsoft-entra-internet-access-and-microsoft-entra-microsoft-access-and-with-netskope-private-access)**
 
 
## Prerequisites
 
To configure Microsoft and Netskope for a unified SASE solution, start by setting up Microsoft Entra Internet Access and Microsoft Entra Private Access. Next, configure Netskope Private Access and Internet Access. Finally, make sure to establish the required Fully Qualified Domain Name (FQDN) and IP bypasses to ensure smooth integration between the two platforms.
 
- Set up Microsoft Entra Internet Access and Microsoft Entra Private Access. These products make up the Global Secure Access solution.
+30 / -7 lines changed
Commit: Adding two more best practices
Changes:
Before
After
 
This article describes security best practices for the following application properties:
 
- Redirect URI
- Access tokens (used for implicit flows)
- Certificates and secrets
- Application ID URI
- Application ownership
 
## Credentials (including certificates and secrets)
- Monitor your production pipelines to prevent credentials of any kind from being committed into code repositories. [Credential Scanner](/previous-versions/azure/security/develop/security-code-analysis-overview#credential-scanner) is a static analysis tool that can be used to detect credentials (and other sensitive content) in source code and build output.
 
 
## Redirect URI
 
It's important to keep Redirect URIs of your application up to date. Under **Authentication** for the application in the Azure portal, a platform must be selected for the application and then the **Redirect URI** property can be defined.
 
- Don't use wildcard reply URLs or insecure URI schemes such as http, or URN.
- Keep the list small. Trim any unnecessary URIs. If possible, update URLs from Http to Https.
 
 
This article describes security best practices for the following application properties:
 
- Credentials
- Redirect URIs
- Implicit flow configuration
- Application ID URI (a.k.a. identifier URI)
- Access token version
- Application instance lock
- Application ownership
 
## Credentials (including certificates and secrets)
- Monitor your production pipelines to prevent credentials of any kind from being committed into code repositories. [Credential Scanner](/previous-versions/azure/security/develop/security-code-analysis-overview#credential-scanner) is a static analysis tool that can be used to detect credentials (and other sensitive content) in source code and build output.
 
 
## Redirect URIs
 
It's important to keep Redirect URIs of your application up to date. Under **Authentication** for the application in the Azure portal, a platform must be selected for the application and then the **Redirect URI** property can be defined.
 
- Don't use wildcard reply URLs or insecure URI schemes such as http, or URN.
Modified by Michele Martin on Jun 10, 2025 7:31 AM
πŸ“– View on learn.microsoft.com
+16 / -17 lines changed
Commit: update security content
Changes:
Before
After
---
title: Security features in external tenants
description: Learn about security features and fundamentals for Microsoft Entra External ID customer identity and access management (CIAM) in external tenant configurations.
ms.author: cmulligan
 
Microsoft Entra External ID external tenants include several baseline security features to help immediately secure customer data. Default settings provide initial protection against threats like brute force attacks and network layer attacks. These protections serve as a starting point as you develop your own identity security plan and add Microsoft Entra premium security features.
 
## NEW
 
## Built-in Security Controls
 
When you create a Microsoft Entra External ID external tenant, core security features are enabled by default. These controls are designed to protect applications from various cyber threats, ensuring robust security for external-facing applications.
 
|Feature Name |Description |
|--------------|-------------|
|Brute Force Protection | Helps mitigate brute force attacks by limiting the number of login attempts. |
|Common Networking HTTP Protection | Provides protection against common networking HTTP threats. |
|Account Protection | Ensures accounts are protected from unauthorized access. |
|Access Control | Controls access to applications and resources. |
---
title: Security Features in External Tenants
description: Learn about security features and fundamentals for Microsoft Entra External ID customer identity and access management (CIAM) in external tenant configurations.
ms.author: cmulligan
 
Microsoft Entra External ID external tenants include several baseline security features to help immediately secure customer data. Default settings provide initial protection against threats like brute force attacks and network layer attacks. These protections serve as a starting point as you develop your own identity security plan and add Microsoft Entra premium security features.
 
## Built-in security controls
 
In newly created external tenants, the following core security features are enabled by default to help protect applications from various cyber threats.
 
|Feature Name |Description |
|--------------|-------------|
|Brute force protection | Mitigates brute force attacks by limiting the number of login attempts to prevent unauthorized access through repeated password guessing. |
|Common networking HTTP Protection | Provides protection against common network-layer attacks and timing-based attacks, protecting against attempts to overwhelm your service with excessive requests.|
|Account Protection | Ensures accounts are protected from unauthorized access to safeguard user data and prevent account compromise. |
|Access Control | Controls access to applications and resources, ensuring only authorized users can access sensitive information. |
## Real-time and offline protection
+17 / -14 lines changed
Commit: PM-updates
Changes:
Before
After
ms.author: joflore
author: MicrosoftGuyJFlo
 
ms.date: 06/06/2025
 
ms.service: entra-id
ms.subservice: conditional-access
 
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.
 
- You must have available [security compute units (SCU)](/copilot/security/manage-usage).
- 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).
ms.author: joflore
author: MicrosoftGuyJFlo
 
ms.date: 06/09/2025
 
ms.service: entra-id
ms.subservice: conditional-access
 
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 Conditional Access optimization agent evaluates policies such as requiring multifactor authentication (MFA), enforcing device based controls (device compliance, app protection policies, and domain-joined devices), and blocking legacy authentication and device code flow.
 
The agent also evaluates all existing enabled policies to propose potential consolidation of similar policies.
 
- You must have available [security compute units (SCU)](/copilot/security/manage-usage).
- 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.
- You can assign [Conditional Access Administrators](../role-based-access-control/permissions-reference.md#conditional-access-administrator) with Security Copilot access, which gives your Conditional Access Administrators the ability to use the agent as well.
- For more information, see [Assign Security Copilot access](/copilot/security/authentication#assign-security-copilot-access)
- Device-based controls require [Microsoft Intune licenses](/intune/intune-service/fundamentals/licenses).
+14 / -14 lines changed
Commit: Adding in PM updates.
Changes:
Before
After
title: Integrate Darwinbox HR With Microsoft Entra ID
description: Learn how to integrate Darwinbox HR with Microsoft Entra ID to automate user provisioning, manage lifecycle workflows, and streamline HR-driven processes.
author: jenniferf-skc
manager: femila
ms.reviewer: rahuln3223
ms.service: entra-id
ms.subservice: saas-apps
ms.topic: how-to
ms.date: 05/07/2025
ms.author: jfields
ms.custom: ai-gen-description
ai-usage: ai-assisted
 
For detailed guidance on how to integrate your Darwinbox environment, reference the Dawinbox guide here. Select the Help docs link next to the application name.
 
Here are the high-level steps for configuring the app integration with Microsoft Entra ID in the Darwinbox Portal:
 
 
## Install connectors in Darwinbox Studio
Open Darwinbox studio and navigate to Connector Library. Search for and install the β€œMicrosoft” and β€œMicrosoft Entra” connectors:
title: Integrate Darwinbox HR With Microsoft Entra ID
description: Learn how to integrate Darwinbox HR with Microsoft Entra ID to automate user provisioning, manage lifecycle workflows, and streamline HR-driven processes.
author: jenniferf-skc
manager: pmwongera
ms.reviewer: cmmdesai
ms.service: entra-id
ms.subservice: saas-apps
ms.topic: how-to
ms.date: 06/09/2025
ms.author: jfields
ms.custom: ai-gen-description
ai-usage: ai-assisted
 
For detailed guidance on how to integrate your Darwinbox environment, reference the Dawinbox guide here. Select the Help docs link next to the application name.
 
Follow these high-level steps for configuring the app integration with Microsoft Entra ID in the Darwinbox Portal.
 
 
## Install connectors in Darwinbox Studio
Open Darwinbox studio and navigate to **Connector Library**. Search for and install the **Microsoft** and **Microsoft Entra** connectors
Modified by Henry Mbugua on Jun 10, 2025 6:40 PM
πŸ“– View on learn.microsoft.com
+16 / -11 lines changed
Commit: What's new - May 2025
Changes:
Before
After
 
Welcome to what's new in the Microsoft identity platform documentation. This article lists new articles that were added or had significant updates in the last three months.
 
## April 2025
 
### New articles
- [Tutorial: Prepare a JavaScript single-page application for authentication](tutorial-single-page-app-javascript-prepare-app.md) - The tutorial was updated with the latest code sample.
- [Understand the app manifest (Microsoft Graph format)](reference-microsoft-graph-app-manifest.md) - The update improved content clarity.
- [Web app that signs in users: Sign-in and sign out](scenario-web-app-sign-user-sign-in.md) - The update improved content clarity.
 
 
## February 2025
 
### New articles
 
- [Best practices to protect frontline workers](security-best-practices-for-frontline-workers.md) - Best Practices to Protect Frontline Workers
 
### Updated articles
 
- [Microsoft identity platform and OAuth 2.0 Resource Owner Password Credentials](v2-oauth-ropc.md) - Added clarity to the content
 
Welcome to what's new in the Microsoft identity platform documentation. This article lists new articles that were added or had significant updates in the last three months.
 
## May 2025
 
### New articles
 
- [Email OTP send event reference](custom-extension-email-otp-send-data.md)
 
### Updated articles
 
- [Custom claims provider reference](custom-claims-provider-reference.md) - The update improved content clarity.
- [Application configuration options](msal-client-application-configuration.md) - The update improved content clarity.
- [Custom authentication extensions overview](custom-extension-overview.md) - The update improved content clarity.
- [Single-page application: Acquire a token to call an API](scenario-spa-acquire-token.md) - [DevEx] The update improved content clarity.
- [Single-page application: Code configuration](scenario-spa-app-configuration.md) - [DevEx] The update improved content clarity.
- [Single-page application: Add sign-in and sign-out code](scenario-spa-sign-in.md) - [DevEx] The update improved content clarity.
- [Microsoft Entra authentication and authorization error codes](reference-error-codes.md) - Add and partially update error code
 
## April 2025
Modified by Ramsay Malange on Jun 10, 2025 6:50 AM
πŸ“– View on learn.microsoft.com
+7 / -11 lines changed
Commit: Update appneta-tutorial.md with new SSO Config Attributes
Changes:
Before
After
`https://<subdomain>.pm.appneta.com`
 
b. In the Reply URL (Assertion Consumer Service URL) field, enter:
`https://sso.connect.pingidentity.com/sso/sp/ACS.saml2`
 
> [!NOTE]
> The Sign-on URL value above is an example. Update this value with the actual Sign-On URL. Contact [AppNeta Performance Manager customer support team](mailto:[email protected]) to get this value. You can also refer to the patterns shown in the **Basic SAML Configuration** section.
 
| Name | Source Attribute |
| --------- | ---------------------- |
| firstName | user.givenname |
| lastName | user.surname |
| email | user.userprincipalname |
| name | user.userprincipalname |
| groups | user.assignedroles |
| phone | user.telephonenumber |
| title | user.jobtitle |
| | |
 
1. In order to properly pass along your ”groups” SAML assertions, you need to configure App roles and set the value to match the role mappings that are set within AppNeta Performance Manager. Under **Entra ID** > **App registrations**, select **Appneta Performance Manager**.
`https://<subdomain>.pm.appneta.com`
 
b. In the Reply URL (Assertion Consumer Service URL) field, enter:
`https://access.broadcom.com/default/saml/v1/sp/acs`
 
> [!NOTE]
> The Sign-on URL value above is an example. Update this value with the actual Sign-On URL. Contact [AppNeta Performance Manager customer support team](mailto:[email protected]) to get this value. You can also refer to the patterns shown in the **Basic SAML Configuration** section.
 
| Name | Source Attribute |
| --------- | ---------------------- |
| FirstName | user.givenname |
| LastName | user.surname |
| Email | user.userprincipalname |
| Groups | user.assignedroles |
 
1. In order to properly pass along your ”Groups” SAML assertions, you need to configure App roles and set the value to match the role mappings that are set within AppNeta Performance Manager. Under **Entra ID** > **App registrations**, select **Appneta Performance Manager**.
 
![Screenshot that shows the App Registrations with Appneta Performance Manager at the bottom.](./media/appneta-tutorial/app-registrations.png)
 
 
+12 / -4 lines changed
Commit: replaced table version 163 with 169
Changes:
Before
After
---
title: Microsoft Entra ID attestation for FIDO2 security key vendors
description: Explains requirements to prepare FIDO2 hardware for attestation with Microsoft Entra ID
ms.date: 05/21/2025
ms.service: entra-id
ms.subservice: authentication
author: justinha
 
## FIDO2 security keys eligible for attestation with Microsoft Entra ID
 
The following table includes each FIDO2 security key model listed in MDS version 163 that's eligible for attestation with Microsoft Entra ID. For each model, the table shows its Authenticator Attestation Globally Unique Identifier (AAGUID) and feature capabilities.
 
Description|AAGUID|Bio|USB|NFC|BLE
-----------|------|---|---|---|---
Cryptnox FIDO2|9c835346-796b-4c27-8898-d6032f515cc5|&#10060;|&#10060;|&#x2705;|&#10060;
Cryptnox FIDO2.1|1d1b4e33-76a1-47fb-97a0-14b10d0933f1|&#10060;|&#10060;|&#x2705;|&#10060;
Dapple Authenticator from Dapple Security Inc.|6dae43be-af9c-417b-8b9f-1b611168ec60|&#10060;|&#10060;|&#10060;|&#10060;
Deepnet SafeKey/Classic (NFC)|b12eac35-586c-4809-a4b1-d81af6c305cf|&#10060;|&#10060;|&#10060;|&#10060;
Deepnet SafeKey/Classic (USB)|b9f6b7b6-f929-4189-bca9-dd951240c132|&#10060;|&#10060;|&#10060;|&#10060;
Egomet FIDO2 Authenticator for Android|1105e4ed-af1d-02ff-ffff-ffffffffffff|&#x2705;|&#10060;|&#10060;|&#10060;
---
title: Microsoft Entra ID attestation for FIDO2 security key vendors
description: Explains requirements to prepare FIDO2 hardware for attestation with Microsoft Entra ID
ms.date: 06/09/2025
ms.service: entra-id
ms.subservice: authentication
author: justinha
 
## FIDO2 security keys eligible for attestation with Microsoft Entra ID
 
The following table includes each FIDO2 security key model listed in MDS version 169 that's eligible for attestation with Microsoft Entra ID. For each model, the table shows its Authenticator Attestation Globally Unique Identifier (AAGUID) and feature capabilities.
 
 
Description|AAGUID|Bio|USB|NFC|BLE
-----------|------|---|---|---|---
Cryptnox FIDO2|9c835346-796b-4c27-8898-d6032f515cc5|&#10060;|&#10060;|&#x2705;|&#10060;
Cryptnox FIDO2.1|1d1b4e33-76a1-47fb-97a0-14b10d0933f1|&#10060;|&#10060;|&#x2705;|&#10060;
Dapple Authenticator from Dapple Security Inc.|6dae43be-af9c-417b-8b9f-1b611168ec60|&#10060;|&#10060;|&#10060;|&#10060;
Deepnet SafeKey/Classic (FP)|e41b42a3-60ac-4afb-8757-a98f2d7f6c9f|&#x2705;|&#10060;|&#10060;|&#10060;
Deepnet SafeKey/Classic (NFC)|b12eac35-586c-4809-a4b1-d81af6c305cf|&#10060;|&#10060;|&#10060;|&#10060;
+6 / -5 lines changed
Commit: Update copilot-entra-security-scenarios.md
Changes:
Before
After
author: cilwerner
ms.author: cwerner
manager: pmwongera
ms.date: 05/30/2025
ms.topic: conceptual
ms.service: entra
ms.custom: microsoft-copilot
 
### Investigate alerts in Scenario Health Monitoring
 
External Health Monitoring is a feature in Microsoft Entra that analyzes scenario-specific metrics for each tenant, detects anomalies, and raises alerts. These alerts are sent via the Microsoft Graph API and displayed in the Microsoft Entra admin center UI, enabling tenant admins to proactively investigate and address issues.
 
For example, in the multifactor authentication (MFA) scenario, External Health Monitoring tracks metrics such as sign-in success rate, sign-in failure rate, and failure count. If there's a spike in failures, an alert is raised to notify the tenant admin, who can then take appropriate action to resolve the issue.
 
Using this feature requires [Microsoft Entra ID P2 licenses](/entra/id-protection/overview-identity-protection#license-requirements) and a public cloud tenant.
 
The following roles can use this feature:
 
- [Security Administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator)
- [Security Reader](/entra/identity/role-based-access-control/permissions-reference#security-reader)
author: cilwerner
ms.author: cwerner
manager: pmwongera
ms.date: 06/09/2025
ms.topic: conceptual
ms.service: entra
ms.custom: microsoft-copilot
 
### Investigate alerts in Scenario Health Monitoring
 
External Health Monitoring is a feature in Microsoft Entra that analyzes scenario-specific metrics for each tenant, detects anomalies, and raises alerts. These alerts are sent via the Microsoft Graph API and displayed in the Microsoft Entra admin center UI, enabling tenant admins to proactively investigate and address issues. For example, in the multifactor authentication (MFA) scenario, External Health Monitoring tracks metrics such as sign-in success rate, sign-in failure rate, and failure count. If there's a spike in failures, an alert is raised to notify the tenant admin, who can then take appropriate action to resolve the issue.
 
Using this feature requires [Microsoft Entra ID P2 licenses](/entra/id-protection/overview-identity-protection#license-requirements) and a public cloud tenant.
 
The following roles can use this feature:
 
- [Reports Reader](/entra/identity/role-based-access-control/permissions-reference#reports-reader)
- [Helpdesk Administrator](/entra/identity/role-based-access-control/permissions-reference#helpdesk-administrator)
- [Security Reader](/entra/identity/role-based-access-control/permissions-reference#security-reader)
- [Security Operator](/entra/identity/role-based-access-control/permissions-reference#security-operator)
Modified by shlipsey3 on Jun 10, 2025 6:11 AM
πŸ“– View on learn.microsoft.com
+2 / -8 lines changed
Commit: 21774
Changes:
Before
After
# userimpact: Low
# implementationcost: Low
---
When Microsoft services applications (service principals with the owner organization ID "f8cdef31-a31e-4b4a-93e4-5f571e91255a") have credentials configured in your tenant, it might create potential attack vectors that threat actors can exploit. If credentials were added by administrator and no longer needed, they can become a target of attackers; although less likely when proper preventive and detective controls are in place on privileged activities, credentials can also be added maliciously by threat actors. In either case, threat actors can use these credentials to authenticate as the service principal, gaining the same permissions and access rights as the Microsoft service application. This initial access can lead to privilege escalation if the application has high-level permissions, allowing lateral movement across the tenant. Attackers can then proceed to data exfiltration or persistence establishment through creating additional backdoor credentials.
 
 
Risk Level: High – Wide spread impact if credentials are misused
 
User Impact: Low - Users should not be affected on their daily usage of Microsoft Services
 
Implementation Cost: Low – Effort is targeted and remediated
 
**Remediation action**
 
# userimpact: Low
# implementationcost: Low
---
Microsoft services applications that operate in your tenant are identified as service principals with the owner organization ID "f8cdef31-a31e-4b4a-93e4-5f571e91255a". When these service principals have credentials configured in your tenant, they might create potential attack vectors that threat actors can exploit. If the credentials were added by an administrator and are no longer needed, they can become a target for attackers. Although less likely when proper preventive and detective controls are in place on privileged activities, credentials can also be added maliciously by threat actors. In either case, threat actors can use these credentials to authenticate as the service principal, gaining the same permissions and access rights as the Microsoft service application. This initial access can lead to privilege escalation if the application has high-level permissions, allowing lateral movement across the tenant. Attackers can then proceed to data exfiltration or persistence establishment through creating additional backdoor credentials.
 
When credentials (like client secrets or certificates) are configured for these service principals in your tenant, it means someone - either an administrator or a malicious actor - has enabled them to authenticate independently within your environment. These credentials should be investigated to determine their legitimacy and necessity. If they are no longer needed, they should be removed to reduce the risk. If they are still required, consider using OAuth2 permissions instead of credentials for better security practices.
 
**Remediation action**
 
 
 
 
 
 
 
+3 / -4 lines changed
Commit: Updating with PM edits.
Changes:
Before
After
title: Provision custom security attributes from HR sources
description: Learn how to provision custom security attributes from HR sources.
author: jenniferf-skc
manager: femila
ms.service: entra-id
ms.subservice: app-provisioning
ms.topic: troubleshooting
ms.date: 04/30/2025
ms.author: jfields
ms.reviewer: chmutali
---
 
## Known limitations
 
- The provisioning service only supports setting custom security attributes of type `String`.
- Provisioning custom security attributes of type `Integer` and `Boolean` isn't supported.
- Provisioning multi-valued custom security attributes isn't supported.
- Provisioning deactivated custom security attributes isn't supported.
- With the [Attribute Log Reader](~/identity/role-based-access-control/permissions-reference.md#attribute-log-reader) role, you can't view the custom security attribute value in the provisioning logs.
title: Provision custom security attributes from HR sources
description: Learn how to provision custom security attributes from HR sources.
author: jenniferf-skc
manager: pmwongera
ms.service: entra-id
ms.subservice: app-provisioning
ms.topic: troubleshooting
ms.date: 06/09/2025
ms.author: jfields
ms.reviewer: chmutali
---
 
## Known limitations
 
- The provisioning service supports setting custom security attributes of type `String`, `Integer`, and `Boolean`.
- Provisioning multi-valued custom security attributes isn't supported.
- Provisioning deactivated custom security attributes isn't supported.
- With the [Attribute Log Reader](~/identity/role-based-access-control/permissions-reference.md#attribute-log-reader) role, you can't view the custom security attribute value in the provisioning logs.
 
+4 / -2 lines changed
Commit: add note to explain sychronization behavior between app reg and sp
Changes:
Before
After
ms.subservice: enterprise-apps
ms.topic: how-to
 
ms.date: 04/08/2025
ms.author: jomondi
ms.reviewer: ergreenl
zone_pivot_groups: enterprise-apps-minus-legacy-powershell
```
:::zone-end
 
> [!NOTE]
> Managed identities are distinct from Microsoft Entra App Registrations. Managed identities only have a service principal object and do not possess an application object, which is typically used for granting app permissions. As a result, global admins cannot change the settings of a managed identity, as the security boundary is the resource itself.
 
## Use Microsoft Graph to configure advanced app properties
 
 
 
ms.subservice: enterprise-apps
ms.topic: how-to
 
ms.date: 06/10/2025
ms.author: jomondi
ms.reviewer: ergreenl
zone_pivot_groups: enterprise-apps-minus-legacy-powershell
```
:::zone-end
 
Enterprise applications (service principals) inherit specific properties from their associated app registrations when both exist in the same tenant. These properties are synchronized from the app registration, but the synchronization isn't immediate or continuous. Sometimes, updating an enterprise application might prompt the directory to refresh properties from the app registration, causing updates that weren't part of the original request.
 
> [!NOTE]
> Managed identities are distinct from Microsoft Entra App Registrations. Managed identities only have a service principal object and don't possess an application object, which is typically used for granting app permissions. As a result, global admins can't change the settings of a managed identity, as the security boundary is the resource itself.
 
## Use Microsoft Graph to configure advanced app properties
 
Modified by Barclay Neira on Jun 10, 2025 7:48 AM
πŸ“– View on learn.microsoft.com
+3 / -3 lines changed
Commit: updating include ownership and manager field
Changes:
Before
After
---
title: Inactive applications don’t have highly privileged Microsoft Graph API permissions
ms.author: joflore
author: MicrosoftGuyJFlo
ms.service: entra-id
ms.topic: include
ms.date: 02/03/2025
ms.author: joflore
ms.custom: Identity-Secure-Recommendation
# category: Access control
# risklevel: Medium
---
title: Inactive applications don’t have highly privileged Microsoft Graph API permissions
ms.author: barclayn
author: barclayn
manager: pmwongera
ms.service: entra-id
ms.topic: include
ms.date: 02/03/2025
ms.custom: Identity-Secure-Recommendation
# category: Access control
# risklevel: Medium
Modified by Barclay Neira on Jun 10, 2025 7:48 AM
πŸ“– View on learn.microsoft.com
+3 / -3 lines changed
Commit: updating include ownership and manager field
Changes:
Before
After
---
title: Inactive applications don’t have highly privileged built-in roles
ms.author: joflore
author: MicrosoftGuyJFlo
ms.service: entra-id
ms.topic: include
ms.date: 02/03/2025
ms.author: joflore
ms.custom: Identity-Secure-Recommendation
# category: Application management
# risklevel: High
---
title: Inactive applications don’t have highly privileged built-in roles
ms.author: barclayn
author: barclayn
manager: pmwongera
ms.service: entra-id
ms.topic: include
ms.date: 02/03/2025
ms.custom: Identity-Secure-Recommendation
# category: Application management
# risklevel: High
Modified by Barclay Neira on Jun 10, 2025 7:48 AM
πŸ“– View on learn.microsoft.com
+3 / -3 lines changed
Commit: updating include ownership and manager field
Changes:
Before
After
---
title: Applications don't have secrets configured
ms.author: joflore
author: MicrosoftGuyJFlo
ms.service: entra-id
ms.topic: include
ms.date: 02/03/2025
ms.author: joflore
ms.custom: Identity-Secure-Recommendation
# category: Application management
# risklevel: High
---
title: Applications don't have secrets configured
ms.author: barclayn
author: barclayn
manager: pmwongera
ms.service: entra-id
ms.topic: include
ms.date: 02/03/2025
ms.custom: Identity-Secure-Recommendation
# category: Application management
# risklevel: High

πŸ—‘οΈ Deleted Documentation Files

DELETED docs/identity/saas-apps/webmethods-integration-cloud-tutorial.md
Deleted by omondiatieno on Jun 10, 2025 6:29 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity/saas-apps/webmethods-integration-cloud-tutorial
-182 lines removed
Commit: Retire articles that whose apps are nolonger in the gallery
DELETED docs/identity/saas-apps/promapp-tutorial.md
Deleted by omondiatieno on Jun 10, 2025 6:29 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity/saas-apps/promapp-tutorial
-165 lines removed
Commit: Retire articles that whose apps are nolonger in the gallery
DELETED docs/identity/saas-apps/illumio-sso-tutorial.md
Deleted by omondiatieno on Jun 10, 2025 6:29 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity/saas-apps/illumio-sso-tutorial
-132 lines removed
Commit: Retire articles that whose apps are nolonger in the gallery
DELETED docs/identity/saas-apps/veritas-provisioning-tutorial.md
Deleted by omondiatieno on Jun 10, 2025 6:29 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity/saas-apps/veritas-provisioning-tutorial
-129 lines removed
Commit: Retire articles that whose apps are nolonger in the gallery
DELETED docs/identity/saas-apps/kontiki-tutorial.md
Deleted by omondiatieno on Jun 10, 2025 6:29 PM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/identity/saas-apps/kontiki-tutorial
-120 lines removed
Commit: Retire articles that whose apps are nolonger in the gallery
DELETED docs/global-secure-access/concept-netskope-integration.md
Deleted by Ken Withee on Jun 10, 2025 1:19 AM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/global-secure-access/concept-netskope-integration
-95 lines removed
Commit: Removes outdated version.
DELETED docs/global-secure-access/concept-netskope-coexistence.md
Deleted by Ken Withee on Jun 10, 2025 1:39 AM
πŸ“– Was available at: https://learn.microsoft.com/en-us/entra/global-secure-access/concept-netskope-coexistence
-89 lines removed
Commit: Updates which file is removed. Coexistence updated, integration is different and added it back.