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

Author: gitName

articles/active-directory-b2c/best-practices.md

@@ -84,7 +84,7 @@ Manage your Azure AD B2C environment.
 | Use the Microsoft Graph API to automate the management of your B2C tenants | Microsoft Graph APIs:<br/>Manage [Identity Experience Framework](/graph/api/resources/trustframeworkpolicy?preserve-view=true&view=graph-rest-beta) (custom policies)<br/>[Keys](/graph/api/resources/trustframeworkkeyset?preserve-view=true&view=graph-rest-beta)<br/>[User Flows](/graph/api/resources/identityuserflow?preserve-view=true&view=graph-rest-beta) |
 | Integrate with Azure DevOps | A [CI/CD pipeline](deploy-custom-policies-devops.md) makes moving code between different environments easy and ensures production readiness always.   |
 | Deploy custom policy | Azure AD B2C relies on caching to deliver performance to your end users. When you deploy a custom policy using whatever method, expect a delay of up to **30 minutes** for your users to see the changes. As a result of this behavior, consider the following practices when you deploy your custom policies: <br> - If you're deploying to a development environment, set the `DeploymentMode` attribute in your custom policy file's `<TrustFrameworkPolicy>` element to `Production`. <br> - Deploy your updated policy files to a production environment when traffic in your app is low. <br> - When you deploy to a production environment to update existing policy files, upload the updated files with new names, which act as new versions of the policies. Then, update your app references to the new names/versions. You can remove the old policy files afterward or keep them as your last known good configuration for easy rollback.<br> - If you need to deploy to a production environment to update existing policy files without versioning, make the new policy backward compatible with the old policy by following some simple rules. If you need to change a technical profile, claim, or [SubJourney](subjourneys.md), create a new version of it, publish the policy, and wait for 30 minutes for Azure AD B2C caches to pick up the new version. Then, in a subsequent update, make changes to use the new version and perform another policy update. Wait for another 30 minutes, then you can delete the old version of the elements if needed. Ensure all of your business logic is inside SubJourneys.<br> - You can set the `DeploymentMode` to `Development` in a production environment to bypass the caching behavior. However, we don't recommend this practice. If you [Collect Azure AD B2C logs with Application Insights](troubleshoot-with-application-insights.md), all claims sent to and from identity providers are collected, which is a security and performance risk. |
-| Deploy app registration updates | When you modify your application registration in your Azure AD B2C tenant, such as updating the application's redirect URI, expect a delay of up to **2 hours (3600s)** for the changes to take effect in the production environment. We recommend that you modify your application registration in your production environment when traffic in your app is low.|
+| Deploy app registration updates | When you modify your application registration in your Azure AD B2C tenant, such as updating the application's redirect URI, expect a delay of up to **2 hours (7200s)** for the changes to take effect in the production environment. We recommend that you modify your application registration in your production environment when traffic in your app is low.|
 | Integrate with Azure Monitor | [Audit log events](view-audit-logs.md) are only retained for seven days. [Integrate with Azure Monitor](azure-monitor.md) to retain the logs for long-term use, or integrate with third-party security information and event management (SIEM) tools to gain insights into your environment. |
 | Setup active alerting and monitoring | [Track user behavior](./analytics-with-application-insights.md) in Azure AD B2C using Application Insights. |
 

articles/api-management/api-management-get-started-publish-versions.md

@@ -9,7 +9,7 @@ ms.topic: tutorial
 ms.date: 03/26/2025
 ms.author: danlep
 
-#customer intent: As a developer, I want to publish mutliple versions of an API so that all callers to the API don't need to use the same version.
+#customer intent: As a developer, I want to publish multiple versions of an API so that all callers to the API don't need to use the same version.
 ---
 
 # Tutorial: Publish multiple versions of your API

articles/api-management/api-management-region-availability.md

@@ -37,6 +37,7 @@ Information in the following table is updated regularly. Capacity availability i
 | East US 2 | ✅ | ✅ | ✅ | ✅ |
 | France Central  | ✅ | ✅ | | ✅ |
 | Germany West Central  | ✅ | ✅ | ✅ | ✅ |
+| Italy North | ✅ | ✅ |  |  |
 | Japan East | ✅ | ✅ | | ✅ |
 | Korea Central | ✅ | ✅ | ✅ | | 
 | North Central US | ✅ | ✅ |  | ✅ |
@@ -45,7 +46,8 @@ Information in the following table is updated regularly. Capacity availability i
 | South Africa North | ✅ | ✅ | |  |
 | South Central US | ✅ | ✅ |  |  |
 | South India | ✅ | ✅ |  |  |
-| Southeast Asia | ✅ | ✅ | | ✅ |
+| Sweden Central | ✅ | ✅ | | |
+| South India | ✅ | ✅ |  |  |
 | Switzerland North | ✅ |✅ |  | |
 | UK South | ✅  | ✅ | ✅ | ✅ |
 | UK West | ✅  | ✅ | | |

articles/api-management/mock-api-responses.md

@@ -60,7 +60,7 @@ The steps in this section show how to create an HTTP API with no backend.
 1. In the **Create an HTTP API** window, select **Full**.
 1. In **Display name**, enter *Test API*.
 1. In **Products**, select *Unlimited*, if that value is available. This value is available only in some tiers. You can leave the value blank for this tutorial, but you need to associate the API with a product to publish it. For more information, see [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api). 
-1. In **Gateways**, select **Managed** if this option is available. (This option is avaiable only in certain service tiers.)
+1. In **Gateways**, select **Managed** if this option is available. (This option is available only in certain service tiers.)
 1. Select **Create**.
 
     :::image type="content" source="media/mock-api-responses/create-http-api.png" alt-text="Screenshot that shows the Create an HTTP API window." lightbox="media/mock-api-responses/create-http-api.png":::

articles/app-service/configure-language-dotnet-framework.md

@@ -5,19 +5,20 @@ description: Learn how to configure an ASP.NET app in Azure App Service. This ar
 ms.devlang: csharp
 ms.custom: devx-track-csharp, devx-track-azurecli, devx-track-dotnet
 ms.topic: article
-ms.date: 06/02/2020
+ms.date: 07/07/2025
 author: cephalin
 ms.author: cephalin
+#customer intent: As an ASP.NET developer, I want to configure an ASP.NET app using Azure App Service to take advantage the Azure features.
 ---
 
 # Configure an ASP.NET app for Azure App Service
 
 > [!NOTE]
 > For ASP.NET Core, see [Configure an ASP.NET Core app for Azure App Service](configure-language-dotnetcore.md). If your ASP.NET app runs in a custom Windows or Linux container, see [Configure a custom container for Azure App Service](configure-custom-container.md).
 
-ASP.NET apps must be deployed to Azure App Service as compiled binaries. The Visual Studio publishing tool builds the solution and then deploys the compiled binaries directly, whereas the App Service deployment engine deploys the code repository first and then compiles the binaries.
+ASP.NET apps must be deployed to Azure App Service as compiled binaries. The Visual Studio publishing tool builds the solution and then deploys the compiled binaries directly. The App Service deployment engine deploys the code repository first and then compiles the binaries.
 
-This guide provides key concepts and instructions for ASP.NET developers. If you've never used Azure App Service, follow the [ASP.NET quickstart](./quickstart-dotnetcore.md?tabs=netframework48) and [ASP.NET with SQL Database tutorial](app-service-web-tutorial-dotnet-sqldatabase.md) first.
+This guide provides key concepts and instructions for ASP.NET developers. If this article is your first experience with Azure App Service, follow [Deploy an ASP.NET web app](./quickstart-dotnetcore.md?tabs=netframework48) and [Deploy an ASP.NET app with Azure SQL database to Azure](app-service-web-tutorial-dotnet-sqldatabase.md) first.
 
 ## Show supported .NET Framework runtime versions
 
@@ -29,7 +30,7 @@ For CLR 4 runtime versions (.NET Framework 4 and above):
 ls "D:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework"
 ```
 
-Latest .NET Framework version may not be immediately available.
+Latest .NET Framework version might not be immediately available.
 
 For CLR 2 runtime versions (.NET Framework 3.5 and below):
 
@@ -73,31 +74,31 @@ ConfigurationManager.ConnectionStrings["MyConnection"];
 }
 ```
 
-If you configure an app setting with the same name in App Service and in *web.config*, the App Service value takes precedence over the *web.config* value. The local *web.config* value lets you debug the app locally, but the App Service value lets your run the app in product with production settings. Connection strings work in the same way. This way, you can keep your application secrets outside of your code repository and access the appropriate values without changing your code.
+If you configure an app setting with the same name in App Service and in *web.config*, the App Service value takes precedence over the *web.config* value. The local *web.config* value lets you debug the app locally. The App Service value lets your run the app in product with production settings. Connection strings work in the same way. This way, you can keep your application secrets outside of your code repository and access the appropriate values without changing your code.
 
 > [!NOTE]
 > Consider more secure connectivity options that don't require connection secrets at all. For more information, see [Secure connectivity to Azure services and databases from Azure App Service](tutorial-connect-overview.md).
 
 
 ## Deploy multi-project solutions
 
-When a Visual Studio solution includes multiple projects, the Visual Studio publish process already includes selecting the project to deploy. When you deploy to the App Service deployment engine, such as with Git, or with ZIP deploy [with build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy), the App Service deployment engine picks the first Web Site or Web Application Project it finds as the App Service app. You can specify which project App Service should use by specifying the `PROJECT` app setting. For example, run the following in the [Cloud Shell](https://shell.azure.com):
+When a Visual Studio solution includes multiple projects, the Visual Studio publish process includes selecting the project to deploy. When you deploy to the App Service deployment engine, such as with Git, or with ZIP deploy [with build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy), the App Service deployment engine picks the first Web Site or Web Application Project it finds as the App Service app. You can specify which project App Service should use by specifying the `PROJECT` app setting. For example, run the following command in the [Cloud Shell](https://shell.azure.com):
 
 ```azurecli-interactive
 az webapp config appsettings set --resource-group <resource-group-name> --name <app-name> --settings PROJECT="<project-name>/<project-name>.csproj"
 ```
 
 ## Get detailed exceptions page
 
-When your ASP.NET app generates an exception in the Visual Studio debugger, the browser displays a detailed exception page, but in App Service that page is replaced by a generic error message. To display the detailed exception page in App Service, open the *Web.config* file and add the `<customErrors mode="Off"/>` element under the `<system.web>` element. For example:
+When your ASP.NET app generates an exception in the Visual Studio debugger, the browser displays a detailed exception page. A generic error message replaces that page in App Service. To display the detailed exception page in App Service, open the *web.config* file and add the `<customErrors mode="Off"/>` element under the `<system.web>` element. For example:
 
 ```xml
 <system.web>
     <customErrors mode="Off"/>
 </system.web>
 ```
 
-Redeploy your app with the updated *Web.config*. You should now see the same detailed exception page.
+Redeploy your app with the updated *web.config*. You should now see the same detailed exception page.
 
 ## Access diagnostic logs
 

articles/azure-maps/how-to-dataset-geojson.md

@@ -86,7 +86,7 @@ One thing to consider when adding to an existing dataset is how the feature IDs
 
 If your original dataset was created from a GoeJSON source and you wish to add another facility created from a drawing package, you can append it to your existing dataset by referencing its `conversionId`, as demonstrated by this HTTP POST request:
 
-```shttp
+```https
 https://us.atlas.microsoft.com/datasets?api-version=2023-03-01-preview&conversionId={conversionId}&outputOntology=facility-2.0&datasetId={datasetId}
 ```
 

articles/azure-maps/zoom-levels-and-tile-grid.md

@@ -430,7 +430,7 @@ namespace AzureMaps
             var tl = GlobalPixelToPosition(new double[] { left, top }, zoom, tileSize);
             var br = GlobalPixelToPosition(new double[] { right, bottom }, zoom, tileSize);
 
-            //Boudning box in the format: [west, south, east, north];
+            //Bounding box in the format: [west, south, east, north];
             var bounds = new double[] { tl[0], br[1], br[0], tl[1] };
 
             return GetQuadkeysInBoundingBox(bounds, zoom, tileSize);
@@ -838,7 +838,7 @@ module AzureMaps {
             var tl = this.GlobalPixelToPosition([left, top], zoom, tileSize);
             var br = this.GlobalPixelToPosition([right, bottom], zoom, tileSize);
 
-            //Boudning box in the format: [west, south, east, north];
+            //Bounding box in the format: [west, south, east, north];
             var bounds = [tl[0], br[1], br[0], tl[1]];
 
             return this.GetQuadkeysInBoundingBox(bounds, zoom, tileSize);

articles/azure-resource-manager/bicep/data-types.md

@@ -2,7 +2,7 @@
 title: Data types in Bicep
 description: This article describes the data types that are available in Bicep.
 ms.topic: reference
-ms.date: 05/20/2025
+ms.date: 06/30/2025
 ms.custom: devx-track-bicep
 ---
 
@@ -66,7 +66,7 @@ var index = 1
 output secondElement int = exampleArray[index] // 2
 ```
 
-Starting with [Bicep CLI version 0.34.x](https://github.com/Azure/bicep/releases/tag/v0.34.1), you can use the `array[^index]` syntax to access elements from the end of an array — `^1` refers to the last element, `^2` to the second-to-last, and so on.
+Starting with [Bicep CLI version 0.34.x](https://github.com/Azure/bicep/releases/tag/v0.34.1), you can use the `array[^index]` syntax to access elements from the end of an array - `^1` refers to the last element, `^2` to the second-to-last, and so on.
 
 ```bicep
 var exampleArray = [1, 2, 3]
@@ -325,7 +325,7 @@ var storageName = 'storage${uniqueString(resourceGroup().id)}'
 In Bicep, multi-line strings are defined between three single quotation marks (`'''`) followed optionally by a newline (the opening sequence) and three single quotation marks (`'''` is the closing sequence). Characters that are entered between the opening and closing sequence are read verbatim. Escaping isn't necessary or possible.
 
 > [!NOTE]
-> The Bicep parser reads every characters as it is. Depending on the line endings of your Bicep file, newlines are interpreted as either `\r\n` or `\n`.
+> The Bicep parser reads every character as it is. Depending on the line endings of your Bicep file, newlines are interpreted as either `\r\n` or `\n`.
 >
 > Interpolation isn't currently supported in multi-line strings. Because of this limitation, you might need to use the [`concat`](./bicep-functions-string.md#concat) function instead of using [interpolation](#strings).
 >

articles/azure-resource-manager/bicep/toc.yml

@@ -278,7 +278,7 @@ items:
   - name: Import (import)
     href: bicep-import.md
   - name: User-defined data types (type)
-    displayName: custom
+    displayName: custom,resourceInput,resourceOutput,resource-derived types
     href: user-defined-data-types.md
   - name: User-defined functions (func)
     displayName: custom

articles/azure-resource-manager/bicep/user-defined-data-types.md

@@ -3,7 +3,7 @@ title: User-defined types in Bicep
 description: This article describes how to define and use user-defined data types in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 04/28/2025
+ms.date: 07/01/2025
 ---
 
 # User-defined data types in Bicep
@@ -412,6 +412,67 @@ output config object = serviceConfig
 
 For more information, see [Custom tagged union data type](./data-types.md#custom-tagged-union-data-type).
 
+## Resource-derived types
+
+Bicep allows you to derive types directly from Azure resource schemas using the `resourceInput<>` and `resourceOutput<>` constructs. Resource-derived types allow you to check parameters and variables against a portion of a resource body instead of with a custom type. [Bicep CLI version 0.34.1](https://github.com/Azure/bicep/releases/tag/v0.34.1) or higher is required to use these constructs.
+
+Templates can reuse resource types wherever a type is expected.
+
+```bicep
+resourceInput<'type@version'>
+```
+
+`resourceInput<>`: Represents the writable properties of a resource type, stripping away any properties marked as ReadOnly in the ARM template schema. It uses the type that you would need to pass in to the resource declaration.
+
+```bicep
+resourceOutput<'type@version'>
+```
+
+`resourceOutput<>`: Represents the readable properties of a resource type, stripping away any properties marked as WriteOnly in the ARM template schema. It matches the type of value returned after the resource is provisioned.
+
+You can apply `resourceInput<>` or `resourceOutput<>` to extract only a part of a resource schema. For example, to type a variable or parameter based on just the `kind` or `properties` of a storage account:
+
+```bicep
+type accountKind = resourceInput<'Microsoft.Storage/storageAccounts@2024-01-01'>.kind
+```
+
+The preceding example is equivalent to:
+
+```bicep
+type accountKind = 'BlobStorage' | 'BlockBlobStorage' | 'FileStorage' | 'Storage' | 'StorageV2'
+```
+
+The following example shows how to use `resourceInput<>` to create a typed parameter based on the `properties` of a storage account resource. This allows you to define a parameter that matches the writable properties of a storage account, such as `accessTier`, `minimumTlsVersion`, and others:
+
+```bicep
+// Typed parameter using the .properties path of a storage account
+param storageAccountProps resourceInput<'Microsoft.Storage/storageAccounts@2023-01-01'>.properties = {
+  accessTier: 'Hot'
+  minimumTlsVersion: 'TLS1_2'
+  allowBlobPublicAccess: false
+  supportsHttpsTrafficOnly: true
+}
+
+// Resource declaration using the typed parameter
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
+  name: 'mystorageacct123'
+  location: resourceGroup().location
+  sku: {
+    name: 'Standard_LRS'
+  }
+  kind: 'StorageV2'
+  properties: storageAccountProps
+}
+```
+
+The following example shows how to use `resourceOutput<>` to create a typed output based on the `primaryEndPoints` of a storage account resource.
+
+```bicep
+output storageEndpoints resourceOutput<'Microsoft.Storage/storageAccounts@2024-01-01'>.properties.primaryEndpoints = ...
+```
+
+Unlike user-defined data types, resource-derived types are checked by Bicep when editing or compiling a file, but they aren't checked by the ARM service.
+
 ## Related content
 
 For a list of the Bicep data types, see [Data types](./data-types.md).