📋 Microsoft Entra Documentation Changes

Daily summary for changes since August 10th 2025, 8:22 PM PDT

Report generated on August 11th 2025, 8:22 PM PDT

📊 Summary

17
Total Commits
0
New Files
2
Modified Files
0
Deleted Files
7
Contributors

📝 Modified Documentation Files

+2 / -23 lines changed
Commit: toc add and b2c deprecate fix
Changes:
Before
After
---
title: Scenario - Using Microsoft Entra ID to secure access to SAP platforms and applications
description: A guide for architects and IT administrators on how to secure access to SAP platforms and applications
author: xstof
manager: alberts
ms.service: entra
ms.subservice: fundamentals
ms.topic: conceptual
ms.date: 08/26/2021
ms.author: christoc
ms.custom: sfi-image-nochange
ms.collection:
---
 
Consider building automation to execute the entire certificate rollover process. For example, one can periodically check for expiring certificates and replace them while updating all relying parties with the new metadata.
 
## Using Azure AD B2C as the Identity Provider
 
[!INCLUDE [active-directory-b2c-end-of-sale-notice.md](~/includes/active-directory-b2c-end-of-sale-notice.md)]
 
---
title: Scenario - Using Microsoft Entra ID to secure access to SAP platforms and applications
description: A guide for architects and IT administrators on how to secure access to SAP platforms and applications
author: MartinPankraz
ms.service: entra
ms.subservice: fundamentals
ms.topic: conceptual
ms.date: 08/26/2021
ms.author: mapankra
ms.custom: sfi-image-nochange
ms.collection:
---
 
Consider building automation to execute the entire certificate rollover process. For example, one can periodically check for expiring certificates and replace them while updating all relying parties with the new metadata.
 
## Next Steps
 
- Learn more about the initial setup in [this tutorial](~/identity/saas-apps/sap-hana-cloud-platform-identity-authentication-tutorial.md)
 
 
+7 / -7 lines changed
Commit: revised attribute format
Changes:
Before
After
 
### Status of attributes after you convert SOA
 
The following table explains the status for **isCloudManaged** and **onPremisesSyncEnabled** attributes after you convert the SOA of an object.
 
Admin step | isCloudManaged value | onPremisesSyncEnabled value | Description 
-----|----------------------|----------------------|------------
Admin syncs an object from AD DS to Microsoft Entra ID | `false` | `true` | When an object is originally synchronized to Microsoft Entra ID, the **OnPremisesSyncEnabled** attribute is set to `true` and **isCloudManaged** is set to `false`. 
Admin converts the source of authority (SOA) of the object to the cloud | `true` | `null` | After an admin converts the SOA of an object to the cloud, the **isCloudManaged** attribute becomes set to `true` and the **OnPremisesSyncEnabled** attribute value is set to `null`. 
Admin rolls back the SOA operation | `false` | `null` | If an admin converts the SOA back to AD, the **isCloudManaged** is set to `false` and **OnPremisesSyncEnabled** is set to `null` until the sync client takes over the object.   
Admin creates a cloud native object in Microsoft Entra ID | `false` | `null` | If an admin creates a new cloud-native object in Microsoft Entra ID, **isCloudManaged** is set to `false` and **onPremisesSyncEnabled** is set to `null`.
 
## Roll back SOA update
 
:::image type="content" border="true" source="media/how-to-group-source-of-authority-configure/rollback.png" alt-text="Screenshot of API call to revert SOA.":::
 
> [!NOTE]
> This change to "isCloudManaged: false" allows an AD DS object that's in scope for sync to be taken over by Connect Sync the next time it runs. Until the next time Connect Sync runs, the object can be edited in the cloud. The rollback of SOA is finished only after *both* the API call and the next scheduled or forced run of Connect Sync are complete.
 
### Validate the change in the Audit Logs
 
### Status of attributes after you convert SOA
 
The following table explains the status for *isCloudManaged* and *onPremisesSyncEnabled* attributes after you convert the SOA of an object.
 
Admin step | isCloudManaged value | onPremisesSyncEnabled value | Description 
-----|----------------------|----------------------|------------
Admin syncs an object from AD DS to Microsoft Entra ID | `false` | `true` | When an object is originally synchronized to Microsoft Entra ID, the *onPremisesSyncEnabled* attribute is set to `true` and *isCloudManaged* is set to `false`. 
Admin converts the source of authority (SOA) of the object to the cloud | `true` | `null` | After an admin converts the SOA of an object to the cloud, the *isCloudManaged* attribute becomes set to `true` and the *onPremisesSyncEnabled* attribute value is set to `null`. 
Admin rolls back the SOA operation | `false` | `null` | If an admin converts the SOA back to AD, the *isCloudManaged* is set to `false` and *onPremisesSyncEnabled* is set to `null` until the sync client takes over the object.   
Admin creates a cloud native object in Microsoft Entra ID | `false` | `null` | If an admin creates a new cloud-native object in Microsoft Entra ID, *isCloudManaged* is set to `false` and *onPremisesSyncEnabled* is set to `null`.
 
## Roll back SOA update
 
:::image type="content" border="true" source="media/how-to-group-source-of-authority-configure/rollback.png" alt-text="Screenshot of API call to revert SOA.":::
 
> [!NOTE]
> The change of *isCloudManaged* to `false` allows an AD DS object that's in scope for sync to be taken over by Connect Sync the next time it runs. Until the next time Connect Sync runs, the object can be edited in the cloud. The rollback of SOA is finished only after *both* the API call and the next scheduled or forced run of Connect Sync are complete.
 
### Validate the change in the Audit Logs