Azure-docs: Azure Active Directory - new portal experience

[SychevIgor]

Azure documentation issue guidance

On of documentation pages still old (classic portal).
https://docs.microsoft.com/en-us/rest/api/datacatalog/create-an-azure-active-directory-tenant
I can't create issue directly from this page, it's why I did it manually

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 14ab965b-dc45-f450-1302-5ffe491ca129
• Version Independent ID: 0d96d50d-a349-3408-3b93-d8b084e1cbd1
• Content: How to get an Azure AD tenant
• Content Source: articles/active-directory/develop/quickstart-create-new-tenant.md
• Service: active-directory
• GitHub Login: @CelesteDG
• Microsoft Alias: celested

[jason-j-MSFT]

@SychevIgor I don't know who to send this issue to as it's not covered in this repo, but I will investigate.

[jason-j-MSFT]

@spelluru, @steelanddata, @hellosnow, do you know where to send an issue regarding the REST API docs or who I could reach out to?

[hellosnow]

The last update is by @spelluru , could you help to take a look?

[spelluru]

@hellosnow - it has been a long time since I worked on Data Catalog. If you are looking for a way to do this in the new portal, I think that this article may help:
https://docs.microsoft.com/en-us/power-bi/developer/create-an-azure-active-directory-tenant

[jason-j-MSFT]

@mtillman could you help route this to a content author? Let me know who to assign it to and I will take care of it.

[JasonWHowell]

@SychevIgor Thanks for making the issue. You could also just spin up an email if needed. Rest APIs pages do not have GitIssues enabled at present.

We can probably just remove the page, since it is out of scope of Azure Data Catalog, but I'll check with the current PMs.

Thanks, Jason

[markingmyname]

@JasonWHowell, @SychevIgor. We have removed this article and redirected its link to here - https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply.

We will gladly continue the discussion, and we can reopen the issue if needed.

This update should be live by tomorrow afternoon.