Azure AD Tenant required to generate Documentation

One of the question our support department get asked a lot is: “What Azure AD tenant should I use?

So here is a quick answer :

When you connect to https://generate.cloudockit.com, the first thing you have to do is to enter the Azure AD  tenant name.

ADK_AADTEnant

If you have access to an Azure Subscription with a Microsoft Account or with an Azure AD Account, it means that there is an Azure AD attached to the subscription.

In Azure, when you connect to the management portal, you can see multiple Azure Active Directories that are all the Directories you have access to:

Even if your account is in multiple Active Directory, it is mandatory that you use the Active Directory that is associated to the subscription that you want to document. Note that there is ONLY ONE Active directory that is associated to the subscription.

In order to find the directory, you can click on the settings menu and you will find the directory to use in the Directory column:

You can now go back to https://generate.cloudockit.com and specify this tenant.

If you don’t have access to the old portal, you can connect to the new one (https://portal.azure.com) and then enter the old portal address (https://manage.windowsazure.com) and you will see that the tenant name is specified in the error window :

ADK_AADTEnantNewPortal

 

 

Note : This article has been updated to reflect the process on how to find the tenant name to generate the documentation. Here is the original Post:

——————————————————————————————————————————————————————————-

CloudocKit now has a new authentication mechanism based on Azure Active Directory.

As we wanted to make the generation of Azure documentation as easy as possible, we have remove the need to create and upload a management certificate.

You can now use an Azure Active Directory account to connect to your subscription and generate the document. One important point to note is that the account needs to be global admin on the Active Directory and Subscription Co-Administrator (see last section of this blog post to see the detailed steps to create the account).

The document generation is a two steps process:

Step 1: Enter the Azure Active Directory tenant

In this first step, you need to enter the Azure Active Directory full name that contains the login that you want to use to generate the documentation. This Azure Active Directory must be linked to the subscription that you want to document.

As an example, you should enter Microsoft Azure Active Directory tenant information like mytenant.onmicrosoft.com, nameoutlook.onmicrosoft.com or azuredockit.com if you have custom domain name.

Step 2: Select the subscription that you want to document

Once you have entered the tenant information, you will automatically be redirected to the Microsoft login page.

You need to first enter you login and password and then accept the consent permissions:

Once done select the appropriate subscription and click on Generate Documentation to create the documentation:

How to create a user that has the required privilege to generate documentation

First, select the Azure Active Directory that you want to use to connect to the subscription and click on.

Then enter the information required and select Global Admin as we want the user to be able to list all users, groups and everything in the Active Directory.

Once done, you need to add the user as a Co-Administrator on the subscription so that he gets access to everything in the subscription (support for Read-Only RBAC is in our roadmap).

Go in the subscription settings:

Click on and enter the user you have created in the previous step:

You are now ready to go to use this account to document your subscription.