Microsoft
Microsoftwroot ckttdev , thx1200 Jim_Woodward , cyber_security GrumpyMammoth1990 , Carol Chisholm sstrausbaugh
We value your constructive feedback. Reiterating my earlier comment- we've considered many factors and perspectives in taking the decision to rename Azure AD to Microsoft Entra ID. A couple of themes that seem common in your feedback is managing updates to documentation within customer / partner environments and no changes to many of the experiences like APIs, signin URLs etc.
On the documentation and content - for anyone who's open to doing that - I'd love to have a deeper dialog to understand what tools are being used for such internal documentation, and if there's anything we can do to support our customers and partners with automation for such changes.
Carol Chisholm our internal documentation is not updated yet updated intentionally. We just announced this change and we'd like to use the next 30 days to inform all our customers about upcoming change, before we implement it. The change management itself will be automated, and we'd like to explore if there's more we can do to support our customers and partners for the internal name changes.
Regarding no changes to capabilities or technical experiences, like signin URLs and APIs - resurfacing my earlier comment. Many of the technical components that are not changing either have low visibility to customers (e.g., sign-in URLs), or for the most part are not branded, like APIs. Example of how Conditional Access API shows up in Microsoft Graph (conditionalAccessPolicy resource type - Microsoft Graph v1.0 | Microsoft Learn)
{
"conditions": {"@odata.type": "microsoft.graph.conditionalAccessConditionSet"},
"createdDateTime": "String (timestamp)",
"displayName": "String",
"grantControls": {"@odata.type": "microsoft.graph.conditionalAccessGrantControls"},
"id": "String (identifier)",
"modifiedDateTime": "String (timestamp)",
"sessionControls": {"@odata.type": "microsoft.graph.conditionalAccessSessionControls"},
"state": "string"
}
For the critical technical components that are highly visible we'd love to partner with you to assess what would be the best path to minimize the presence of 'Azure AD' name in the experience as we work through the change. I hope you'll join us to continue the dialog in the upcoming "Ask me anything" session on rebranding in the Microsoft Entra Tech Accelerator on July 20th at 8:00am - 10:30am. Event | Microsoft Entra Tech Accelerator Part 2 - July 20, 2023