Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into versiont

Author: gitName

.openpublishing.redirection.json

@@ -3751,6 +3751,31 @@
       "redirect_document_id": false
     },
     {
+      "source_path_from_root": "/articles/defender-for-iot/device-builders/quickstart-upload-firmware-using-azure-command-line-interface.md",
+      "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/defender-for-iot/device-builders/quickstart-upload-firmware-using-powershell.md",
+      "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/defender-for-iot/device-builders/tutorial-analyze-firmware.md",
+      "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/defender-for-iot/device-builders/defender-iot-firmware-analysis-faq.md",
+      "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/defender-for-iot/device-builders/defender-iot-firmware-analysis-rbac.md",
+      "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
+      "redirect_document_id": false
+     },
+     {
       "source_path_from_root": "/articles/virtual-network/ip-services/public-ip-upgrade-portal.md",
       "redirect_url": "/azure/virtual-network/ip-services/public-ip-upgrade",
       "redirect_document_id": false
@@ -3764,6 +3789,16 @@
       "source_path_from_root": "/articles/virtual-network/ip-services/public-ip-upgrade-powershell.md",
       "redirect_url": "/azure/virtual-network/ip-services/public-ip-upgrade",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/defender-for-iot/device-builders/quickstart-upload-firmware-using-python.md",
+      "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/defender-for-iot/device-builders/overview-firmware-analysis.md",
+      "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
+      "redirect_document_id": false
     }
   ]
-}
+}

articles/active-directory-b2c/whats-new-docs.md

@@ -1,7 +1,7 @@
 ---
 title: "What's new in Azure Active Directory business-to-customer (B2C)"
 description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
-ms.date: 11/04/2024
+ms.date: 12/02/2024
 ms.service: azure-active-directory
 ms.subservice: b2c
 ms.topic: whats-new
@@ -19,6 +19,12 @@ manager: CelesteDG
 
 Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
 
+## November 2024
+
+### Updated articles
+
+- [Azure Active Directory B2C: Region availability & data residency](data-residency.md) - Updated data residency location 
+
 ## October 2024
 
 ### Updated articles
@@ -35,11 +41,3 @@ Welcome to what's new in Azure Active Directory B2C documentation. This article
 
 - [Developer notes for Azure Active Directory B2C](custom-policy-developer-notes.md) - Updated feature availability for China cloud
 
-## August 2024
-
-This month, we changed Twitter to X in numerous articles and code samples.
-
-### Updated articles
-
-- [Tutorial: Configure Keyless with Azure Active Directory B2C](partner-keyless.md) - Editorial updates
-

articles/analysis-services/analysis-services-addservprinc-admins.md

@@ -95,7 +95,7 @@ The following Resource Manager template deploys an Analysis Services server with
 
 ## Using managed identities
 
-Managed identies that are added to database or server roles will be unable to login to the service or do any operations. Managed identities for service principals are not supported in Azure Analysis Services.
+Managed identities that are added to database or server roles will be unable to login to the service or do any operations. Managed identities for service principals are not supported in Azure Analysis Services.
 
 ## Related information
 

articles/analysis-services/analysis-services-database-users.md

@@ -62,7 +62,7 @@ When adding a **service principal** use `app:appid@tenantid`.
 
 To add roles and users to a deployed model database, you must be connected to the server as a Server administrator or already in a database role with administrator permissions.
 
-1. In Object Exporer, right-click **Roles** > **New Role**.
+1. In Object Explorer, right-click **Roles** > **New Role**.
 
 2. In **Create Role**, enter a role name and description.
 

articles/analysis-services/analysis-services-scale-out.md

@@ -61,7 +61,7 @@ Use SSMS to set ReplicaSyncMode in Advanced Properties. The possible values are:
 - `1` (default): Full replica database rehydration in stages (incremental). 
 - `2`: Optimized synchronization in parallel. 
 
-![RelicaSyncMode setting](media/analysis-services-scale-out/aas-scale-out-sync-mode.png)
+![ReplicaSyncMode setting](media/analysis-services-scale-out/aas-scale-out-sync-mode.png)
 
 When setting **ReplicaSyncMode=2**, depending on how much of the cache needs to be updated, more memory may be consumed by the query replicas. To keep the database online and available for queries, depending on how much of the data has changed, the operation can require up to *double the memory* on the replica because both the old and new segments are kept in memory simultaneously. Replica nodes have the same memory allocation as the primary node, and there's normally extra memory on the primary node for refresh operations, so it may be unlikely that the replicas would run out of memory. Additionally, the common scenario is that the database is incrementally updated on the primary node, and therefore the requirement for double the memory should be uncommon. If the Sync operation does encounter an out of memory error, it retries using the default technique (attach/detach two at a time). 
 

articles/api-center/manage-apis-azure-cli.md

@@ -125,7 +125,7 @@ Use the [az apic api delete](/cli/azure/apic/api#az_apic_api_delete) command to
 
 ```azurecli-interactive
 az apic api delete \
-    --resource-group myResoureGroup --service-name myAPICenter \
+    --resource-group myResourceGroup --service-name myAPICenter \
     --api-id petstore-api
 ```
 

articles/api-management/api-management-get-started-revise-api.md

@@ -7,7 +7,7 @@ author: dlepow
 ms.service: azure-api-management
 ms.custom: mvc, devx-track-azurecli, devdivchpfy22
 ms.topic: tutorial
-ms.date: 07/31/2024
+ms.date: 11/27/2024
 ms.author: danlep
 
 ---
@@ -31,7 +31,7 @@ In this tutorial, you learn how to:
 > * Browse the developer portal to see changes and change log
 > * Access an API revision
 
-:::image type="content" source="media/api-management-getstarted-revise-api/azure-portal.png" alt-text="Screenshot of API revisions in the Azure portal." lightbox="media/api-management-getstarted-revise-api/azure-portal.png":::
+:::image type="content" source="media/api-management-get-started-revise-api/azure-portal.png" alt-text="Screenshot of API revisions in the Azure portal." lightbox="media/api-management-get-started-revise-api/azure-portal.png":::
 
 ## Prerequisites
 
@@ -43,11 +43,11 @@ In this tutorial, you learn how to:
 
 1. Sign in to the [Azure portal](https://portal.azure.com), and go to your API Management instance.
 1. In the left menu, under **APIs**, select **APIs**.
-2. Select **Demo Conference API** from the API list (or another API to which you want to add revisions).
+2. Select **Swagger Petstore** from the API list (or another API to which you want to add revisions).
 3. Select the **Revisions** tab.
 4. Select **+ Add revision**.
 
-   :::image type="content" source="media/api-management-getstarted-revise-api/07-add-revisions-01-add-new-revision.png" alt-text="Screenshot of adding an API revision in the portal.":::
+   :::image type="content" source="media/api-management-get-started-revise-api/07-add-revisions-01-add-new-revision.png" alt-text="Screenshot of adding an API revision in the portal.":::
 
     > [!TIP]
     > You can also select **Add revision** in the context menu (**...**) of the API.
@@ -61,7 +61,7 @@ In this tutorial, you learn how to:
 
 ## Make nonbreaking changes to your revision
 
-1. Select **Demo Conference API** from the API list.
+1. Select **Swagger Petstore** from the API list.
 1. Select the **Design** tab near the top of the screen.
 1. Notice that the **revision selector** (directly above the design tab) shows **Revision 2** as currently selected.
 
@@ -71,7 +71,7 @@ In this tutorial, you learn how to:
 1. Set your new operation to **POST**, and the  **Display name**, **Name**, and **URL** of the operation as **test**.
 1. **Save** your new operation.
 
-   :::image type="content" source="media/api-management-getstarted-revise-api/07-add-revisions-02-make-changes.png" alt-text="Screenshot showing how to add an operation in a revision in the portal.":::
+   :::image type="content" source="media/api-management-get-started-revise-api/07-add-revisions-02-make-changes.png" alt-text="Screenshot showing how to add an operation in a revision in the portal.":::
 1. You've now made a change to **Revision 2**. Use the **revision selector** near the top of the page to switch back to **Revision 1**.
 1. Notice that your new operation doesn't appear in **Revision 1**. 
 
@@ -85,7 +85,7 @@ In this tutorial, you learn how to:
 1. Select the **Post to Public Change log for this API** checkbox, if you want to post notes about this change. Provide a description for your change that the developers can see, for example: **Testing revisions. Added new "test" operation.**
 1. **Revision 2** is now current.
 
-    :::image type="content" source="media/api-management-getstarted-revise-api/revisions-menu.png" alt-text="Screenshot of revision menu in Revisions window in the portal." lightbox="media/api-management-getstarted-revise-api/revisions-menu.png":::
+    :::image type="content" source="media/api-management-get-started-revise-api/revisions-menu.png" alt-text="Screenshot of revision menu in Revisions window in the portal." lightbox="media/api-management-get-started-revise-api/revisions-menu.png":::
 
 ### [Azure CLI](#tab/azure-cli)
 
@@ -95,7 +95,7 @@ To begin using Azure CLI:
 
 Use this procedure to create and update a release.
 
-1. Run the [az apim api list](/cli/azure/apim/api#az-apim-api-list) command to see your API IDs:
+1. Run the [az api list](/cli/azure/apim/api#az-apim-api-list) command to see your API IDs:
 
    ```azurecli
    az apim api list --resource-group apim-hello-word-resource-group \
@@ -108,7 +108,7 @@ Use this procedure to create and update a release.
 
    ```azurecli
    az apim api release create --resource-group apim-hello-word-resource-group \
-       --api-id demo-conference-api --api-revision 2 --service-name apim-hello-world \
+       --api-id swagger-petstore --api-revision 2 --service-name apim-hello-world \
        --notes 'Testing revisions. Added new "test" operation.'
    ```
 
@@ -118,7 +118,7 @@ Use this procedure to create and update a release.
 
    ```azurecli
    az apim api release list --resource-group apim-hello-word-resource-group \
-       --api-id echo-api --service-name apim-hello-world --output table
+       --api-id swagger-petstore --service-name apim-hello-world --output table
    ```
 
    The notes you specify appear in the change log. You can see them in the output of the previous command.
@@ -127,7 +127,7 @@ Use this procedure to create and update a release.
 
    ```azurecli
    az apim api release update --resource-group apim-hello-word-resource-group \
-       --api-id demo-conference-api --release-id 00000000000000000000000000000000 \
+       --api-id swagger-petstore --release-id 00000000000000000000000000000000 \
        --service-name apim-hello-world --notes "Revised notes."
    ```
 
@@ -137,7 +137,7 @@ You can remove any release by running the [az apim api release delete ](/cli/azu
 
 ```azurecli
 az apim api release delete --resource-group apim-hello-word-resource-group \
-    --api-id demo-conference-api --release-id 00000000000000000000000000000000 
+    --api-id swagger-petstore --release-id 00000000000000000000000000000000 
     --service-name apim-hello-world
 ```
 
@@ -150,21 +150,21 @@ If you've tried the [developer portal](api-management-howto-developer-portal-cus
 1. In the Azure portal, navigate to your API Management instance.
 1. In the left menu, under **APIs**, select **APIs**.
 1. Select **Developer portal** from the top menu.
-1. In the developer portal, select **APIs**, and then select **Demo Conference API**.
+1. In the developer portal, select **APIs**, and then select **Swagger Petstore**.
 1. Notice your new **test** operation is now available.
 1. Select **Changelog** near the API name.
 1. Notice that your change log entry appears in the list.
 
 
 ## Access an API revision
 
-Each revision to your API can be accessed using a specially formed URL. Add `;rev={revisionNumber}` at the end of your API URL path, but before the query string, to access a specific revision of that API. For example, you might use this URL to access revision 2 of the Demo Conference API:
+Each revision to your API can be accessed using a specially formed URL. Add `;rev={revisionNumber}` at the end of your API URL path, but before the query string, to access a specific revision of that API. For example, you might use a URL similar to the following to access revision 2 of the Swagger Petstore API:
 
-`https://apim-hello-world.azure-api.net/conf;rev=2/speakers`
+`https://apim-hello-world.azure-api.net/store/pet/1;rev=2/`
 
 You can find the URL paths for your API's revisions on the **Revisions** tab in the Azure portal.
 
-:::image type="content" source="media/transform-api/revision-url-path.png" alt-text="Screenshot of revision URLs in the portal.":::
+:::image type="content" source="media/api-management-get-started-revise-api/revision-url-path.png" alt-text="Screenshot of revision URLs in the portal.":::
 
 > [!TIP]
 > You can access the *current* revision of your API using the API path without the `;rev` string, in addition to the full URL that appends `;rev={revisionNumber}` to your API path.

articles/api-management/api-management-howto-api-inspector.md

@@ -149,7 +149,7 @@ For information about customizing trace information, see the [trace](trace-polic
 In this tutorial, you learned how to:
 
 > [!div class="checklist"]
-> * Trace an example call in the test conosle
+> * Trace an example call in the test console
 > * Review request processing steps
 > * Enable tracing for an API
 

articles/api-management/developer-portal-wordpress-plugin.md

@@ -69,7 +69,7 @@ In this step, create a new Microsoft Entra app. In later steps, you configure th
 
     `https://<apim-instance-name>.developer.azure-api.net/signin`
 
-1. Select **+ Add a platform** again. Select **Single-page application** agaain.
+1. Select **+ Add a platform** again. Select **Single-page application** again.
 1. On the **Configure single-page application** page, enter the following redirect URI, substituting the name of your API Management instance, and select **Configure**:
 
     `https://<apim-instance-name>.developer.azure-api.net/`

articles/api-management/high-availability.md

@@ -35,8 +35,7 @@ Enabling [zone redundancy](../reliability/migrate-api-mgt.md) for an API Managem
 
 When you enable zone redundancy in a region, consider the number of API Management scale [units](upgrade-and-scale.md) that need to be distributed. Minimally, configure the same number of units as the number of availability zones, or a multiple so that the units are distributed evenly across the zones. For example, if you select 3 availability zones in a region, you could have 3 units so that each zone hosts one unit.
 
-> [!NOTE]
-> Use [capacity metrics](api-management-capacity.md) and your own testing to decide the number of scale units that will provide the gateway performance for your needs. Learn more about [scaling and upgrading](upgrade-and-scale.md) your service instance.
+[!INCLUDE [api-management-az-notes](../../includes/api-management-az-notes.md)]
 
 ## Multi-region deployment