![]() I guarantee that with such a configuration you will make your and your user’s life much more complicated than it’s necessary. ![]() Imagine we have a user, who is being managed in AD with the following attributes: Hold on, cause it will be a hardcore journey. Let’s think about what happens in the most pessimistic scenario in the most complicated setup. I know all of the security guys are cursing me right now, I hear your bashing – “oooh C’mon man, users can’t give their credentials without thinking about it” – yes, I agree. You can tell your users just to use their email and password every time they are asked for credentials. It allows using many scenarios without straining your brain cells. Why is such a setup essential? Well, the answer is very simple – it gives peace of mind to end users and the IT staff. In our story, our hero had the following setup: Simplifying a bit, each user account in AD has two logins: Why did I mention emails so many times? Because this story should be about UPN – User Principal Name, but hardly anyone knows what this means – especially the end users. And all this only by using his email and password. He can also access files shared with him by those partners who also use Office 365. He can also talk to his external partners on Skype for Business. Then he uses the same credentials to access all his productivity applications.Įvery application is accessible using these credentials. In this story, our hero is using his email to access all the systems and applications. Let’s start with a story about the environment where everything is set up properly and users and admins are living happily doing their jobs. How to properly set up credentials for cloud services?.What problems can occur when adopting Office 365?.
0 Comments
Leave a Reply. |