You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn how to troubleshoot the AvailabilityZoneNotSupported error when you try to create an Azure Kubernetes Service cluster in a set of zones.
4
+
ms.date: 06/04/2025
5
+
ms.reviewer: marcha, skuchipudi, v-weizhu
6
+
ms.service: azure-kubernetes-service
7
+
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
8
+
#Customer intent: As an Azure Kubernetes Services (AKS) user, I want to troubleshoot an Azure Kubernetes Service cluster create that failed because of a AvailabilityZoneNotSupported error code so that I can create the cluster successfully.
9
+
---
10
+
# Troubleshoot the AvailabilityZoneNotSupported error code
11
+
12
+
This article discusses how to identify and resolve the "AvailabilityZoneNotSupported" error that occurs when you try to create an Azure Kubernetes Service (AKS) cluster.
13
+
14
+
## Prerequisites
15
+
16
+
Access to [Azure CLI](/cli/azure/get-started-with-azure-cli).
17
+
18
+
## Symptoms
19
+
20
+
An AKS cluster creation fails in specified availability zones, and you receive an "AvailabilityZoneNotSupported" error with the following message:
21
+
22
+
> Preflight validation check for resource(s) for container service \<resource-name> in resource group \<resource-group-name> failed. Message: The zone(s) '1' for resource '\<agentpoolName>' is not supported. The supported zones for location '\<location>' are 'A', 'B'
23
+
24
+
## Cause
25
+
26
+
The issue occurs because the requested SKU has restrictions in some or all zones of your subscription. To verify the restrictions, go to the [Verify SKU restrictions](#verify-sku-restrictions) section.
27
+
28
+
## Solution
29
+
30
+
To resolve this issue, follow the [Azure region access request process](../../general/region-access-request-process.md) to request access to the specified region or zone.
31
+
32
+
## Verify SKU restrictions
33
+
34
+
1. List the SKU details by running one of the following commands:
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/linux/upgrade-rhel-7dotx-to-7dot9-sap-hana-apps.md
+20-10Lines changed: 20 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,13 +47,18 @@ For more information about performing the upgrade process on custom, golden, or
47
47
```bash
48
48
sudo rm /etc/yum/vars/releasever
49
49
```
50
+
3. Create a config file by using this command:
50
51
51
-
3. Install the *rhui-azure-rhel7-base-sap-ha* package:
52
+
```bash
53
+
sudo tee rhel7-base-sap-ha.config > /dev/null <<<$'[rhui-microsoft-azure-rhel7-base-sap-ha]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 7 (rhel7-base-sap-ha)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel7-base-sap-ha\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc\nsslverify=1'
54
+
```
55
+
4. Install the *rhui-azure-rhel7-base-sap-ha* package:
4. Verify that the corresponding repositories are available and show no errors:
60
+
61
+
5. Verify that the corresponding repositories are available and show no errors:
57
62
58
63
```bash
59
64
sudo yum repolist
@@ -77,12 +82,12 @@ For more information about performing the upgrade process on custom, golden, or
77
82
> [!IMPORTANT]
78
83
> A single host can accommodate both SAP HANA and other SAP applications, such as NetWeaver. In this case, all the preceding repositories are required. Optionally, you can modify the */etc/yum.repos.d/rh-cloud-base-sap-ha.repo* file based on your system's specific requirements.
79
84
80
-
5. Upgrade the system to RHEL 7.9:
85
+
6. Upgrade the system to RHEL 7.9:
81
86
82
87
```bash
83
88
sudo yum update
84
89
```
85
-
6. Reboot the VM to complete the upgrade:
90
+
7. Reboot the VM to complete the upgrade:
86
91
87
92
```bash
88
93
sudo reboot
@@ -100,14 +105,19 @@ For more information about performing the upgrade process on custom, golden, or
100
105
```bash
101
106
sudo rm /etc/yum/vars/releasever
102
107
```
108
+
3. Create a config file by using this command:
103
109
104
-
3. Install the *rhui-azure-rhel7-base-sap-apps* package:
110
+
```bash
111
+
sudo tee rhel7-base-sap-apps.config > /dev/null <<<$'[rhui-microsoft-azure-rhel7-base-sap-apps]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 7 (rhel7-base-sap-apps)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel7-base-sap-apps\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc\nsslverify=1'
112
+
```
113
+
114
+
4. Install the *rhui-azure-rhel7-base-sap-apps* package:
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/linux/upgrade-rhel-8-dot-x-to-8-dot-10-on-sap-hana-apps.md
+21-10Lines changed: 21 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,13 +53,19 @@ For more information about performing the upgrade process on custom, golden, and
53
53
sudo rm /etc/yum/vars/releasever
54
54
```
55
55
56
-
3. Install the *rhui-azure-rhel8-base-sap-ha* package:
56
+
3. Create a config file by using this command:
57
+
58
+
```bash
59
+
sudo tee rhel8-base-sap-ha.config > /dev/null <<<$'[rhui-microsoft-azure-rhel8-base-sap-ha]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 8 (rhel8-base-sap-ha)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel8-base-sap-ha\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc\nsslverify=1'
60
+
```
61
+
62
+
4. Install the *rhui-azure-rhel8-base-sap-ha* package:
4. Verify that the corresponding repositories are available and show no errors:
68
+
5. Verify that the corresponding repositories are available and show no errors:
63
69
64
70
```bash
65
71
sudo dnf repolist
@@ -80,13 +86,13 @@ For more information about performing the upgrade process on custom, golden, and
80
86
> [!IMPORTANT]
81
87
> A single host can accommodate both SAP HANA and other SAP applications, such as NetWeaver. In this case, all the preceding repositories are required. Optionally, you can modify the */etc/yum.repos.d/rh-cloud-base-sap-ha.repo* file based on your system's specific requirements.
82
88
83
-
5. Upgrade the system to RHEL 8.10:
89
+
6. Upgrade the system to RHEL 8.10:
84
90
85
91
```bash
86
92
sudo dnf update
87
93
```
88
94
89
-
6. Reboot the VM to complete the upgrade:
95
+
7. Reboot the VM to complete the upgrade:
90
96
91
97
```bash
92
98
sudo reboot
@@ -105,14 +111,19 @@ For more information about performing the upgrade process on custom, golden, and
105
111
```bash
106
112
sudo rm /etc/yum/vars/releasever
107
113
```
114
+
3. Create a config file by using this command:
108
115
109
-
3. Install the *rhui-azure-rhel8-base-sap-apps* package:
116
+
```bash
117
+
sudo tee rhel8-base-sap-apps.config > /dev/null <<<$'[rhui-microsoft-azure-rhel8-base-sap-apps]\nname=Microsoft Azure RPMs for Red Hat Enterprise Linux 8 (rhel8-base-sap-apps)\nbaseurl=https://rhui4-1.microsoft.com/pulp/repos/unprotected/microsoft-azure-rhel8-base-sap-apps\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc\nsslverify=1'
118
+
```
119
+
120
+
4. Install the *rhui-azure-rhel8-base-sap-apps* package:
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/windows/performance-diagnostics.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,7 @@ Select one of the following tabs for detailed instructions.
148
148
|**Enable continuous diagnostics**| Get continuous, actionable insights into high resource usage by having data collected every 5 seconds and updates uploaded every 5 minutes to address performance issues promptly. Store insights in your preferred storage account. The storage account retains insights based on the account retention policies that you can configure to [manage the data lifecycle effectively](/azure/storage/blobs/lifecycle-management-policy-configure). You can disable continuous diagnostics at any time. |
149
149
| **Run on-demand diagnostics** | Get on-demand, actionable insights into high resource usage and various system configurations. Receive a downloadable report that provides comprehensive diagnostics data to address performance issues. Store insights and reports in your preferred storage account. The storage account retains insights that are based on the account retention policies that you can configure to [manage the data lifecycle effectively](/azure/storage/blobs/lifecycle-management-policy-configure). You can initiate on-demand diagnostics at any time by using the specific analysis type that you need:<br/><ul><li>**Performance analysis**<br/>Includes all checks in the **Quick analysis** scenario, and monitors high resource consumption. Use this version to troubleshoot general performance issues, such as high CPU, memory, and disk usage. This analysis takes 30 seconds to 15 minutes to run, depending on the selected duration. Learn more [Windows](how-to-use-perfinsights.md) or [Linux](../linux/how-to-use-perfinsights-linux.md)</li><br/><li>**Quick analysis**<br/>Checks for known issues, analyzes best practices, and collects diagnostics data. This analysis takes several minutes to run. Learn more for [Windows](how-to-use-perfinsights.md) or [Linux](../linux/how-to-use-perfinsights-linux.md)</li><br/><li>**Advanced performance analysis** [*Windows only*]<br/>Includes all checks in the **Performance analysis** scenario, and collects one or more of the traces, as listed in the following sections. Use this scenario to troubleshoot complex issues that require more traces. Running this scenario for longer periods increases the overall size of diagnostics output, depending on the size of the VM and the trace options that are selected. This analysis takes 30 seconds to 15 minutes to run, depending on the selected duration. [Learn more](./how-to-use-perfinsights.md)</li><br/><li>**Azure file analysis** [*Windows only*]<br/>Includes all checks in the **Performance analysis** scenario, and captures a network trace and Server Message Block (SMB) counters. Use this scenario to troubleshoot the performance of Azure files. This analysis takes 30 seconds to 15 minutes to run, depending on the selected duration. [Learn more](./how-to-use-perfinsights.md)</li></ul> |
150
150
|**Storage account**| Optionally, if you want to use a single storage account to store the Performance Diagnostics results for multiple VMs, you can select a storage account from the drop-down menu. If you don't specify a storage account, Performance Diagnostics uses the default diagnostics storage account or creates a new storage account. |
151
-
|[Authentication method](#authentication-methods)|Performance Diagnostics supports three authentication methods to write performance diagnostics data to the storage account. They are system-assigned managed identity (default), user-assigned managed identity and storage account access keys. If system-assigned managed identity is selected but not enabled for the VM, Performance Diagnostics will attempt to enable it. If the current user lacks the necessary permissions, this operation may fail. Learn more. |
151
+
|[Authentication method](#authentication-methods)|Performance Diagnostics supports three authentication methods to write performance diagnostics data to the storage account. They are system-assigned managed identity (default), user-assigned managed identity and storage account access keys. If system-assigned managed identity is selected but not enabled for the VM, Performance Diagnostics attempts to enable it. If the current user lacks the necessary permissions, this operation might fail.|
152
152
153
153
5. Review the legal terms and privacy policy, and select the corresponding checkbox to acknowledge acceptance (*required*).
This is the default authentication method. If system-assigned managed identity is selected but not enabled for the VM, Performance Diagnostics will attempt to enable it. If the current user lacks the necessary permissions, this operation may fail. Performance Diagnostics will add the **Storage Table Data Contributor** role and the **Storage Blob Data Contributor** role for the storage account, to the system-assigned managed identity. For more information, see [How to enable system-assigned managed identity on an existing VM](/entra/identity/managed-identities-azure-resources/how-to-configure-managed-identities#enable-system-assigned-managed-identity-on-an-existing-vm).
171
+
This is the default authentication method. If system-assigned managed identity is selected but not enabled for the VM, Performance Diagnostics attempts to enable it. If the current user lacks the necessary permissions, this operation might fail. Performance Diagnostics adds the **Storage Table Data Contributor** role and the **Storage Blob Data Contributor** role for the storage account, to the system-assigned managed identity. For more information, see [How to enable system-assigned managed identity on an existing VM](/entra/identity/managed-identities-azure-resources/how-to-configure-managed-identities#enable-system-assigned-managed-identity-on-an-existing-vm).
172
172
173
173
- User-assigned managed identity
174
174
175
-
User can select one from a list of user-assigned managed identities associated with the VM. Performance Diagnostics will add the **Storage Table Data Contributor** role and the **Storage Blob Data Contributor** role for the storage account, to the user-assigned managed identity. For more information, see [How to assign a user-assigned managed identity to an existing VM](/entra/identity/managed-identities-azure-resources/how-to-configure-managed-identities#assign-a-user-assigned-managed-identity-to-an-existing-vm).
175
+
The user can select one from a list of user-assigned managed identities associated with the VM. Performance Diagnostics adds the **Storage Table Data Contributor** role and the **Storage Blob Data Contributor** role for the storage account, to the user-assigned managed identity. For more information, see [How to assign a user-assigned managed identity to an existing VM](/entra/identity/managed-identities-azure-resources/how-to-configure-managed-identities#assign-a-user-assigned-managed-identity-to-an-existing-vm).
176
176
177
177
- Storage account access keys
178
178
179
-
User can select storage account access keys. If **Allow storage account key access** is disabled for the storage account, the installation operation will fail. For more information, see [Shared key authorization](/azure/storage/common/shared-key-authorization-prevent#disable-shared-key-authorization).
179
+
The user can select storage account access keys. If **Allow storage account key access** is disabled for the storage account, the installation operation fails. For more information, see [Shared key authorization](/azure/storage/common/shared-key-authorization-prevent#disable-shared-key-authorization).
180
180
181
181
To change the authentication method, uninstall Performance Diagnostics and reinstall it.
182
182
183
183
> [!NOTE]
184
-
> Once the managed identities are linked to the VM, it may take a few minutes for them to be propagated and recognized by Performance Diagnostics. If the installation fails, wait a few minutes and try again.
184
+
> Once the managed identities are linked to the VM, it might take a few minutes for them to be propagated and recognized by Performance Diagnostics. If the installation fails, wait a few minutes and try again.
0 commit comments