Merge branch 'MicrosoftDocs:main' into main

Author: dekadays

.openpublishing.redirection.json

@@ -6978,6 +6978,26 @@
       "source_path": "articles/defender-for-iot/organizations/eiot-sensor.md",
       "redirect_url": "/azure/defender-for-iot/organizations/concept-enterprise",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cyclecloud/release-notes/ccws/2024.09.18.md",
+      "redirect_url": "/azure/cyclecloud/release-notes/ccws/2024-09-18",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cyclecloud/release-notes/ccws/2024.11.08.md",
+      "redirect_url": "/azure/cyclecloud/release-notes/ccws/2024-11-08",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cyclecloud/release-notes/ccws/2024.12.18.md",
+      "redirect_url": "/azure/cyclecloud/release-notes/ccws/2024-12-18",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/cyclecloud/release-notes/ccws/2025.02.06.md",
+      "redirect_url": "/azure/cyclecloud/release-notes/ccws/2025-02-06",
+      "redirect_document_id": false
     }
   ]
 }

articles/api-management/configure-custom-domain.md

@@ -7,7 +7,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 05/09/2025
+ms.date: 05/30/2025
 ms.author: danlep
 ms.custom:
   - engagement-fy23
@@ -50,10 +50,10 @@ There are several API Management endpoints to which you can assign a custom doma
 | Endpoint | Default |
 | -------- | ----------- |
 | **Gateway** | Default is: `<apim-service-name>.azure-api.net`. Gateway is the only endpoint available for configuration in the Consumption tier.<br/><br/>The default Gateway endpoint configuration remains available after a custom Gateway domain is added. |
-| **Developer portal** | Default is: `<apim-service-name>.developer.azure-api.net` |
-| **Management** | Default is: `<apim-service-name>.management.azure-api.net` |
-| **Configuration API (v2)** | Default is: `<apim-service-name>.configuration.azure-api.net` |
-| **SCM** | Default is: `<apim-service-name>.scm.azure-api.net` |
+| **Developer portal** (all tiers except Consumption) | Default is: `<apim-service-name>.developer.azure-api.net` |
+| **Management** (classic tiers only) | Default is: `<apim-service-name>.management.azure-api.net` |
+| **Self-hosted gateway configuration API (v2)** | Default is: `<apim-service-name>.configuration.azure-api.net` |
+| **SCM** (classic tiers only) | Default is: `<apim-service-name>.scm.azure-api.net` |
 
 ### Considerations
 
@@ -62,6 +62,7 @@ There are several API Management endpoints to which you can assign a custom doma
 * Only API Management instance owners can use **Management** and **SCM** endpoints internally. These endpoints are less frequently assigned a custom domain name.
 * The **Premium** and **Developer** tiers support setting multiple hostnames for the **Gateway** endpoint.
 * Wildcard domain names, like `*.contoso.com`, are supported in all tiers except the Consumption tier. A specific subdomain certificate (for example, api.contoso.com) would take precedence over a wildcard certificate (*.contoso.com) for requests to api.contoso.com.
+* When configuing a custom domain for the **Developer portal**, you can [enable CORS](enable-cors-developer-portal.md) for the new domain name. This is needed for developer portal visitors to use the interactive console in the API reference pages.
 
 ## Domain certificate options
 

articles/api-management/enable-cors-developer-portal.md

@@ -6,19 +6,20 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 12/22/2023
+ms.date: 05/30/2025
 ms.author: danlep
 ---
 
 # Enable CORS for interactive console in the API Management developer portal 
+
+[!INCLUDE [premium-dev-standard-basic-premiumv2-standarv2-basicv2.md](../../includes/api-management-availability-premium-dev-standard-basic-premiumv2-standardv2-basicv2.md)]
+
 Cross-origin resource sharing (CORS) is an HTTP-header based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. 
 
 To let visitors to the API Management [developer portal](developer-portal-overview.md) use the interactive test console in the API reference pages, enable a [CORS policy](cors-policy.md) for APIs in your API Management instance. If the developer portal's domain name isn't an allowed origin for cross-domain API requests, test console users will see a CORS error.  
 
 For certain scenarios, you can configure the developer portal as a CORS proxy instead of enabling a CORS policy for APIs.
 
-[!INCLUDE [premium-dev-standard-basic.md](../../includes/api-management-availability-premium-dev-standard-basic.md)]
-
 ## Prerequisites 
 
 + Complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md)
@@ -41,7 +42,6 @@ You can enable a setting to configure a CORS policy automatically for all APIs i
 
 ![Screenshot that shows where to check status of your CORS policy in the developer portal.](media/enable-cors-developer-portal/cors-azure-portal.png)
 
-
 ### Enable CORS policy manually
 
 1. Select the **Manually apply it on the global level** link to see the generated policy code.
@@ -57,6 +57,12 @@ You can enable a setting to configure a CORS policy automatically for all APIs i
 >
 > As a workaround, you can pass the subscription key in a query parameter.
 
+## CORS configuration for custom domain name
+
+If you configure a [custom domain](configure-custom-domain.md) for the developer portal and want visitors to use the test console on API reference pages, ensure that you enable CORS for the custom developer portal domain name.
+
+When configuring the custom domain, you can enable a setting to add an origin for your custom developer portal domain in the CORS policy. If CORS was already enabled for the default domain, both origins will be included in the CORS policy. You can change the CORS policy settings anytime.
+
 ## CORS proxy option
 
 For some scenarios (for example, if the API Management gateway is network isolated), you can choose to configure the developer portal as a CORS proxy itself, instead of enabling a CORS policy for your APIs. The CORS proxy routes the interactive console's API calls through the portal's backend in your API Management instance.
@@ -84,4 +90,4 @@ If you [self-host](developer-portal-self-host.md) the developer portal, the foll
 ## Related content
 
 * For more information about configuring a policy, see [Set or edit policies](set-edit-policies.md).
-* For details about the CORS policy, see the [cors](cors-policy.md) policy reference.
+* For details about the CORS policy, see the [cors](cors-policy.md) policy reference.

articles/app-service/includes/quickstart-python/create-app-cli.md

@@ -26,7 +26,7 @@ az webapp up --runtime PYTHON:3.13 --sku B1 --logs
 * You can optionally specify a name with the argument `--name <app-name>`. If you don't provide one, then a name will be automatically generated.
 * 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 appservice list-locations`](/cli/azure/appservice#az-appservice-list-locations) command.
 
-The command may take a few minutes to complete. While the command is 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.
+The command may take a few minutes to complete. While the command is 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 returns a message that includes the app's URL, which is the app's URL on Azure.
 
 <pre>
 The webapp '&lt;app-name>' doesn't exist
@@ -39,9 +39,9 @@ Creating zip with contents of dir /home/cephas/myExpressApp ...
 Getting scm site credentials for zip deployment
 Starting zip deployment. This operation can take a while to complete ...
 Deployment endpoint responded with status code 202
-You can launch the app at http://&lt;app-name>.azurewebsites.net
+You can launch the app at &lt;URL>
 {
-  "URL": "http://&lt;app-name>.azurewebsites.net",
+  "URL": "&lt;URL>",
   "appserviceplan": "&lt;app-service-plan-name>",
   "location": "centralus",
   "name": "&lt;app-name>",

articles/app-service/includes/quickstart-python/create-app-service-visual-studio-code-4.md

@@ -6,4 +6,4 @@ ms.date: 04/30/2022
 ---
 Enter the name *msdocs-python-webapp-quickstart-XYZ* for this web app, where *XYZ* is any three unique characters.<br>
 <br>
-When deployed, this name is used as your app name in the form `https://<app-name>.azurewebsites.net`.
+When deployed, this name is used as your app name.

articles/app-service/includes/quickstart-python/deploy-zip-curl-commands.md

@@ -4,14 +4,19 @@ ms.author: daberry
 ms.topic: include
 ms.date: 01/29/2022
 ---
+Get the \<URL> from your Kudu Environment: 
+
+1. Open your app in the Azure portal and select **Development Tools** > **Advanced Tools**, then select **Go**.
+1. Copy the value from the address bar and append */api/zipdeploy*.
+
 ##### [bash](#tab/terminal-bash)
 
 ```bash
 curl -X POST \
     -H 'Content-Type: application/zip' \
     -u '<deployment-user>' \
     -T <zip-file-name> \
-    https://<app-name>.scm.azurewebsites.net/api/zipdeploy
+    <URL>
 ```
 
 ##### [PowerShell terminal](#tab/terminal-powershell)
@@ -23,7 +28,7 @@ curl -X POST `
     -H 'Content-Type: application/zip' `
     -u '<deployment-user>' `
     -T <zip-file-name> `
-    https://<app-name>.scm.azurewebsites.net/api/zipdeploy
+    <URL>
 ```
 
 ---

articles/app-service/includes/tutorial-set-up-app-service-authentication/after.md

@@ -156,7 +156,7 @@ When you enabled the App Service authentication/authorization module in the prev
 1. Select the app registration that was created. 
 1. In the overview, verify that **Supported account types** is set to **My organization only**.
 
-1. To verify that access to your app is limited to users in your organization, go to your web app **Overview** and select the **Default domain** link.  Or, start a browser in incognito or private mode and go to `https://<app-name>.azurewebsites.net` (see [note at top](#dnl-note)).
+1. To verify that access to your app is limited to users in your organization, go to your web app **Overview** and select the **Default domain** link.
 
     :::image type="content" alt-text="Screenshot that shows verifying access." source="../../media/scenario-secure-app-authentication-app-service/verify-access.png":::
 

articles/app-service/overview-hosting-plans.md

@@ -14,8 +14,6 @@ ms.custom: UpdateFrequency3
 
 An *Azure App Service plan* defines a set of compute resources for a web app to run. An app service always runs in an App Service plan. [Azure Functions](../azure-functions/dedicated-plan.md) also has the option of running in an App Service plan.
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 When you create an App Service plan in a certain region, you create a set of compute resources for that plan in that region. Whatever apps you put into the App Service plan run on those compute resources, as defined in the plan.
 
 Each App Service plan defines:

articles/app-service/overview-managed-identity.md

@@ -15,11 +15,9 @@ ai-usage: ai-assisted
 
 This article shows you how to create a managed identity for Azure App Service and Azure Functions applications, and how to use it to access other resources.
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 [!INCLUDE [app-service-managed-identities](../../includes/app-service-managed-identities.md)]
 
-The managed identity configuration is specific to the slot. To configure a managed identity for a deployment slot in the portal, go to the slot first. To find the managed identity for your web app or deployment slot in your Microsoft Entra tenant from the Azure portal, search for it directly from the **Overview** page of your tenant. Usually, the slot name is similar to `<app-name>/slots/<slot-name>`.
+The managed identity configuration is specific to the slot. To configure a managed identity for a deployment slot in the portal, go to the slot first. To find the managed identity for your web app or deployment slot in your Microsoft Entra tenant from the Azure portal, search for it directly from the **Overview** page of your tenant.
 
 > [!NOTE]
 > Managed identities aren't available for [apps deployed in Azure Arc](overview-arc-integration.md).

articles/app-service/overview-private-endpoint.md

@@ -14,8 +14,6 @@ ms.assetid: 2dceac28-1ba6-4904-a15d-9e91d5ee162c
 
 # Use private endpoints for Azure App Service apps
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 You can use a private endpoint for your Azure App Service apps. The private endpoint allows clients located in your private network to securely access an app over Azure Private Link. The private endpoint uses an IP address from your Azure virtual network address space. Network traffic between a client on your private network and the app goes over the virtual network and Private Link on the Microsoft backbone network. This configuration eliminates exposure from the public internet.
 
 When you use a private endpoint for your app, you can:
@@ -57,9 +55,7 @@ You can find the client source IP in the web HTTP logs of your app. This feature
 
 ## DNS
 
-When you use private endpoint for App Service apps, the requested URL must match the name of your app, which is by default `<app-name>.azurewebsites.net`. When you use a [unique default hostname](#dnl-note), your app name has the format `<app-name>-<random-hash>.<region>.azurewebsites.net`. In the following examples, `mywebapp` could also represent the full regionalized unique hostname.
-
-By default, without a private endpoint, the public name of your web app is a canonical name to the cluster. For example, the name resolution is:
+When you use private endpoint for App Service apps, the requested URL must match the address of your app. By default, without a private endpoint, the public name of your web app is a canonical name to the cluster. For example, the name resolution is:
 
 | Name | Type | Value |
 |:-----|:-----|:------|