Authored by Andreas Helland
Enter Azure Active Directory (AAD). Why should I care about Azure Active Directory (AAD) as a developer? Isn't it basically a clouded version of an on-premises Active Directory (AD)? Which is usually more of an admin thing than something for developers. I hear you, but it's not that simple.
You can skim through the intro parts, and quickly get a feel for things. Afterwards, you can read more of the manuals or just dive straight into the samples. "Hey, there's an MVC web app. Let's pull down the repo, build and hit F5 in Visual Studio… It works! Great!"
If you haven't done the exercise before I encourage you to do this, because even if you don't understand all the code after the first five minutes it will hopefully give you a good feeling of accomplishment to propel yourself onwards.
Use the same portal you used for registering the app for configuring it afterwards. Yes, you should be able to switch between the old and new Azure portal, but that doesn't mean everything is identical on the back-end. Maybe there is a bug giving the appearance of being correctly configured, but it isn't actually so.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.