Steve_Kurutz Thank you for your additional feedback and insights. We recognize that this change may feel disruptive, and would love to partner with customers, like yourself, on identifying ways for making it easier. At the same time, to offer additional detail
- Customer understanding of differences between Azure AD and AD. We serve over 720,000 organizations of various sizes globally. With that our customers range from deep identity experts, like yourself, to security professionals that manage a variety of security tools and may not have bandwidth to deeply learn on-premises and cloud identity product differences. The discussion in thread shows that there is a perception that Azure AD is an Active Directory in Azure, which is technically inaccurate. Both products target the same need but solve it differently. The product that is closest to "AD in Azure" is, indeed, Azure AD Domain Services.
{
"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 customers 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