๐ก๐ฒ๐ ๐ฅ๐ผ๐น๐ฒ & ๐ฃ๐ฒ๐ฟ๐บ๐ถ๐๐๐ถ๐ผ๐ป ๐๐ถ๐๐ฐ๐ผ๐๐ฒ๐ฟ๐ฒ๐ฑ ๐ถ๐ป ๐๐ป๐๐ฟ๐ฎ ๐๐๐ถ๐ป๐ด ๐ ๐ถ๐ฐ๐ฟ๐ผ๐๐ผ๐ณ๐ ๐ฏ๐ฒ๐ฑ ๐๐ฆ๐
While reviewing role definitions via Microsoft 365 DSC, we spotted a few interesting changes in Entra:
๐ฅ๐ผ๐น๐ฒ: ๐ฃ๐ฒ๐ผ๐ฝ๐น๐ฒ ๐๐ฑ๐บ๐ถ๐ป๐ถ๐๐๐ฟ๐ฎ๐๐ผ๐ฟ
We found a new permission in the destination tenant not present in the source:
โ microsoft.office365.webPortal/allEntities/standard/read
This is in addition to the expected permissions like:
โข microsoft.peopleAdmin/organization/allProperties/read
โข microsoft.peopleAdmin/organization/allProperties/update
โข microsoft.people/users/photo/read
โข microsoft.people/users/photo/update
๐ ๐ก๐ฒ๐ ๐ฅ๐ผ๐น๐ฒ ๐๐ฒ๐๐ฒ๐ฐ๐๐ฒ๐ฑ: ๐ ๐ถ๐ฐ๐ฟ๐ผ๐๐ผ๐ณ๐ ๐๐ฟ๐ฎ๐ฝ๐ต ๐๐ฎ๐๐ฎ ๐๐ผ๐ป๐ป๐ฒ๐ฐ๐ ๐๐ฑ๐บ๐ถ๐ป๐ถ๐๐๐ฟ๐ฎ๐๐ผ๐ฟ
This role was absent in the source and now appears in the destination configuration.
These kinds of differences are exactly why we use Microsoft 365 DSC for change tracking and governanceโseeing whatโs new, missing, or unexpected is critical for securing and managing M365 environments.
โธป
๐ง Stay sharp, stay secure.
#Microsoft365DSC #Microsoft365 #Entra #AzureAD #MicrosoftGraph #CloudSecurity #IdentityGovernance #M365Admins #TechCommunity #MSP