Merge pull request #6999 from diberry/diberry/0307-url-allowlist-fixes

prmerger-automator[bot] · web-flow · commit 237c106e7e9d · 2025-03-07T20:34:14.000Z
JS - URL ALLOW LIST - Placeholder fixes
diff --git a/articles/javascript/core/configure-local-development-environment.md b/articles/javascript/core/configure-local-development-environment.md
@@ -1,14 +1,14 @@
 ---
 title: Configure your local JavaScript environment for Azure development
 description: How to set up a local JavaScript dev environment for working with Azure, including an editor, the Azure SDK libraries, optional tools, and the necessary credentials for library authentication.
-ms.date: 01/07/2025
+ms.date: 03/07/2025
 ms.topic: how-to
 ms.custom: devx-track-js, azure-sdk-javascript-ai-text-analytics-5.0.0
 ---
 
 # Configure your JavaScript develop environment for Azure
 
-When creating cloud applications, developers typically prefer to test code on their local workstations before deploying that code to a cloud environment like Azure. Local development gives you the advantage of a wider variety of tools along with a familiar environment.
+When you create cloud applications, developers typically prefer to test code on their local workstations before deploying that code to a cloud environment like Azure. Local development gives you the advantage of a wider variety of tools along with a familiar environment.
 
 This article provides setup instructions to create and validate a local development environment that's suitable for JavaScript with Azure.
 
@@ -38,24 +38,25 @@ This article provides setup instructions to create and validate a local developm
     :::column-end:::
     :::column span="2":::
         If you already have a subscription, access your existing subscription with:
-* [Azure portal](https://portal.azure.com)
-* [Azure CLI](/cli/azure/install-azure-cli)
-* [Azure client libraries for JavaScript](../azure-sdk-library-package-index.md)
-* [Visual Studio Code extensions](https://marketplace.visualstudio.com/search?term=azure&target=VSCode&category=Azure&sortBy=Relevance)
+
+        * [Azure portal](https://portal.azure.com)
+        * [Azure CLI](/cli/azure/install-azure-cli)
+        * [Azure client libraries for JavaScript](../azure-sdk-library-package-index.md)
+        * [Visual Studio Code extensions](https://marketplace.visualstudio.com/search?term=azure&target=VSCode&category=Azure&sortBy=Relevance)
     :::column-end:::
 :::row-end:::
 :::row:::
     :::column span="1":::
         Across multiple subscriptions
     :::column-end:::
-    :::column span="2" :::
+    :::column span="2":::
         If you need to manage multiple subscriptions, [learn how](/azure/governance/management-groups/create-management-group-javascript) to create a management group with JavaScript.
     :::column-end:::
 :::row-end:::
 
 ## One-time software installation
 
-Azure development with JavaScript on your local workstation, we suggest you install the following:
+Azure development with JavaScript on your local workstation, we suggest you install the following tools:
 
 |Name/Installer|Description|
 |--|--|
@@ -136,7 +137,7 @@ set AZURE_CLIENT_SECRET="<REPLACE-WITH-YOUR-AZURE-CLIENT-SECRET>"
 
 ---
 
-Replace the values shown in these commands with those of your specific environment variable.
+Replace the values in `<>` brackets in these commands with those of your specific environment variable.
 
 ### Create `.env` file 
 
@@ -158,9 +159,9 @@ For every project, we recommend that you always create a separate folder, and it
     npm init -y
     ```
 
-    This creates the package.json file and initializes the minimum properties.
+    This command creates the package.json file and initializes the minimum properties.
 
-1. Install the Azure cl libraries you need, such as this example:
+1. Install the Azure client libraries you need, such as this authentication client library example:
 
     ```console
     npm install @azure/identity
@@ -180,10 +181,10 @@ We recommend that you get into the habit of creating a source control repository
 
 1. Create a new repository on [GitHub](https://github.com/new) and copy the repository URL for the next few step. 
 
-1. In the Visual Studio integrated terminal, use the following [git](https://git-scm.com/docs) command to add your remote repository to your local repository. Replace `YOUR-ALIAS` and `YOUR-REPOSITORY` with your own values.
+1. In the Visual Studio integrated terminal, use the following [git](https://git-scm.com/docs) command to add your remote repository to your local repository. Replace `<YOUR-ACCOUNT>` and `<REPOSITORY>` with your own values.
 
     ```bash
-    git remote add origin https://github.com/YOUR-ALIAS/YOUR-REPOSITORY
+    git remote add origin https://github.com/<YOUR-ACCOUNT>/<REPOSITORY>
     ```
 
 Visual Studio Code includes many built-in git features. For more information, see [Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol).
diff --git a/articles/javascript/how-to/with-visual-studio-code/clone-github-repository.md b/articles/javascript/how-to/with-visual-studio-code/clone-github-repository.md
@@ -42,13 +42,13 @@ This action isn't available from this feature. Select a different tab.
 1. Clone your repo with the following git command:
 
     ```bash
-    git clone https://github.com/YOUR-NAME-OR-ORGANIZATION/YOUR-REPO-NAME
+    git clone https://github.com/<ACCOUNT>/<REPOSITORY>
     ```
 
 1. Open in Visual Studio Code:
 
     ```bash
-    code YOUR-REPO-NAME
+    code <REPOSITORY>
     ```
 
 ---
@@ -57,7 +57,7 @@ Visual Studio Code uses Git authentication provided by the operating system (suc
 
 ## Open your local repository
 
-If you have an existing repository on your local computer and want to open it in Visual Studio Code, just open the folder. Visual Studio Code recognizes the `.git` subfolder and display the relevant information. 
+If you have an existing repository on your local computer and want to open it in Visual Studio Code, just open the folder. Visual Studio Code recognizes the `.git` subfolder and displays the relevant information. 
 
 ### [Activity bar](#tab/activity-bar)
 
@@ -170,7 +170,7 @@ Create a new branch to capture changes and isolate from the main or default bran
 
 ## Commit changes locally
 
-Once you have made changes on your branch, commit the changes.
+Once you make changes to files on your branch, commit the changes.
 
 ### [Activity bar](#tab/activity-bar)
 
@@ -220,7 +220,7 @@ This action isn't available from this feature. Select a different tab.
 
 1. Open the command palette with the key combination of <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>. 
 1. In the command palette, filter with `Git` then select `Push`.
-1. If you have multiple upstream remotes, select the remote then press <kbd>Enter</kbd>.
+1. If you have multiple upstream remotes, select a remote name then press <kbd>Enter</kbd>.
 
 
 ### [Integrated terminal](#tab/integrated-terminal)
@@ -236,7 +236,7 @@ This action isn't available from this feature. Select a different tab.
 
 ## View Git output
 
-You can view the Git commands run when you use the Source control extension. This helps debug when a command fails.
+You can view the Git commands output when you use the Source control extension. This helps debug when a command fails.
 
 1. Select the Source Control icon from the activity bar.
 1. Select the ellipsis (...) then select **Show Git Output**.
diff --git a/articles/javascript/tutorial/browser-file-upload-azure-storage-blob.md b/articles/javascript/tutorial/browser-file-upload-azure-storage-blob.md
@@ -13,7 +13,7 @@ ms.custom: scenarios:getting-started, languages:JavaScript, devx-track-js, azure
 Use a static web app to upload files directly to an Azure Storage blob using the @azure/storage-blob package. The API generates a SAS token following the [Valet Key pattern](/azure/architecture/patterns/valet-key), which lets you securely delegate limited access without exposing full credentials.
 
 > [!CAUTION]
-> This tutorial shows you how to host your function app in a Consumption Plan. When you plan to secure your connections by using Microsoft Entra ID with managed identities, you should instead consider hosting your app in the [Flex Consumption plan](/azure/azure-functions/flex-consumption-plan). The Flex Consumption plan has been designed to optimize security by supporting the use of managed identities without any of the tradeoffs required when running in a Consumption or Premium plan. Flex Consumption also fully supports virtual network integration.  
+> This tutorial shows you how to host your function app in a Consumption Plan. When you plan to secure your connections by using Microsoft Entra ID with managed identities, you should instead consider hosting your app in the [Flex Consumption plan](/azure/azure-functions/flex-consumption-plan). The **Flex Consumption** tier optimizes security by supporting the use of managed identities and virtual network integration.  
 
 ## Prerequisites
 
@@ -126,10 +126,10 @@ The [Dev Containers extension](https://marketplace.visualstudio.com/items?itemNa
     >
     > :::image type="content" source="media/browser-file-upload-azure-storage-blob/open-terminal-option.png" lightbox="media/browser-file-upload-azure-storage-blob/open-terminal-option.png" alt-text="Screenshot of the menu option to open a new terminal.":::
 
-1. Clone your fork into the current directory. Replace `YOUR-ACCOUNT` in the following command with your account name.
+1. Clone your fork into the current directory. Replace `<YOUR-ACCOUNT>` in the following command with your account name.
 
     ```bash
-    git clone https://github.com/YOUR-ACCOUNT/azure-typescript-e2e-apps
+    git clone https://github.com/<YOUR-ACCOUNT>/azure-typescript-e2e-apps
     ```
 
 1. Open the **Command Palette**, search for the **Dev Containers** commands, and then select **Dev Containers: Reopen in Container**.
@@ -188,9 +188,9 @@ The sample app for this tutorial is in the `azure-upload-file-to-storage` folder
 
 <a name="3-create-storage-resource-with-visual-studio-extension"></a>
 
-## Create Storage resource with Visual Studio extension
+## Create storage resource with Visual Studio extension
 
-Create the Storage resource to use with the sample app. Storage is used for:
+Create the Azure Storage resource to use with the sample app. Storage is used for:
 
 * Triggers in the Azure Functions app
 * Blob (file) storage
@@ -206,7 +206,7 @@ Create the Storage resource to use with the sample app. Storage is used for:
 
     |Property|Value|
     |--|--|
-    |Enter a globally unique name for the new web app.| Enter a unique value such as `fileuploadstor`, for your Storage resource name.<br><br> This unique name is **your resource name** used in the next section. Use only characters and numbers, up to 24 in length. You need this **account name** to use later.|
+    |Enter a globally unique name for the new web app.| Enter a unique value such as `fileuploadstor`, for your Storage resource name.<br><br> This unique name is **your resource name** used in the next section. Use a maximum of 24 alphanumeric characters in length. You need this **account name** to use later.|
     |Select a location for new resources.|Use the recommended location.|
 
 1. When the app creation process is complete, a notification appears with information about the new resource. 
@@ -249,9 +249,9 @@ Create a private container which has publicly readable blobs.
 
 ## Grant yourself Blob Data access
 
-While you created the resource, you don't have permission to view the contents of the container. That is reserved for specific IAM roles. Add your account so you can view the blobs in the containers.
+While you created the resource, you don't have permission to view the contents of the container. This authorization is reserved for specific IAM roles. Add your account so you can view the blobs in the containers.
 
-1. Still in the Azure portal storage account, select **Access Control (IAM)**.
+1. In the Azure portal storage account, select **Access Control (IAM)**.
 1. Select **Add role assignments**. 
 1. Search and select **Storage Blob Data Contributor**. Select **Next**. 
 1. Select **+ Select members**. 
@@ -265,7 +265,7 @@ The Storage resource credentials are used in the Azure Functions API app to conn
 
 1. While still in the Azure portal, in the **Security + networking** section, select **Access keys**.
 1. Copy the `Key ` key. 
-1. In Visual Studio Code, in the `./workspaces/azure-typescript-e2e-apps/azure-upload-file-to-storage/api`folder, **rename** the file from `local.settings.json.sample` to `local.settings.json`. The file is ignored by Git so it won't be checked into source control.
+1. In Visual Studio Code, in the `./workspaces/azure-typescript-e2e-apps/azure-upload-file-to-storage/api`folder, **rename** the file from `local.settings.json.sample` to `local.settings.json`. The file is ignored by Git so it isn't be checked into source control.
 1. Update the settings for `local.settings.json` using the following table.
 
     |Property|Value|Description|
@@ -274,7 +274,7 @@ The Storage resource credentials are used in the Azure Functions API app to conn
     |Azure_Storage_AccountKey|Azure Storage account key|Used in source code to connect to Storage resource.|
     |AzureWebJobsStorage|Azure Storage account connection string|Use by Azure Functions runtime to store state and logs.|
 
-It may seem like you entered the same account credentials twice, once as a key and once as a connection string. You did, but specifically for this simple tutorial. Generally speaking, Azure Functions apps should have a separate Storage resource that isn't reused for another purpose. When you create the Azure Function resource later in the tutorial, you won't need to set the **AzureWebJobsStorage** value for the cloud resource. You'll only need to set the **Azure_Storage_AccountName** and **Azure_Storage_AccountKey** values which are used in source code.
+It may seem like you entered the same account credentials twice, once as a key and once as a connection string. You did, but specifically for this simple tutorial. Generally speaking, Azure Functions apps should have a separate Storage resource that isn't reused for another purpose. When you create the Azure Function resource later in the tutorial, you won't need to set the **AzureWebJobsStorage** value for the cloud resource. You'll need to set the **Azure_Storage_AccountName** and **Azure_Storage_AccountKey** values which are used in source code.
 
 ## Run the API app
 
@@ -312,7 +312,7 @@ Run the Functions App to make sure it works correctly before deploying it to Azu
         "url":"https://YOUR-STORAGE-RESOURCE.blob.core.windows.net/upload/test.png?sv=2023-01-03&spr=https&st=2023-07-26T22%3A15%3A59Z&se=2023-07-26T22%3A25%3A59Z&sr=b&sp=w&sig=j3Yc..."
     }
     ```
-1. Copy the base of the API URL in the browser address bar (not the SAS token URL in the JSON object) to use in the next step. The base URL is everything before `/api/sas`. You will paste this into the client app environment variable file in the next section.
+1. Copy the base of the API URL in the browser address bar (not the SAS token URL in the JSON object) to use in the next step. The base URL is everything before `/api/sas`. You'll paste this base URL into the client app environment variable file in the next section.
 
 ## Configure and run the client app
 
@@ -339,7 +339,7 @@ Run the Functions App to make sure it works correctly before deploying it to Azu
 
 1. Select the **Ports** tab in the bottom pane then right-click the **5173** port and select the globe icon.
 
-1. You should see the simple web app.
+1. You should see the web app.
 
     :::image type="content" source="media/browser-file-upload-azure-storage-blob/browser-app-select-file.png" alt-text="Screenshot of web browser showing web app with Select File button available.":::
 
@@ -360,7 +360,7 @@ Run the Functions App to make sure it works correctly before deploying it to Azu
 
 ## Deploy static web app to Azure 
 
-The Azure Functions app is using a preview feature, it must be deployed to **West US 2** to function properly.
+The Azure Functions app is using a preview feature. It must be deployed to **West US 2** to function properly.
 
 1. In Visual Studio Code, select the Azure explorer.
 
@@ -383,7 +383,7 @@ The Azure Functions app is using a preview feature, it must be deployed to **Wes
     |*Choose build preset to configure default project structure.*|Select **Custom**.|
     |*Select the location of your application code*|`azure-upload-file-to-storage/app`|
     |*Select the location of your Azure Functions code*|`azure-upload-file-to-storage/api`|
-    |*Enter the path of your build output...*|`dist`<br><br>This is the path from your app to your static (generated) files.|
+    |*Enter the path of your build output...*|`dist`<br><br> value is the path from your app to your static (generated) files.|
     |*Select a location for new resources.*|Select a region close to you.|
 
 1. When the process is complete, a notification pop-up displays. Select **View/Edit Workflow**.
@@ -406,7 +406,7 @@ The Azure Functions app is using a preview feature, it must be deployed to **Wes
     ###### End of Repository/Build Configurations ######
     ```
 
-1. Go to your GitHub fork of the sample, `https://github.com/YOUR-ACCOUNT/azure-typescript-e2e-apps/actions` to verify the build and deploy action, named `Azure Static Web Apps CI/CD`, completed successfully. This may take a few minutes to complete.
+1. Go to your GitHub fork of the sample, `https://github.com/<YOUR-ACCOUNT>/azure-typescript-e2e-apps/actions` to verify the build and deploy action, named `Azure Static Web Apps CI/CD`, completed successfully. This action may take a few minutes to complete.
 
 1. Go to your Azure portal for your app and view the **APIs** section of **Settings**. The **Backend Resource Name** in the production environment is `(managed)` indicating your APIs are successfully deployed. 
 1. Select **(managed)** to see the list of APIs loaded in the app:
@@ -446,13 +446,13 @@ Verify the deploy and configuration succeeded by using the web site.
 
 ## Clean up resources
 
-In Visual Studio Code, use the Azure explorer for Resource Groups, right-click on your resource group then select **Delete**.
+In Visual Studio Code, use the Azure explorer for Resource Groups. Right-click on your resource group then select **Delete**.
 
-This deletes all resources in the group, including your Storage and Static Web app resources.
+This action deletes all resources in the group, including your Storage and Static Web app resources.
 
 ## Troubleshooting
 
-Report [issues](https://github.com/Azure-Samples/azure-typescript-e2e-apps/issues) with this sample in the GitHub repo noted below. Include the following with the issue:
+Report [issues](https://github.com/Azure-Samples/azure-typescript-e2e-apps/issues) with this sample in the GitHub repo. Include the following with the issue:
 
 * The URL of the article
 * The step or context within the article that was problematic
