Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 15 subscribers
  • Views 4325 views
  • Users 0 members are here
Options
Suggested
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

balletbob

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
  • 0

    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.

    Thanks,
    Yashraj Singha
    Manager | Global Community Support
    Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
    If a post solves your question, please use the "Verify Answer" button.
    The New Home of Sophos Support Videos!  - Visit Sophos Techvids
  • FormerMember
    0 FormerMember in reply to Yashraj S

    What it also means, is that when we block an account in Azure AD the user can still bypass Microsoft authentication and login locally. We would need to remember to manually delete the account in Sophos. From a security best practice standpoint, that looks odd.

    Therefore I'd say it makes sense to separately request integration with Azure AD so that users are managed by a the AD and not in isolation.

Reply
  • FormerMember
    0 FormerMember in reply to Yashraj S

    What it also means, is that when we block an account in Azure AD the user can still bypass Microsoft authentication and login locally. We would need to remember to manually delete the account in Sophos. From a security best practice standpoint, that looks odd.

    Therefore I'd say it makes sense to separately request integration with Azure AD so that users are managed by a the AD and not in isolation.

Children
No Data
Unfiltered HTML