title: Correct implementation of multi-tenancy in Azure Active Directory
body: <p>Lets say I set up and create a new Azure Account and Subscription. Azure automatically creates me an Azure AD called "<em>somedomain.onmicrosoft.com</em>".</p>
  
  <p>Later I deploy REST API and Angular SPA app to Azure. Since I'm using Azure AD for authentication and authorization on both of the applications I register them on my Azure AD, under the domain "<em>somedomain.onmicrosoft.com</em>". </p>
  
  <p>Everything works fine, however after some time I realize that I want to allow access to my services/apps to other organizations. After doing some research I realize that what I want to achieve is <em>multi-tenancy</em>. </p>
  
  <p>In order to register a new <em>tenant</em> I do the following:</p>
  
  <ol>
  <li>Go to Azure portal.</li>
  <li>On the left blade menu click on "Create a resource" and search for "Azure Active Directory".</li>
  <li>Create a new directory called "<em>tenant-1.onmicrosoft.com</em>".</li>
  </ol>
  
  <p>Next, I update my registered apps (on "<em>somedomain.onmicrosoft.com</em>") according to <a href="https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant" rel="nofollow noreferrer">this documentation</a> - enabling multi tenancy and common endpoint.</p>
  
  <p>After all of this, both users from AD "<em>somedomain.onmicrosoft.com</em>" and "<em>tenant-1.onmicrosoft.com</em>" should be able to authenticate and access my services.</p>
  
  <p><strong>Question</strong></p>
  
  <p>Is this the correct way of achieving and implementing multi tenancy?</p>