Merge pull request #192466 from MicrosoftDocs/main

3/22 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -26213,6 +26213,11 @@
       "redirect_url": "/azure/vs-azure-tools-storage-explorer-files",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/storage/files/storage-files-how-to-create-nfs-shares.md",
+      "redirect_url": "/azure/storage/files/storage-files-quick-create-use-linux",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/storage/files/storage-how-to-use-files-powershell.md",
       "redirect_url": "/azure/storage/files/storage-how-to-use-files-portal",

articles/aks/azure-files-csi.md

@@ -3,7 +3,7 @@ title: Use Container Storage Interface (CSI) drivers for Azure Files on Azure Ku
 description: Learn how to use the Container Storage Interface (CSI) drivers for Azure Files in an Azure Kubernetes Service (AKS) cluster.
 services: container-service
 ms.topic: article
-ms.date: 12/10/2021
+ms.date: 03/22/2021
 author: palma21
 
 ---
@@ -276,8 +276,11 @@ kind: StorageClass
 metadata:
   name: azurefile-csi-nfs
 provisioner: file.csi.azure.com
+allowVolumeExpansion: true
 parameters:
   protocol: nfs
+mountOptions:
+  - nconnect=8
 ```
 
 After editing and saving the file, create the storage class with the [kubectl apply][kubectl-apply] command:

articles/aks/azure-files-dynamic-pv.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Kubernetes Service
 description: Learn how to dynamically create a persistent volume with Azure Files for use with multiple concurrent pods in Azure Kubernetes Service (AKS)
 services: container-service
 ms.topic: article
-ms.date: 07/01/2020
+ms.date: 03/22/2021
 
 
 #Customer intent: As a developer, I want to learn how to dynamically create and attach storage using Azure Files to pods in AKS.
@@ -46,6 +46,7 @@ apiVersion: storage.k8s.io/v1
 metadata:
   name: my-azurefile
 provisioner: file.csi.azure.com # replace with "kubernetes.io/azure-file" if aks version is less than 1.21
+allowVolumeExpansion: true
 mountOptions:
   - dir_mode=0777
   - file_mode=0777
@@ -55,7 +56,7 @@ mountOptions:
   - cache=strict
   - actimeo=30
 parameters:
-  skuName: Standard_LRS
+  skuName: Premium_LRS
 ```
 
 Create the storage class with the [kubectl apply][kubectl-apply] command:
@@ -66,7 +67,7 @@ kubectl apply -f azure-file-sc.yaml
 
 ## Create a persistent volume claim
 
-A persistent volume claim (PVC) uses the storage class object to dynamically provision an Azure file share. The following YAML can be used to create a persistent volume claim *5 GB* in size with *ReadWriteMany* access. For more information on access modes, see the [Kubernetes persistent volume][access-modes] documentation.
+A persistent volume claim (PVC) uses the storage class object to dynamically provision an Azure file share. The following YAML can be used to create a persistent volume claim *100 GB* in size with *ReadWriteMany* access. For more information on access modes, see the [Kubernetes persistent volume][access-modes] documentation.
 
 Now create a file named `azure-file-pvc.yaml` and copy in the following YAML. Make sure that the *storageClassName* matches the storage class created in the last step:
 
@@ -81,7 +82,7 @@ spec:
   storageClassName: my-azurefile
   resources:
     requests:
-      storage: 5Gi
+      storage: 100Gi
 ```
 
 > [!NOTE]
@@ -99,7 +100,7 @@ Once completed, the file share will be created. A Kubernetes secret is also crea
 $ kubectl get pvc my-azurefile
 
 NAME           STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
-my-azurefile   Bound     pvc-8436e62e-a0d9-11e5-8521-5a8664dc0477   5Gi        RWX            my-azurefile      5m
+my-azurefile   Bound     pvc-8436e62e-a0d9-11e5-8521-5a8664dc0477   10Gi       RWX            my-azurefile      5m
 ```
 
 ## Use the persistent volume
@@ -172,6 +173,7 @@ apiVersion: storage.k8s.io/v1
 metadata:
   name: my-azurefile
 provisioner: file.csi.azure.com # replace with "kubernetes.io/azure-file" if aks version is less than 1.21
+allowVolumeExpansion: true
 mountOptions:
   - dir_mode=0777
   - file_mode=0777
@@ -181,7 +183,7 @@ mountOptions:
   - cache=strict
   - actimeo=30
 parameters:
-  skuName: Standard_LRS
+  skuName: Premium_LRS
 ```
 
 ## Using Azure tags

articles/api-management/api-management-cross-domain-policies.md

@@ -64,6 +64,9 @@ The `cors` policy adds cross-origin resource sharing (CORS) support to an operat
 > [!NOTE]
 > If request matches an operation with an OPTIONS method defined in the API, pre-flight request processing logic associated with CORS policies will not be executed. Therefore, such operations can be used to implement custom pre-flight processing logic.
 
+> [!IMPORTANT]
+> If you configure the CORS policy at the product scope, and your API uses subscription key authentication, the policy will only work when requests include a subscription key as a query parameter. 
+
 CORS allows a browser and a server to interact and determine whether or not to allow specific cross-origin requests (i.e. XMLHttpRequests calls made from JavaScript on a web page to other domains). This allows for more flexibility than only allowing same-origin requests, but is more secure than allowing all cross-origin requests.
 
 You need to apply the CORS policy to enable the interactive console in the developer portal. Refer to the [developer portal documentation](./developer-portal-faq.md#cors) for details.

articles/app-service/quickstart-nodejs.md

@@ -3,9 +3,10 @@ title: 'Quickstart: Create a Node.js web app'
 description: Deploy your first Node.js Hello World to Azure App Service in minutes.
 ms.assetid: 582bb3c2-164b-42f5-b081-95bfcb7a502a
 ms.topic: quickstart
-ms.date: 03/10/2022
+ms.custom: mvc, devcenter, seodec18, devdivchpfy22
+#zone_pivot_groups: app-service-platform-windows-linux
+ms.date: 03/22/2022
 ms.devlang: javascript
-ms.custom: mvc, devcenter, seodec18, mode-api
 #zone_pivot_groups: app-service-ide-oss
 zone_pivot_groups: app-service-vscode-cli-portal
 ---
@@ -45,12 +46,12 @@ This quickstart configures an App Service app in the **Free** tier and incurs no
 ::: zone-end
 ## Create your Node.js application
 
-In this step, you create a starter Node.js application and make sure it runs on your computer.
+In this step, you create a basic Node.js application and ensure it runs on your computer.
 
 > [!TIP]
 > If you have already completed the [Node.js tutorial](https://code.visualstudio.com/docs/nodejs/nodejs-tutorial), you can skip ahead to [Deploy to Azure](#deploy-to-azure).
 
-1. Create a simple Node.js application using the [Express Generator](https://expressjs.com/starter/generator.html), which is installed by default with Node.js and NPM.
+1. Create a Node.js application using the [Express Generator](https://expressjs.com/starter/generator.html), which is installed by default with Node.js and NPM.
 
     ```bash
     npx express-generator myExpressApp --view ejs
@@ -89,7 +90,7 @@ Before you continue, ensure that you have all the prerequisites installed and co
 
 #### Sign in to Azure
 
-1. In the terminal, make sure you're in the *myExpressApp* directory, then start Visual Studio Code with the following command:
+1. In the terminal, ensure you're in the *myExpressApp* directory, then start Visual Studio Code with the following command:
 
     ```bash
     code .
@@ -112,14 +113,14 @@ Before you continue, ensure that you have all the prerequisites installed and co
 
     :::image type="content" source="media/quickstart-nodejs/deploy.png" alt-text="Screenshot of the Azure App service in Visual Studio Code showing the blue arrow icon selected.":::
 
-1. Choose the *myExpressApp* folder.
+1. Select the *myExpressApp* folder.
 
 # [Deploy to Linux](#tab/linux)
 
-3. Choose **Create new Web App**. A Linux container is used by default.
+3. Select **Create new Web App**. A Linux container is used by default.
 1. Type a globally unique name for your web app and press **Enter**. The name must be unique across all of Azure and use only alphanumeric characters ('A-Z', 'a-z', and '0-9') and hyphens ('-').
 1. In Select a runtime stack, select the Node.js version you want. An **LTS** version is recommended.
-1. In Select a pricing tier, select **Free (F1)** and wait for the the resources to be provisioned in Azure.
+1. In Select a pricing tier, select **Free (F1)** and wait for the resources to be provisioned in Azure.
 1. In the popup **Always deploy the workspace "myExpressApp" to \<app-name>"**, select **Yes**. This way, as long as you're in the same workspace, Visual Studio Code deploys to the same App Service app each time.
 
     While Visual Studio Code provisions the Azure resources and deploys the code, it shows [progress notifications](https://code.visualstudio.com/api/references/extension-guidelines#notifications).
@@ -128,7 +129,7 @@ Before you continue, ensure that you have all the prerequisites installed and co
 
 # [Deploy to Windows](#tab/windows)
 
-3. Choose **Create new Web App... Advanced**.
+3. Select **Create new Web App... Advanced**.
 1. Type a globally unique name for your web app and press **Enter**. The name must be unique across all of Azure and use only alphanumeric characters ('A-Z', 'a-z', and '0-9') and hyphens ('-').
 1. Select **Create a new resource group**, then enter a name for the resource group, such as *AppServiceQS-rg*.
 1. Select the Node.js version you want. An **LTS** version is recommended.
@@ -164,7 +165,7 @@ Before you continue, ensure that you have all the prerequisites installed and co
 
 :::zone target="docs" pivot="development-environment-cli"
 
-In the terminal, make sure you're in the *myExpressApp* directory, and deploy the code in your local folder (*myExpressApp*) using the [az webapp up](/cli/azure/webapp#az-webapp-up) command:
+In the terminal, ensure you're in the *myExpressApp* directory, and deploy the code in your local folder (*myExpressApp*) using the [az webapp up](/cli/azure/webapp#az-webapp-up) command:
 
 # [Deploy to Linux](#tab/linux)
 
@@ -180,12 +181,12 @@ az webapp up --sku F1 --name <app-name> --os-type Windows
 
 -----
 
-- If the `az` command isn't recognized, be sure you have the Azure CLI installed as described in [Set up your initial environment](#set-up-your-initial-environment).
+- If the `az` command isn't recognized, ensure you have the Azure CLI installed as described in [Set up your initial environment](#set-up-your-initial-environment).
 - Replace `<app_name>` with a name that's unique across all of Azure (*valid characters are `a-z`, `0-9`, and `-`*). A good pattern is to use a combination of your company name and an app identifier.
 - The `--sku F1` argument creates the web app on the Free pricing tier, which incurs a no cost.
 - You can optionally include the argument `--location <location-name>` where `<location_name>` is an available Azure region. You can retrieve a list of allowable regions for your Azure account by running the [`az account list-locations`](/cli/azure/appservice#az_appservice_list_locations) command.
 - The command creates a Linux app for Node.js by default. To create a Windows app instead, use the `--os-type` argument. 
-- If you see the error, "Could not auto-detect the runtime stack of your app," make sure you're running the command in the *myExpressApp* directory (See [Troubleshooting auto-detect issues with az webapp up](https://github.com/Azure/app-service-linux-docs/blob/master/AzWebAppUP/runtime_detection.md)).
+- If you see the error, "Could not auto-detect the runtime stack of your app," ensure you're running the command in the *myExpressApp* directory (See [Troubleshooting auto-detect issues with az webapp up](https://github.com/Azure/app-service-linux-docs/blob/master/AzWebAppUP/runtime_detection.md)).
 
 The command may take a few minutes to complete. While running, it provides messages about creating the resource group, the App Service plan, and the app resource, configuring logging, and doing ZIP deployment. It then gives the message, "You can launch the app at http://&lt;app-name&gt;.azurewebsites.net", which is the app's URL on Azure.
 
@@ -231,15 +232,15 @@ Sign in to the Azure portal at https://portal.azure.com.
      :::image type="content" source="./media/quickstart-nodejs/portal-search.png?text=Azure portal search details" alt-text="Screenshot of portal search":::
 
 1. In the **App Services** page, select **Create**.
-1. In the **Basics** tab, under **Project details**, make sure the correct subscription is selected and then choose to **Create new** resource group. Type *myResourceGroup* for the name.
+1. In the **Basics** tab, under **Project details**, ensure the correct subscription is selected and then select to **Create new** resource group. Type *myResourceGroup* for the name.
 
     :::image type="content" source="./media/quickstart-nodejs/project-details.png" alt-text="Screenshot of the Project details section showing where you select the Azure subscription and the resource group for the web app":::
 
-1. Under **Instance details**, type a globally unique name for your web app and select **Code**. Choose *Node 14 LTS* **Runtime stack**, an **Operating System**, and a **Region** you want to serve your app from.
+1. Under **Instance details**, type a globally unique name for your web app and select **Code**. Select *Node 14 LTS* **Runtime stack**, an **Operating System**, and a **Region** you want to serve your app from.
 
     :::image type="content" source="./media/quickstart-nodejs/instance-details.png" alt-text="Screenshot of the Instance details section where you provide a name for the virtual machine and select its region, image and size":::
 
-1. Under **App Service Plan**, choose to **Create new** App Service Plan. Type *myAppServicePlan* for the name. To change to the Free tier, click **Change size**, select **Dev/Test** tab, select **F1**, and select the **Apply** button at the bottom of the page.
+1. Under **App Service Plan**, select **Create new** App Service Plan. Type *myAppServicePlan* for the name. To change to the Free tier, select **Change size**, select **Dev/Test** tab, select **F1**, and select the **Apply** button at the bottom of the page.
 
     :::image type="content" source="./media/quickstart-nodejs/app-service-plan-details.png" alt-text="Screenshot of the Administrator account section where you provide the administrator username and password":::
 
@@ -255,9 +256,9 @@ Sign in to the Azure portal at https://portal.azure.com.
 
 ### Get FTP credentials
 
-Azure App Service supports [**two types of credentials**](deploy-configure-credentials.md) for FTP/S deployment. These credentials are not the same as your Azure subscription credentials. In this section, you get the *application-scope credentials* to use with FileZilla.
+Azure App Service supports [**two types of credentials**](deploy-configure-credentials.md) for FTP/S deployment. These credentials aren't the same as your Azure subscription credentials. In this section, you get the *application-scope credentials* to use with FileZilla.
 
-1. From the App Service app page, click **Deployment Center** in the left-hand menu and select **FTPS credentials** tab.
+1. From the App Service app page, select **Deployment Center** in the left-hand menu and select **FTPS credentials** tab.
 
     :::image type="content" source="./media/quickstart-nodejs/ftps-deployment-credentials.png" alt-text="FTPS deployment credentials":::
 
@@ -267,7 +268,7 @@ Azure App Service supports [**two types of credentials**](deploy-configure-crede
 
     :::image type="content" source="./media/quickstart-nodejs/filezilla-ftps-connection.png" alt-text="FTPS connection details":::
 
-1. Click **Connect** in FileZilla.
+1. Select **Connect** in FileZilla.
 
 ### Deploy files with FTP
 
@@ -330,11 +331,11 @@ You can deploy changes to this app by making edits in Visual Studio Code, saving
 
 You can stream log output (calls to `console.log()`) from the Azure app directly in the Visual Studio Code output window.
 
-1. In the **App Service** explorer, right-click the app node and choose **Start Streaming Logs**.
+1. In the **App Service** explorer, right-click the app node and select **Start Streaming Logs**.
 
     ![Start Streaming Logs](./media/quickstart-nodejs/view-logs.png)
 
-1. If asked to restart the app, click **Yes**. Once the app is restarted, the Visual Studio Code output window opens with a connection to the log stream.
+1. If asked to restart the app, select **Yes**. Once the app is restarted, the Visual Studio Code output window opens with a connection to the log stream.
 
 1. After a few seconds, the output window shows a message indicating that you're connected to the log-streaming service. You can generate more output activity by refreshing the page in the browser.
 
@@ -373,7 +374,7 @@ To stop log streaming at any time, press **Ctrl**+**C** in the terminal.
 
 You can access the console logs generated from inside the app and the container in which it runs. You can stream log output (calls to `console.log()`) from the Node.js app directly in the Azure portal.
 
-1. In the same **App Service** page for your app, use the left menu to scroll to the *Monitoring* section and click **Log stream**.
+1. In the same **App Service** page for your app, use the left menu to scroll to the *Monitoring* section and select **Log stream**.
 
     :::image type="content" source="./media/quickstart-nodejs/log-stream.png" alt-text="Screenshot of Log stream in Azure App service.":::
 
@@ -390,7 +391,7 @@ You can access the console logs generated from inside the app and the container
     2021-10-26T21:04:08.614403210Z: [INFO]
     2021-10-26T21:04:08.614407110Z: [INFO]  export NODE_PATH=/usr/local/lib/node_modules:$NODE_PATH
     2021-10-26T21:04:08.614411210Z: [INFO]  if [ -z "$PORT" ]; then
-    2021-10-26T21:04:08.614415310Z: [INFO]  		export PORT=8080
+    2021-10-26T21:04:08.614415310Z: [INFO]          export PORT=8080
     2021-10-26T21:04:08.614419610Z: [INFO]  fi
     2021-10-26T21:04:08.614423411Z: [INFO]
     2021-10-26T21:04:08.614427211Z: [INFO]  node /opt/startup/default-static-site.js
@@ -439,7 +440,7 @@ The `--no-wait` argument allows the command to return before the operation is co
 
 When no longer needed, you can delete the resource group, App service, and all related resources.
 
-1. From your App Service *overview* page, click the *resource group* you created in the [Create Azure resources](#create-azure-resources) step.
+1. From your App Service *overview* page, select the *resource group* you created in the [Create Azure resources](#create-azure-resources) step.
 
     :::image type="content" source="./media/quickstart-nodejs/resource-group.png" alt-text="Resource group in App Service overview page":::
 
@@ -468,4 +469,4 @@ Check out the other Azure extensions.
 * [Azure Resource Manager Tools](https://marketplace.visualstudio.com/items?itemName=msazurermtools.azurerm-vscode-tools)
 
 Or get them all by installing the
-[Node Pack for Azure](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-node-azure-pack) extension pack.
+[Node Pack for Azure](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-node-azure-pack) extension pack.