Merge pull request #291486 from MicrosoftDocs/main

v-ccolin · web-flow · commit 620cecf2dfc9 · 2024-12-05T12:13:56.000Z
Merge main to live, 4 AM
diff --git a/articles/automation/TOC.yml b/articles/automation/TOC.yml
@@ -59,6 +59,8 @@
       href: automation-runbook-types.md
     - name: Automation Runtime environment
       href: runtime-environment-overview.md
+    - name: Automation limits and quotas
+      href: automation-subscription-limits-faq.md
     - name: PowerShell DSC
       href: /powershell/dsc/overview
     - name: Automation network configuration details
diff --git a/articles/automation/automation-subscription-limits-faq.md b/articles/automation/automation-subscription-limits-faq.md
@@ -0,0 +1,54 @@
+---
+title: Azure Automation subscription limits and quotas
+description: This article provides automation subscription and service limits and includes answers to frequently asked questions.
+services: automation
+ms.topic: faq
+ms.date: 12/05/2024
+ms.custom: references_regions
+#Customer intent: As an implementer, I want answers to various questions.
+---
+
+# Azure Automation limits and quotas
+
+Azure Automation will soon revise its service and subscription limits to ensure fair distribution of cloud resources across all customers. This change is another step to improve the reliability and performance of the service while optimizing resource utilization. Since the resource requirements vary across organizations and evolve over time, we aim to empower customers to configure their quotas based on actual usage. [Learn more](https://techcommunity.microsoft.com/blog/AzureGovernanceandManagementBlog/azure-automation-is-revising-service-and-subscription-limits/4351067).
+
+## Revised limits
+
+For more information on the current service and subscription limits, see [Automation limits](https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#process-automation).
+
+The following limits would be changed:
+- Maximum number of active Automation accounts in a subscription in a region. 
+- Maximum number of concurrent running jobs at the same instance of time per Automation account. 
+ 
+**Resource** | **Limit** | **Notes** |
+|---|--- | --- |
+|Maximum number of active Automation accounts in a subscription in a region. | 10 </br></br></br> 2 </br></br></br></br> 1 | Enterprise and CSP subscriptions would be able to create accounts in any of the [regions supported](https://azure.microsoft.com/pricing/details/automation/) by the service. </br></br> Pay-as-you-go, Sponsored, MSDN, MPN, Azure Pass subscriptions can create Automation accounts in any of the [regions supported](https://azure.microsoft.com/pricing/details/automation/) by the service. </br></br>  Free trial, Azure for Student, Azure in Open subscriptions can create only one Automation account per region per subscription. Allowed list of regions: EastUS, EastUS2, WestUS, NorthEurope, SoutheastAsia, and JapanWest2 |
+|Maximum number of concurrent running jobs at the same instance of time per Automation account per region. | 50 </br></br> 10 </br> </br> 5 | Enterprise and CSP subscriptions.</br> </br> Pay-as-you-go, Sponsored, MSDN, MPN, Azure Pass subscriptions. </br></br> Free trial, Azure for Student, Azure in Open subscriptions.|  
+
+> [!NOTE]
+> You get an error message when you exceed the limits mentioned above.
+
+## Frequently asked questions
+
+
+### How do I check my current limits?
+
+You'll be able to check your current limits while creating a support request under the category *Service and Subscription limits (Quotas) -> Azure Automation*. 
+
+### My current usage is more than the revised limits.  What should I do?
+
+Rest assured that your current usage of both resources - Automation accounts and concurrently running jobs - is honored and remains unaffected.
+
+### I need more resources than my current limits. What should I do?
+
+You can request for quota increase by creating a support request under the category *Service and Subscription limits (Quotas) -> Azure Automation*. [Learn more](https://techcommunity.microsoft.com/blog/azuregovernanceandmanagementblog/azure-automation-is-revising-service-and-subscription-limits/4351067).
+
+### How do quota requests impact my subscription's billing?
+
+Support requests for quota changes don't have any additional impact on your subscription billing. You can use your existing support plan to request for quota changes. 
+
+## Next steps
+
+If your question isn't answered here, refer to the following sources for more questions and answers.
+
+- [Feedback forum](https://feedback.azure.com/d365community/forum/721a322e-bd25-ec11-b6e6-000d3a4f0f1c)
diff --git a/articles/azure-web-pubsub/quickstart-serverless.md b/articles/azure-web-pubsub/quickstart-serverless.md
@@ -29,7 +29,7 @@ In this tutorial, you learn how to:
 
 - A code editor, such as [Visual Studio Code](https://code.visualstudio.com/)
 
-- [Node.js](https://nodejs.org/en/download/), version 18.x or above.
+- [Node.js](https://nodejs.org/en/download/package-manager/), version 18.x or above.
   > [!NOTE]
   > For more information about the supported versions of Node.js, see [Azure Functions runtime versions documentation](../azure-functions/functions-versions.md#languages).
 - [Azure Functions Core Tools](https://github.com/Azure/azure-functions-core-tools#installing) (v4 or higher preferred) to run Azure Function apps locally and deploy to Azure.
@@ -40,7 +40,7 @@ In this tutorial, you learn how to:
 
 - A code editor, such as [Visual Studio Code](https://code.visualstudio.com/)
 
-- [Node.js](https://nodejs.org/en/download/), version 18.x or above.
+- [Node.js](https://nodejs.org/en/download/package-manager/), version 18.x or above.
   > [!NOTE]
   > For more information about the supported versions of Node.js, see [Azure Functions runtime versions documentation](../azure-functions/functions-versions.md#languages).
 - [Azure Functions Core Tools](https://github.com/Azure/azure-functions-core-tools#installing) (v4 or higher preferred) to run Azure Function apps locally and deploy to Azure.
diff --git a/articles/azure-web-pubsub/tutorial-serverless-notification.md b/articles/azure-web-pubsub/tutorial-serverless-notification.md
@@ -27,7 +27,7 @@ In this tutorial, you learn how to:
 
 * A code editor, such as [Visual Studio Code](https://code.visualstudio.com/)
 
-* [Node.js](https://nodejs.org/en/download/), version 18.x or above.
+* [Node.js](https://nodejs.org/en/download/package-manager/), version 18.x or above.
    > [!NOTE]
    > For more information about the supported versions of Node.js, see [Azure Functions runtime versions documentation](../azure-functions/functions-versions.md#languages).
 
@@ -39,7 +39,7 @@ In this tutorial, you learn how to:
 
 * A code editor, such as [Visual Studio Code](https://code.visualstudio.com/)
 
-* [Node.js](https://nodejs.org/en/download/), version 18.x or above.
+* [Node.js](https://nodejs.org/en/download/package-manager/), version 18.x or above.
    > [!NOTE]
    > For more information about the supported versions of Node.js, see [Azure Functions runtime versions documentation](../azure-functions/functions-versions.md#languages).
 
diff --git a/articles/energy-data-services/includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md b/articles/energy-data-services/includes/how-to/how-to-deploy-gcz/deploy-gcz-on-aks.md
@@ -316,7 +316,7 @@ Learn how to deploy Geospatial Consumption Zone (GCZ) on Azure Kubernetes Servic
 1. Deploy the GCZ HELM chart:
 
    ```bash
-   helm upgrade -i $CHART . -n $NAMESPACE -f osdu_gcz_custom_values.yaml --set-file global.provider.configLoaderJs="gcz-provider/gcz-provider-core/config/configLoader.js"
+   helm upgrade -i $CHART . -n $NAMESPACE -f osdu_gcz_custom_values.yaml --set-file global.provider.configLoaderJs="../../../../gcz-provider/gcz-provider-core/config/configLoader.js"
    ```
 
 1. Verify the deployment:
diff --git a/articles/logic-apps/add-run-javascript.md b/articles/logic-apps/add-run-javascript.md
@@ -54,7 +54,7 @@ The following diagram shows the highlights from example workflow:
 
   * Consumption workflow
 
-    * [Node.js version 8.11.10](https://nodejs.org/en/download/releases/)
+    * [Node.js version 8.11.10](https://nodejs.org/en/about/previous-releases)
 
     * [Link to an integration account](logic-apps-enterprise-integration-create-integration-account.md), empty or otherwise, from your logic app resource.
 
@@ -73,7 +73,7 @@ The following diagram shows the highlights from example workflow:
 
   * Standard workflow
 
-    * [Node.js versions 16.x.x](https://nodejs.org/en/download/releases/)
+    * [Node.js versions 16.x.x](https://nodejs.org/en/about/previous-releases)
 
     * No integration account required.
 
diff --git a/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md b/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md
@@ -94,7 +94,7 @@ As you progress, you'll complete these high-level tasks:
    | [Azurite for Visual Studio Code](https://github.com/Azure/Azurite#visual-studio-code-extension) | Provides a local data store and emulator to use with Visual Studio Code so that you can work on your logic app project and run your workflows in your local development environment. If you don't want Azurite to automatically start, you can disable this option: <br><br>1. On the **File** menu, select **Preferences** > **Settings**. <br><br>2. On the **User** tab, select **Extensions** > **Azure Logic Apps (Standard)**. <br><br>3. Find the setting named **Azure Logic Apps Standard: Auto Start Azurite**, and clear the selected checkbox. |
    | [.NET SDK 6.x.x](https://dotnet.microsoft.com/download/dotnet/6.0) | Includes the .NET Runtime 6.x.x, a prerequisite for the Azure Logic Apps (Standard) runtime. |
    | Azure Functions Core Tools - 4.x version | Installs the version based on your operating system ([Windows](https://github.com/Azure/azure-functions-core-tools/releases), [macOS](../azure-functions/functions-run-local.md?tabs=macos#install-the-azure-functions-core-tools), or [Linux](../azure-functions/functions-run-local.md?tabs=linux#install-the-azure-functions-core-tools)). <br><br>These tools include a version of the same runtime that powers the Azure Functions runtime, which the Azure Logic Apps (Standard) extension uses in Visual Studio Code. |
-   | [Node.js version 16.x.x unless a newer version is already installed](https://nodejs.org/en/download/releases/) | Required to enable the [Inline Code Operations action](../logic-apps/logic-apps-add-run-inline-code.md) that runs JavaScript. |
+   | [Node.js version 16.x.x unless a newer version is already installed](https://nodejs.org/en/about/previous-releases) | Required to enable the [Inline Code Operations action](../logic-apps/logic-apps-add-run-inline-code.md) that runs JavaScript. |
 
    The installer doesn't perform the following tasks:
 
@@ -205,7 +205,7 @@ As you progress, you'll complete these high-level tasks:
    |------------|-------------|
    | [.NET SDK 6.x.x](https://dotnet.microsoft.com/download/dotnet/6.0) | Includes the .NET Runtime 6.x.x, a prerequisite for the Azure Logic Apps (Standard) runtime. |
    | Azure Functions Core Tools - 4.x version | - [Windows](https://github.com/Azure/azure-functions-core-tools/releases): Use the Microsoft Installer (MSI) version, which is `func-cli-X.X.XXXX-x*.msi`. <br>- [macOS](../azure-functions/functions-run-local.md?tabs=macos#install-the-azure-functions-core-tools) <br>- [Linux](../azure-functions/functions-run-local.md?tabs=linux#install-the-azure-functions-core-tools) <br><br>These tools include a version of the same runtime that powers the Azure Functions runtime, which the Azure Logic Apps (Standard) extension uses in Visual Studio Code. <br><br>If you have an installation that's earlier than these versions, uninstall that version first, or make sure that the PATH environment variable points at the version that you download and install. |
-   | [Node.js version 16.x.x unless a newer version is already installed](https://nodejs.org/en/download/releases/) | Required to enable the [Inline Code Operations action](../logic-apps/logic-apps-add-run-inline-code.md) that runs JavaScript. <br><br>**Note**: For Windows, download the MSI version. If you use the ZIP version instead, you have to manually make Node.js available by using a PATH environment variable for your operating system. |
+   | [Node.js version 16.x.x unless a newer version is already installed](https://nodejs.org/en/about/previous-releases) | Required to enable the [Inline Code Operations action](../logic-apps/logic-apps-add-run-inline-code.md) that runs JavaScript. <br><br>**Note**: For Windows, download the MSI version. If you use the ZIP version instead, you have to manually make Node.js available by using a PATH environment variable for your operating system. |
 
 1. If you already installed the version of the Azure Logic Apps (Standard) extension that automatically installs all the dependencies (preview), skip this step. Otherwise, [download and install the Azure Logic Apps (Standard) extension for Visual Studio Code](https://go.microsoft.com/fwlink/p/?linkid=2143167).
 
diff --git a/articles/storage/blobs/quickstart-blobs-javascript-browser.md b/articles/storage/blobs/quickstart-blobs-javascript-browser.md
@@ -35,7 +35,7 @@ Additional resources:
 
 - [An Azure account with an active subscription](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio)
 - [An Azure Storage account](../common/storage-account-create.md)
-- [Node.js LTS](https://nodejs.org/en/download/)
+- [Node.js LTS](https://nodejs.org/en/download/package-manager/)
 - [Microsoft Visual Studio Code](https://code.visualstudio.com)
 
 
diff --git a/articles/storage/blobs/storage-quickstart-blobs-nodejs-typescript.md b/articles/storage/blobs/storage-quickstart-blobs-nodejs-typescript.md
@@ -23,7 +23,7 @@ In this article, you follow steps to install the package and try out example cod
 
 - Azure account with an active subscription - [create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio)
 - Azure Storage account - [Create a storage account](../common/storage-account-create.md)
-- [Node.js LTS](https://nodejs.org/en/download/)
+- [Node.js LTS](https://nodejs.org/en/download/package-manager/)
 - [TypeScript](https://www.typescriptlang.org/download)
 
 ## Setting up
diff --git a/articles/storage/blobs/storage-quickstart-blobs-nodejs.md b/articles/storage/blobs/storage-quickstart-blobs-nodejs.md
@@ -50,14 +50,14 @@ In this article, you use the [Azure Developer CLI](/azure/developer/azure-develo
 
 - Azure account with an active subscription - [create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio)
 - Azure Storage account - [Create a storage account](../common/storage-account-create.md)
-- [Node.js LTS](https://nodejs.org/en/download/)
+- [Node.js LTS](https://nodejs.org/en/download/package-manager/)
 
 ::: zone-end
 
 ::: zone pivot="blob-storage-quickstart-template"
 
 - Azure subscription - [create one for free](https://azure.microsoft.com/free/)
-- [Node.js LTS](https://nodejs.org/en/download/)
+- [Node.js LTS](https://nodejs.org/en/download/package-manager/)
 - [Azure Developer CLI](/azure/developer/azure-developer-cli/install-azd)
 
 ::: zone-end
diff --git a/articles/storage/container-storage/container-storage-introduction.md b/articles/storage/container-storage/container-storage-introduction.md
@@ -40,7 +40,7 @@ Azure Container Storage offers persistent volume support with ReadWriteOnce acce
 |------------------|-----------------|---------------|---------------|------------------------|
 | **[Azure Elastic SAN](../elastic-san/elastic-san-introduction.md)** (Preview)| Provision on demand, fully managed resource | General purpose databases, streaming and messaging services, CD/CI environments, and other tier 1/tier 2 workloads. | Azure Elastic SAN | Provisioned on demand per created volume and volume snapshot. Multiple clusters can access a single SAN concurrently, however persistent volumes can only be attached by one consumer at a time. |
 | **[Azure Disks](/azure/virtual-machines/managed-disks-overview)** | Granular control of storage SKUs and configurations​ | Azure Disks are a good fit for tier 1 and general purpose databases such as MySQL, MongoDB, and PostgreSQL. | Premium SSD, Premium SSD v2, Standard SSD, Ultra Disk | Provisioned per target container storage pool size and maximum volume size. |
-| **Ephemeral Disk** | Utilizes local storage resources on AKS nodes (NVMe or temp SSD) | Ephemeral disk is extremely latency sensitive (low sub-ms latency), so it's best for applications with no data durability requirement or with built-in data replication support such as Cassandra. | NVMe is available on [storage optimized VM SKUs](/azure/virtual-machines/sizes-storage) | Deployed as part of the VMs hosting an AKS cluster. AKS discovers the available ephemeral storage on AKS nodes and acquires them for volume deployment. |
+| **Ephemeral Disk** | Utilizes local storage resources on AKS nodes (NVMe or temp SSD) | Ephemeral disk is extremely latency sensitive (low sub-ms latency), so it's best for applications with no data durability requirement or with built-in data replication support such as Cassandra. | NVMe is available on some Azure VM SKUs, for example, [Storage optimized VM SKUs](/azure/virtual-machines/sizes/overview#storage-optimized) or [GPU accelerated VM SKUs](/azure/virtual-machines/sizes/overview#gpu-accelerated) | Deployed as part of the VMs hosting an AKS cluster. AKS discovers the available ephemeral storage on AKS nodes and acquires them for volume deployment. |
 
 ### Feature support for different storage types
 
@@ -67,7 +67,7 @@ Feature support depends on which backing storage option you select. The followin
 
 Our latest updates enhance the resiliency and performance of stateful containers. We now offer multi-zone storage pools and volume replication for local NVMe storage pools, ensuring availability during single node failures. Snapshot support is available across all storage options for backup and disaster recovery. Additionally, the Ephemeral Disk portfolio now includes temp SSD support, providing cost-efficient solutions for use cases leveraging directly attached local storage: 
 
-- Enhance the resiliency of your persistent volumes hosted on local NVMe storage (L-series ephemeral disks) with replication support.
+- Enhance the resiliency of your persistent volumes hosted on local NVMe storage with replication support.
 - Improved persistent volume recovery after a restart of an Azure Kubernetes Service (AKS) cluster.
 - Customize the performance of your local NVMe storage with new performance tier options.
 
diff --git a/articles/storage/container-storage/install-container-storage-aks.md b/articles/storage/container-storage/install-container-storage-aks.md
@@ -121,7 +121,7 @@ To use Azure Container Storage, you'll need a node pool of at least three Linux
 Follow these guidelines when choosing a VM type for the cluster nodes. You must choose a VM type that supports [Azure premium storage](/azure/virtual-machines/premium-storage-performance).
 
 - If you intend to use Azure Elastic SAN or Azure Disks as backing storage, choose a [general purpose VM type](/azure/virtual-machines/sizes-general) such as **standard_d4s_v5**.
-- If you intend to use Ephemeral Disk with local NVMe, choose a [storage optimized VM type](/azure/virtual-machines/sizes-storage) such as **standard_l8s_v3**.
+- If you intend to use Ephemeral Disk with local NVMe, choose a VM SKU that support local NVMe disks, for example, [Storage optimized VM SKUs](/azure/virtual-machines/sizes/overview#storage-optimized) or [GPU accelerated VM SKUs](/azure/virtual-machines/sizes/overview#gpu-accelerated).
 - If you intend to use Ephemeral Disk with temp SSD, choose a VM that has a temp SSD disk such as [Ev3 and Esv3-series](/azure/virtual-machines/ev3-esv3-series).
 
 ## Create a new AKS cluster and install Azure Container Storage
diff --git a/articles/storage/container-storage/use-container-storage-with-local-disk.md b/articles/storage/container-storage/use-container-storage-with-local-disk.md
@@ -27,7 +27,7 @@ Due to the ephemeral nature of these disks, Azure Container Storage supports the
 
 ## Choose a VM type that supports local NVMe
 
-Ephemeral Disk is only available in certain types of VMs. If you plan to use local NVMe, a [storage optimized VM](/azure/virtual-machines/sizes-storage) such as **standard_l8s_v3** is required.
+Local NVMe Disk is only available in certain types of VMs, for example, [Storage optimized VM SKUs](/azure/virtual-machines/sizes/overview#storage-optimized) or [GPU accelerated VM SKUs](/azure/virtual-machines/sizes/overview#gpu-accelerated). If you plan to use local NVMe capacity, choose one of these VM SKUs.
 
 Run the following command to get the VM type that's used with your node pool. Replace `<resource group>` and `<cluster name>` with your own values. You don't need to supply values for `PoolName` or `VmSize`, so keep the query as shown here.
 
diff --git a/articles/storage/container-storage/use-container-storage-with-local-nvme-replication.md b/articles/storage/container-storage/use-container-storage-with-local-nvme-replication.md
@@ -27,7 +27,7 @@ Due to the ephemeral nature of these disks, Azure Container Storage supports the
 
 ## Choose a VM type that supports local NVMe
 
-Ephemeral Disk is only available in certain types of VMs. If you plan to use local NVMe, a [storage optimized VM](/azure/virtual-machines/sizes-storage) such as **standard_l8s_v3** is required.
+Local NVMe Disk is only available in certain types of VMs, for example, [Storage optimized VM SKUs](/azure/virtual-machines/sizes/overview#storage-optimized) or [GPU accelerated VM SKUs](/azure/virtual-machines/sizes/overview#gpu-accelerated). If you plan to use local NVMe, choose one of these VM SKUs.
 
 Run the following command to get the VM type that's used with your node pool. Replace `<resource group>` and `<cluster name>` with your own values. You don't need to supply values for `PoolName` or `VmSize`, so keep the query as shown here.
 
diff --git a/articles/storage/queues/storage-quickstart-queues-nodejs.md b/articles/storage/queues/storage-quickstart-queues-nodejs.md
