Need some clarifications on the Microsoft 365 login
Sorry to use the issue threads for this but I need some concerns addressed or assumptions confirmed to help address some of the UI issues with that login dialog.
Summarizing the Integration
My impression from looking into the situation that is Microsoft 365 account is that it's for connecting to some form of Active Directory (or successive techologies). What sort exactly does that integration that grant you on the desktop? The dialog says calendar, contacts and files but is that the best summary for the type of integration this is?
It would be extremely helpful to hear from someone using this integration.
Consistent Terminology
Additionally, Microsoft has rebranded or changed the terminology around this product several times to the point where it makes this dialog's UI hard to adjust or get a sense of what settings here correspond to what components on the Microsoft side.
Client ID
- I've seen reference to "Application (Client) ID" in older examples for Azure, presumably that is what this is?
- Without an ID presumably this dialog is of no use to anyone? Which would mean that that should be mentioned in the dialog itself.
Issuer
- I haven't seen this term among the Microsoft (or third-party) documentation, what does this correspond to?
- I've seen "Directory (Tenant) ID" in the most recent documentation, is this the information users will need to provide here (since the format matches)?
- it's also unclear what the difference between Common and Custom is, or rather: who/what is the common issuer? and why you would a user change from that to a custom issuer.
Changing Login Name
The login is called "Microsoft 365" but, correct me if I'm wrong, I think it only applies to what was formerly Azure Active Directory under an enterprise 365 account, and not (as it may be confused for) a personal 365 account which some one may have for Microsoft Office.
As of March 2024, this on the Microsoft side has been rebranded once again to "Microsoft Entra" should the dialog/login be changed yet again to reflect this? (A downside I can see here is that some older enterprise deployments may be still under the old terminology/brand name).