Thursday, May 19, 2016

The 3 ways to overseeing characters in Office 365

On the off chance that you aren't prepared to relinquish on-premises Active Directory administration, you have three great alternatives.



Overseeing Active Directory personalities from the Office 365 cloud is not that entangled, but rather it's a troublesome jump for some administrators used to taking care of their own character administration on-premises through Active Directory for as far back as 15 years or something like that. They think that its hard to envision having that administration happen somewhere else, dreading lost control.

Be that as it may, moving to Office 365 for Active Directory organization is not a win big or bust suggestion. There are three ways you can take.

1. Go all-cloud through Azure Active Directory

Suppose you have another organization hoping to utilize Office 365 for all its correspondence and cooperation needs. You've never set up Active Directory or on-premises servers - and you'd like to keep it that way. All things considered, put your clients in Office 365 just, utilizing Azure Active Directory to oversee them.

2. Sync on-premises Active Directory with the cloud

On the off chance that you have on-premises Active Directory, you can begin with synchronized personality between your on-premises server and Azure Active Directory. With index synchronization, you can keep on doing the administration on-premises, as the progressions you make to client accounts get matched up to Azure Active Directory in the cloud. With this strategy, you can synchronize the passwords as well, yet clients will even now need to sign into Office 365 - you get secret key match up however not single sign-on.

3. Combine personalities between on-premises and the cloud for single sign-on


In the event that you need SSO, you can get it - through unified characters. What's fascinating about this alternative is that the secret word hash doesn't need to be synchronized with Azure Active Directory. Accordingly, the secret word is checked by the on-premises Active Directory server, yet because of either Active Directory Federation Services (ADFS) or an outsider device, the SSO access to Office 365 (and other upheld SaaS applications) is conceded.

Despite the fact that ADFS is incorporated with Office 365, you may need an outsider administration. (Microsoft distributes a rundown of united character suppliers, which incorporate Centrify, Okta, and CA Secure Cloud.)

One motivation to look past Microsoft: Active Directory Federation Services requires time and exertion for its equipment and programming arrangement; a few server parts must be set up (the Federation Service, the Federation Service Proxy, and the Web server specialist). It's genuine work to set up various servers and get the SSL testaments set up. At that point there's the time and cost of setting up excess servers for high accessibility. At last, once the ADFS trust is built up, you need to decide claims rules for each upheld cloud application.

In the event that you utilize an outsider united personality administration, a lot of that work is accomplished for you. First and foremost, the suppliers have lists of preconfigured SaaS applications officially set up; you don't need to stretch about making every association. You likewise don't need to introduce extra on-premises servers and administrations (or stress over their accessibility).



 
http://www.infoworld.com/article/3071181/identity-management/the-3-paths-to-managing-identities-in-office-365.html

No comments:

Post a Comment