Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Central and Azure AD federation setup and behaviour

I've setup the Sophos Central Azure AD federation and am slightly puzzled by the process and behaviour.

It seems like an Admin or Standard user still has to create a password in Sophos Central before the Microsoft integration will work.

So, I’m not understanding the purpose of this integration if a user needs to create a password for Sophos Central anyway. It does defeat the purpose of a user using existing credentials. The user object already existed in the Sophos Central console so why did we need to create a password?

Other products that use Azure AD integration are happy to match against account ID without having to have the user create a password that is not used.



This thread was automatically locked due to age.
Parents
  • Hi  

    Sophos Central grants access to sensitive security options that when granting to anyone else, can be catastrophic from a security standpoint. Hence it requires a set of credentials to make it even more secure. But if you want to put in a suggestion wherein there should be no need creating separate accounts in Sophos Central once you integrate Azure AD, then I would request you to raise a feature request.

Reply
  • Hi  

    Sophos Central grants access to sensitive security options that when granting to anyone else, can be catastrophic from a security standpoint. Hence it requires a set of credentials to make it even more secure. But if you want to put in a suggestion wherein there should be no need creating separate accounts in Sophos Central once you integrate Azure AD, then I would request you to raise a feature request.

Children