<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>missingsubscriptionregistration-error on The Cloud Hub</title>
    <link>https://thecloudhub.com/tag/missingsubscriptionregistration-error/</link>
    <description>Recent content in missingsubscriptionregistration-error on The Cloud Hub</description>
    <generator>Hugo -- 0.118.2</generator>
    <language>en-au</language>
    <lastBuildDate>Wed, 07 Jul 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://thecloudhub.com/tag/missingsubscriptionregistration-error/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to fix Azure MissingSubscriptionRegistration error</title>
      <link>https://thecloudhub.com/2021/07/07/how-to-fix-azure-missingsubscriptionregistration-error/</link>
      <pubDate>Wed, 07 Jul 2021 00:00:00 +0000</pubDate>
      <guid>https://thecloudhub.com/2021/07/07/how-to-fix-azure-missingsubscriptionregistration-error/</guid>
      <description>Are you trying to deploy an Azure Resource Manager (ARM) template and getting the error MissingSubscriptionRegistration? In this article we&amp;rsquo;ll take a look at what the cause of the error is, and how you can easily rectify the problem.
Sometimes when trying to run an ARM template in a new subscription to create Azure resources, customers come across the following error:
MissingSubscriptionRegistration: The subscription is not registered to use namespace &#39;Microsoft.</description>
      <content:encoded><![CDATA[<p>Are you trying to deploy an Azure Resource Manager (ARM) template and getting the error <code>MissingSubscriptionRegistration</code>? In this article we&rsquo;ll take a look at what the cause of the error is, and how you can easily rectify the problem.</p>
<p>Sometimes when trying to run an ARM template in a new subscription to create Azure resources, customers come across the following error:</p>
<p><code>MissingSubscriptionRegistration: The subscription is not registered to use namespace 'Microsoft.Web'</code></p>
<p>The namespace may be different depending on the resources you&rsquo;re trying to create - but effectively this error is telling you that for your subscription, you cannot create resources belonging to the aforementioned namespace. In the case of this example, that&rsquo;s <code>Microsoft.Web</code> - specifically an App Service.</p>
<p>By default, a new subscription will have most resource providers <strong>disabled</strong> as <a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider">a precautionary security measure</a>. You can see a full list of default <strong>enabled</strong> providers <a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-services-resource-providers">here</a>.</p>
<p>By having most providers disabled, compromised accounts are unable to create a raft of resources. Therefore it&rsquo;s <strong>critical</strong> that you only enable namespaces you need to use.</p>
<p>Normally deploying an ARM template should automatically enable the resource namespace - but sometimes it doesn&rsquo;t work as expected. Similarly, creating a resource manually in the Azure portal should also automatically enable the resource namespace.</p>
<p>Fixing this error is quite straightforward, assuming you have owner or contributor access to the subscription. If you don&rsquo;t, you&rsquo;ll need to get your IT administrator to make these changes on your behalf.</p>
<p>Open <a href="https://portal.azure.com">the Azure Portal</a>, navigate to <code>Subscriptions</code> and choose the subscription you&rsquo;re trying to deploy the ARM template into. Then, go to <code>Resource providers</code> in the sidebar.</p>
<p><img loading="lazy" src="images/resource_providers-1024x737.png" alt=""  />
</p>
<p>Now scroll through the list of all resource providers until you see the one mentioned in the error message you received. Click the namespace to highlight it, and then choose <code>Register</code> from the menu bar.</p>
<p>This will now activate the namespace, allowing you to create resources that reside within it and thereby the error will be resolved.</p>
<p>Note however that the namespace may not be activated immediately - you may need to wait up to 15 minutes before running the ARM template deployment again.</p>
<p>The registering status shows in the portal while the namespace is being activated - so a quick refresh of the page will allow you to see when the work is completed.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
