Skip to content

Commit 8fc897c

Browse files
authored
Merge pull request #286114 from mumian/0904-arm-troubleshoot
New troubleshooting article on region not accepting new customers
2 parents 2dc9529 + 7666be3 commit 8fc897c

File tree

3 files changed

+44
-0
lines changed

3 files changed

+44
-0
lines changed
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: Resolve location ineligible errors
3+
description: Learn how to resolve location ineligible errors.
4+
ms.topic: troubleshooting
5+
ms.date: 05/07/2025
6+
---
7+
8+
# Resolve location ineligible errors
9+
10+
This article provides information about the location ineligible error that might occur when you attempt to create new resources in an Azure region.
11+
12+
## Symptom
13+
14+
The following error message is returned when you attempt to create a new resource in an Azure region using an Azure Resource Manager (ARM) template, Azure CLI, or Azure PowerShell. Or, you might see this error in Azure portal when you select an Azure region in the region drop-down while attempting to create a new resource.
15+
16+
```Output
17+
The selected region is currently not accepting new customers: https://aka.ms/locationineligible
18+
```
19+
20+
## Cause
21+
22+
To prioritize resources for existing customers in an Azure region, Microsoft may restrict access for customers without resources in that location. If you attempt to create resources in a region where this policy applies and your tenant is new to that region, you receive this error message. This policy is currently in effect for the following region(s):
23+
24+
- West Europe
25+
26+
## Solution
27+
28+
If you receive this message, there are two possible solutions:
29+
30+
- **Select an alternative region:** Most users should select a different Azure region to deploy their resources into.
31+
- **Submit a remediation request:** If one or more subscriptions in your tenant have resources already deployed to the Azure region, or there's a clear business need for country-specific data sovereignty, then contact Microsoft support by using the following steps:
32+
33+
> [!NOTE]
34+
> Remember that a remediation request should only be submitted to Microsoft support if there is a clear requirement for deploying resources to the Azure region. Otherwise, please choose a different Azure region for your deployment.
35+
36+
1. Sign in to the Azure portal by selecting [this link](https://portal.azure.com/#create/Microsoft.Support/Parameters/%7B%0A%09%22subId%22%3A%20%22%22%2C%0A%09%22pesId%22%3A%20%2206bfd9d3-516b-d5c6-5802-169c800dec89%22%2C%0A%09%22supportTopicId%22%3A%20%22de9828b5-622d-15db-8ad0-b4fe9590cef8%22%2C%0A%09%22contextInfo%22%3A%20%22Unable%20to%20access%20Azure%20regions%22%2C%0A%09%22caller%22%3A%20%22accessazureregionsdeeplink%22%2C%0A%09%22severity%22%3A%20%222%22%0A%7D).
37+
1. In **How can we help you?** enter **region access**, and then select **Go**.
38+
1. In **Which service are you having an issue with?** select **Service and subscription limits (quotas)**, and then select **Next**.
39+
1. Select **Create a support request**.
40+
1. Select your **Subscription**, and in **Quota type**, select **Unable to access West Europe region**, and then select **Next**
41+
42+
:::image type="content" source="./media/error-region-access-policy/azure-support-troubleshooting-new-support-request.png" alt-text="Screenshot of new support request.":::
Loading

articles/azure-resource-manager/troubleshooting/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,8 @@
4848
href: error-invalid-name-segments.md
4949
- name: Resource quota exceeded
5050
href: error-resource-quota.md
51+
- name: Location ineligible
52+
href: error-region-access-policy.md
5153
- name: SKU not available
5254
href: error-sku-not-available.md
5355
- name: Reference

0 commit comments

Comments
 (0)