This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 82%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAO%3C/text%3E%3C/svg%3E)
I am trying to create Data Catalog in existing subscription but but I am getting "Only one Azure Data Catalog is supported per organization. If a Catalog has already been created for your organization, you cannot add additional catalogs." However I did not previously create a data catalog. How to get around this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 9%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
Hi @Alphonse Okossi ,
Welcome to Microsoft Q&A forum and thanks for your query.
Are you trying to create Azure Data Catalog or Azure Purview instance? You can provision only one data catalog per organization (Azure Active Directory domain). Therefore, if the owner or co-owner of an Azure subscription who belongs to this Azure Active Directory domain has already created a catalog, then you can't create a catalog again even if you have multiple Azure subscriptions. To test whether a data catalog has been created by a user in your Azure Active Directory domain, go to the Azure Data Catalog home page and verify whether you see the catalog. If a catalog has already been created for you
For updated Data Catalog features, please use the new Azure Purview (Preview) service, which offers unified data governance for your entire data estate.
Actually I was able to resolve my issue by logging in using my new log in id instead of the old one.
@Alphonse Okossi - Glad to know that the issue was resolved. Thanks for sharing your findings. Please feel free to accept your answer, as it would help others to find it quickly.
Thank you
Have a good day!