From the course: Microsoft Graph for Developers

Multitenant vs. single tenant

From the course: Microsoft Graph for Developers

Multitenant vs. single tenant

- [Instructor] Now there is one other thing worth pointing out at this time, and that is the concept of single-tenant versus multi-tenant. So at this point, visit your admin center in Office 365, and from there, access Azure AD, which will take you over here, then try and find your app registration. Right, so under App registrations, MyWebApp, and when you come to the registration of your web app, click on All Settings, and then click on Properties, and then scroll to the bottom here. And you see here that that by default, your web application is not multi-tenanted. What does that mean? This means that the application, the way it's currently written in its current form, needs to preregistered in the Azure AD you're running it under. In other words, this is an in-house application, designed for say that you're writing this application for one company or one client, or at least a few. If you want to expand this application, let's say you're a third-party ISV, and you want to have this application sort of self-register itself during the authentication process, then you would change this to Multi-tenanted Yes. And what essentially that will do is that when the first user signs in, and assuming that they're an admin-like user, the application will register itself in their Azure AD. Now that doesn't mean that the other user in the other tenancy can change the permissions or anything about the application really. It just means that the application now exists in their Azure AD and now you can roll out this application as a third-party ISV in a multi-tenanted form.

Contents