You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When signing in, the suggested FQDN for the email address reflects the original settings of the Entra ID (which in our case is green.develop.turingsafehaven.ac.uk, rather than the domain for the actual SRE being logged in to.
This is controlled by the company branding settings on the Entra ID, and it looks like is only a global setting that can't change according to which SHM the SRE being logged in to is attached to.
This is something a system manager would define when setting up the Entra ID, rather than something we control.
Thus, it is probably just a case of recommending that these company branding fields be left empty if you are intending to deploy multiple SHMs linked to one Entra ID.
The text was updated successfully, but these errors were encountered:
This is something we set up previously. It's under Identity > User experiences > Company branding in Entra. Sounds like a simple change to the Entra setup docs to put some suggested wording in here (ideally that doesn't refer to the domain name since multiple domains can be connected to a single SHM).
You could consider adding icons etc. too if you like?
When signing in, the suggested FQDN for the email address reflects the original settings of the Entra ID (which in our case is
green.develop.turingsafehaven.ac.uk
, rather than the domain for the actual SRE being logged in to.This is controlled by the company branding settings on the Entra ID, and it looks like is only a global setting that can't change according to which SHM the SRE being logged in to is attached to.
This is something a system manager would define when setting up the Entra ID, rather than something we control.
Thus, it is probably just a case of recommending that these company branding fields be left empty if you are intending to deploy multiple SHMs linked to one Entra ID.
The text was updated successfully, but these errors were encountered: