📋 Microsoft Entra Documentation Changes

Daily summary for changes since November 8th 2025, 7:24 PM PST

Report generated on November 9th 2025, 7:24 PM PST

📊 Summary

3
Total Commits
0
New Files
1
Modified Files
0
Deleted Files
2
Contributors

📝 Modified Documentation Files

+1 / -1 lines changed
Commit: Update docs/global-secure-access/how-to-configure-domain-controllers.md
Changes:
Before
After
 
- Client IP address
- IP address ranges
- On-premises User Principal Name (UPN) such as `username@domain`. UPN is supported with Private Access Sensor version 2.1.31 or higher and is case insensitive. Username, which is the first part of the UPN, is supported with the earlier sensor versions and can be added in the `localpolicy`file only. We highly recommend using the UPNs instead of usernames. UPNs for on-premise users that are synced to Entra can be added from Microsoft Entra Admin Center. UPNs for on-premise users that aren't synced can only be added to the `localpolicy` file.
 
You can configure multiple IP addresses, multiple IP ranges, or both for a single SPN. Similarly, you can exclude multiple usernames for an SPN.
 
 
- Client IP address
- IP address ranges
- On-premises User Principal Name (UPN) such as `username@domain`. UPN is supported with Private Access Sensor version 2.1.31 or higher and is case insensitive. Username, which is the first part of the UPN, is supported with the earlier sensor versions and can be added in the `localpolicy`file only. We highly recommend using the UPNs instead of usernames. UPNs for on-premises users that are synced to Entra can be added from Microsoft Entra Admin Center. UPNs for on-premises users that aren't synced can only be added to the `localpolicy` file.
 
You can configure multiple IP addresses, multiple IP ranges, or both for a single SPN. Similarly, you can exclude multiple usernames for an SPN.