question

AnandRMenon-2032 avatar image
0 Votes"
AnandRMenon-2032 asked MarileeTurscak-MSFT edited

Facing error while trying to deploy custom ARM templates in Azure

I'm facing an error while trying to deploy custom ARM templates in Azure.

"message": "Pricing tier doesn't match the subscription's billing model. Read http://aka.ms/PricingTierWarning
for more details."

I'm doing this as part of Azure Sentinel training, part of SC-200 exam. I have a Pay-As-You-Go Azure subscription now.

Found this error reported previously online but couldn't figure out how to fix this issue from the solutions provided as some options have changed in Azure since those questions were posted.

Including the screenshot for your reference. Please help on this issue.

136315-azure-arm-error.png



azure-sentinel
azure-arm-error.png (92.9 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

MarileeTurscak-MSFT avatar image
1 Vote"
MarileeTurscak-MSFT answered MarileeTurscak-MSFT edited

This can happen if the wrong SKU is mentioned in the ARM template. In this thread, users were able to fix this by selecting the right service plan SKU for their LogAnalytics Workspace (changed from Free to pergb2018).

 "location": "[resourceGroup().location]",
       "properties": {
         "sku": {
           "name": "pergb2018"
         }
       }
     },

Which guide are you following for this?


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you so much for the quick reply. I made changes in the ARM template as you mentioned(Changed from 'Free' to 'pergb2018') and now the issue is resolved. The deployment has succeeded now. Seems the custom template provided in Microsoft Learn is designed for 'Free' plan and we have to make changes according to the plan we have subscribed to.
I previously referred the following thread dealing with a similar issue:
https://github.com/MicrosoftDocs/azure-docs/issues/25161

0 Votes 0 ·

Thanks for confirming! Glad it worked as I wasn't 100% sure if it was the same issue. I converted the comment to an answer.

0 Votes 0 ·