Merge pull request #310220 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-07 18:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -6574,6 +6574,11 @@
       "source_path": "articles/oracle/oracle-db/exadata-vm-clusters.md",
       "redirect_url": "/azure/oracle/oracle-db/database-overview",
       "redirect_document_id": false
+    },
+    { 
+      "source_path": "articles/reliability/reliability-health-insights.md",
+      "redirect_url": "/azure/azure-health-insights/reliability-health-insights",
+      "redirect_document_id": false
     }
 
   ]

articles/api-management/inject-vnet-v2.md

@@ -54,7 +54,7 @@ If you want to enable *public* inbound access to an API Management instance in t
 * Minimum: /27 (32 addresses)
 * Recommended: /24 (256 addresses) - to accommodate scaling of API Management instance
 
-### Examples
+#### Examples
 
 The following table shows subnet sizing examples for API Management virtual network injection, illustrating how different CIDR blocks affect the number of scale-out units possible:
 
@@ -64,18 +64,19 @@ The following table shows subnet sizing examples for API Management virtual netw
 | /26         | 64                  | 5                   | 2                            | 1                          | 56                          | 28                   | 29               |
 | /25         | 128                 | 5                   | 2                            | 1                          | 120                         | 30*                  | 30*              |
 
+<sup>*</sup> Premium v2 limit
 
-### Key Points
+#### Key points
 
 - **Minimum subnet size**: /27 (provides 24 usable IP addresses for API Management)
 - **Azure reserved IPs**: 5 addresses per subnet (first and last for protocol conformance, plus 3 for Azure services)
 - **Scale-out requirement**: Each scale-out unit requires 2 IP addresses
 - **Internal load balancer**: Only required when API Management is deployed in internal virtual network mode
-- **Premium V2 limit**: * Currently supports up to 30 units maximum.
+- **Premium V2 limit**: Currently supports up to 30 units maximum.
 
 > [!IMPORTANT]
-> API Management is a member of Azure Integration Services and is typically deployed as a pivotal service in enterprise architectures. It is prudent to err on the higher side of available IPs for the API Management subnet as changing it later can have far-reaching impact.
-> The private IP addresses of internal load balancer and API Management units are assigned dynamically. Therefore, it is impossible to anticipate the private IP of the API Management instance prior to its deployment. Additionally, changing to a different subnet and then returning might cause a change in the private IP address.
+> - API Management is a member of Azure Integration Services and is typically deployed as a pivotal service in enterprise architectures. It is prudent to err on the higher side of available IPs for the API Management subnet as changing it later can have far-reaching impact.
+> - The private IP addresses of internal load balancer and API Management units are assigned dynamically. Therefore, it is impossible to anticipate the private IP of the API Management instance prior to its deployment. Additionally, changing to a different subnet and then returning might cause a change in the private IP address.
 
 ### Network security group
 

articles/application-gateway/application-gateway-diagnostics.md

@@ -7,7 +7,7 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 06/16/2025
+ms.date: 01/05/2026
 ms.author: mbender
 ms.custom:
   - ai-gen-docs-bap
@@ -35,6 +35,47 @@ You can use different types of logs in Azure to manage and troubleshoot applicat
 > [!NOTE]
 > Logs are available only for resources deployed in the Azure Resource Manager deployment model. You can't use logs for resources in the classic deployment model. For a better understanding of the two models, see the [Understanding Resource Manager deployment and classic deployment](../azure-resource-manager/management/deployment-models.md) article.
 
+## Storage locations for diagnostic logs 
+Azure Monitor provides multiple options for storing resource logs depending on your analysis, retention, and integration requirements. When configuring diagnostic settings, you can choose one or more destinations for log collection. 
+
+**Log Analytics workspace (recommended)** 
+A Log Analytics workspace is the recommended destination for collecting and analyzing Application Gateway resource logs. It enables: 
+
+- Use of predefined queries and visualizations 
+- Creation of alerts based on specific log conditions 
+- Integration with Azure Monitor features and insights 
+In Log Analytics, the table used for storing diagnostic logs depends on the collection type configured in the diagnostic setting. 
+
+**Collection types in Log Analytics**
+
+**Azure Diagnostics (legacy):** When you select Azure Diagnostics, all logs are written to the shared AzureDiagnostics table.Because this table is shared across many resource types, each service writes its own custom fields. When the number of custom fields exceeds 500, additional fields are stored under the AdditionalFields dynamic property as key/value pairs. This can lead to reduced discoverability and more complex queries. 
+
+**Resource-specific (recommended):** When you select Resource-specific, logs are written into dedicated tables for each category.
+Resource-specific mode provides: 
+
+- Simplified querying with predictable schemas 
+- Improved discoverability of fields and table structures 
+- Better performance due to lower ingestion latency and faster query execution 
+- Granular RBAC by assigning access at the table level 
+
+For Application Gateway, resource-specific mode creates the following tables: 
+
+- [AGWAccessLogs](/azure/azure-monitor/reference/tables/agwaccesslogs.md)
+- [AGWPerformanceLogs](/azure/azure-monitor/reference/tables/agwperformancelogs.md)
+- [AGWFirewallLogs](/azure/azure-monitor/reference/tables/agwfirewalllogs.md)
+
+**Selecting the collection type in Log analytics**
+
+Azure services are transitioning to resource-specific mode. As part of this migration, a toggle is available in the diagnostic settings to choose either: 
+
+- Resource-specific (default) 
+- Azure Diagnostics 
+
+The toggle determines whether logs for the selected categories are routed to dedicated tables or to the AzureDiagnostics table. When switching to resource-specific mode, only newly selected categories use the dedicated tables; existing streams continue unchanged until reconfigured.  
+
+Selecting resource-specific mode provides enhanced flexibility through workspace transformations, allowing you to preprocess data before ingestion.For guidance on configuring workspace transformations, see: [Tutorial: Add a workspace transformation to Azure Monitor Logs by using the Azure portal](/azure/azure-monitor/logs/tutorial-workspace-transformations-portal.md)
+ 
+
 ## Examples of optimizing access logs using Workspace Transformations
 
 **Example 1: Selective Projection of Columns**: Imagine you have application gateway access logs with 20 columns, but you're interested in analyzing data from only six specific columns. By using workspace transformation, you can project these six columns into your workspace, effectively excluding the other 14 columns. Even though the original data from those excluded columns won't be stored, empty placeholders for them still appear in the Logs blade. This approach optimizes storage and ensures that only relevant data is retained for analysis.
@@ -58,7 +99,7 @@ Other storage locations:
 - **Azure Event Hubs**: Event hubs are a great option for integrating with other security information and event management (SIEM) tools to get alerts on your resources.
 - **Azure Monitor partner integrations**.
 
-Learn more about the Azure Monitor's [diagnostic settings destinations](/azure/azure-monitor/essentials/diagnostic-settings?WT.mc_id=Portal-Microsoft_Azure_Monitoring&tabs=portal#destinations) .
+Learn more about the Azure Monitor's [diagnostic settings destinations](/azure/azure-monitor/essentials/diagnostic-settings.md) .
 
 ## Enable logging through PowerShell
 
@@ -116,4 +157,4 @@ You can also connect to your storage account and retrieve the JSON log entries f
 
 - Visualize counter and event logs by using [Azure Monitor logs](/previous-versions/azure/azure-monitor/insights/azure-networking-analytics).
 - [Visualize your Azure activity log with Power BI](https://powerbi.microsoft.com/blog/monitor-azure-audit-logs-with-power-bi/) blog post.
-- [View and analyze Azure activity logs in Power BI and more](https://azure.microsoft.com/blog/analyze-azure-audit-logs-in-powerbi-more/) blog post.
+- [View and analyze Azure activity logs in Power BI and more](https://azure.microsoft.com/blog/analyze-azure-audit-logs-in-powerbi-more/) blog post.

articles/azure-health-insights/TOC.yml

@@ -23,7 +23,7 @@ items:
      - name: How to configure the containers
        href: configure-containers.md
      - name: Reliability in Azure Health Insights
-       href: ../reliability/reliability-health-insights.md?toc=/azure/health-insights/toc.json   
+       href: reliability-health-insights.md
 - name: Responsible use of AI
   expanded: true
   items:

…liability/reliability-health-insights.md …-insights/reliability-health-insights.mdarticles/reliability/reliability-health-insights.md renamed to articles/azure-health-insights/reliability-health-insights.md articles/reliability/reliability-health-insights.md renamed to articles/azure-health-insights/reliability-health-insights.md

@@ -3,7 +3,7 @@ title: Bicep functions - deployment
 description: Describes the functions to use in a Bicep file to retrieve deployment information.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 12/22/2025
+ms.date: 01/06/2026
 ---
 
 # Deployment functions for Bicep
@@ -61,59 +61,13 @@ For more information about Azure identities, see [What is an Azure Active Direct
 
 `deployment()`
 
-Returns information about the current deployment operation.
+Returns information about the current deployment operation. 
 
 Namespace: [az](bicep-functions.md#namespaces-for-functions).
 
 ### Return value
 
-This function returns the object that is passed during deployment. The properties in the returned object differ based on whether you are:
-
-- deploying a local Bicep file.
-- deploying to a resource group or deploying to one of the other scopes ([Azure subscription](deploy-to-subscription.md), [management group](deploy-to-management-group.md), or [tenant](deploy-to-tenant.md)).
-
-When deploying a local Bicep file to a resource group, the function returns the following format:
-
-```json
-{
-  "name": "",
-  "properties": {
-    "template": {
-      "$schema": "",
-      "contentVersion": "",
-      "parameters": {},
-      "variables": {},
-      "resources": [],
-      "outputs": {}
-    },
-    "templateHash": "",
-    "parameters": {},
-    "mode": "",
-    "provisioningState": ""
-  }
-}
-```
-
-When you deploy to an Azure subscription, management group, or tenant, the return object includes a `location` property. The `location` property isn't included when deploying a local Bicep file. The format is:
-
-```json
-{
-  "name": "",
-  "location": "",
-  "properties": {
-    "template": {
-      "$schema": "",
-      "contentVersion": "",
-      "resources": [],
-      "outputs": {}
-    },
-    "templateHash": "",
-    "parameters": {},
-    "mode": "",
-    "provisioningState": ""
-  }
-}
-```
+Bicep files are sometimes compiled to [languageVersion 2.0](../templates/syntax.md#languageversion-20) ARM templates. Therefore, Bicep type checking considers the `deployment()` function to return only the subset of properties as would be returned in a languageVersion 2.0 ARM template. For more information, see [deployment() function for languageVersion 2.0](../templates/template-functions-deployment.md#deployment ).
 
 ### Example
 
@@ -127,23 +81,23 @@ The preceding example returns the following object:
 
 ```json
 {
-  "name": "deployment",
+  "name": "deploymentOutput",
+  "location": "",
   "properties": {
     "template": {
-      "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
       "contentVersion": "1.0.0.0",
-      "resources": [],
-      "outputs": {
-        "deploymentOutput": {
-          "type": "Object",
-          "value": "[deployment()]"
+      "metadata": {
+        "_EXPERIMENTAL_WARNING": "This template uses ARM features that are experimental. Experimental features should be enabled for testing purposes only, as there are no guarantees about the quality or stability of these features. Do not enable these settings for any production usage, or your production environment may be subject to breaking.",
+        "_EXPERIMENTAL_FEATURES_ENABLED": [
+          "Asserts"
+        ],
+        "_generator": {
+          "name": "bicep",
+          "version": "0.39.26.7824",
+          "templateHash": "10348958332696598785"
         }
       }
-    },
-    "templateHash": "13135986259522608210",
-    "parameters": {},
-    "mode": "Incremental",
-    "provisioningState": "Accepted"
+    }
   }
 }
 ```

articles/azure-resource-manager/bicep/bicep-functions-deployment.md

@@ -3,7 +3,7 @@ title: Template functions - deployment
 description: Describes the functions to use in an Azure Resource Manager template (ARM template) to retrieve deployment information.
 ms.topic: reference
 ms.custom: devx-track-arm-template
-ms.date: 08/05/2025
+ms.date: 01/06/2026
 ---
 
 # Deployment functions for ARM templates
@@ -81,9 +81,9 @@ In Bicep, use the [`deployment`](../bicep/bicep-functions-deployment.md#deployme
 
 This function returns the object that's  passed during deployment. The properties in the returned object differ based on if you're:
 
-- Deploying a template or a template spec.
-- Deploying a template that's  a local file or deploying a template that's  a remote file accessed through a URI.
-- Deploying to a resource group or deploying to one of the other scopes ([Azure subscription](deploy-to-subscription.md), [management groups](deploy-to-management-group.md), or [tenants](deploy-to-tenant.md)).
+* Deploying a template or a template spec.
+* Deploying a template that's  a local file or deploying a template that's  a remote file accessed through a URI.
+* Deploying to a resource group or deploying to one of the other scopes ([Azure subscription](deploy-to-subscription.md), [management groups](deploy-to-management-group.md), or [tenants](deploy-to-tenant.md)).
 
 When deploying a local template to a resource group, the function returns the following format:
 
@@ -188,7 +188,8 @@ When deploying a [languageVersion 2.0](./syntax.md#languageversion-20) template,
   "location": "",
   "properties": {
     "template": {
-      "contentVersion": ""
+      "contentVersion": "",
+      "metadata": {}
     },
     "templateLink": {
       "id": "",
@@ -198,6 +199,8 @@ When deploying a [languageVersion 2.0](./syntax.md#languageversion-20) template,
 }
 ```
 
+The `location` property is included only for deployments at the [subscription](./deploy-to-subscription.md), [management group](./deploy-to-management-group.md), or [tenant](./deploy-to-tenant.md) scope. The `templateLink` property is included only when the user provides a linked template rather than an inline template.
+
 ### Remarks
 
 You can use `deployment()` to link to another template based on the URI of the parent template:

articles/azure-resource-manager/templates/template-functions-deployment.md

@@ -3,7 +3,7 @@ title: Restore Azure Kubernetes Service (AKS) via PowerShell using Azure Backup
 description: This article explains how to restore backed-up Azure Kubernetes Service (AKS) using Azure PowerShell.
 ms.topic: how-to
 ms.service: azure-backup
-ms.date: 01/30/2025
+ms.date: 01/07/2026
 ms.custom:
   - devx-track-azurepowershell
   - ignite-2023
@@ -34,7 +34,7 @@ Before you restore an AKS cluster, ensure that you meet the following prerequisi
 
 For more information on the limitations and supported scenarios, see the [support matrix](azure-kubernetes-service-cluster-backup-support-matrix.md).
 
-## Initialize Variables for Resource Commands
+## Initialize Variables for Resource Commands for AKS cluster restore
 
 Here, provide the necessary details for each resource to be used in your commands.
 
@@ -113,7 +113,7 @@ To prepare the restore request, run the following cmdlets:
     $aksRestoreRequest = Initialize-AzDataProtectionRestoreRequest -DatasourceType AzureKubernetesService  -SourceDataStore OperationalStore -RestoreLocation $restoreLocation -RestoreType AlternateLocation -TargetResourceId $targetAKSClusterId -RecoveryPoint $rp[0].Property.RecoveryPointId -RestoreConfiguration $aksRestoreCriteria -BackupInstance $AllInstances[2]
     ```
 
-## Trigger the restore
+## Trigger the restore for AKS cluster
 
 To trigger the restore operation, run the following cmdlets:
 
@@ -136,7 +136,7 @@ To trigger the restore operation, run the following cmdlets:
     $restoreJob = Start-AzDataProtectionBackupInstanceRestore -SubscriptionId $vaultSubId  -ResourceGroupName $vaultRgName -VaultName $vaultName -BackupInstanceName $AllInstances[2].BackupInstanceName -Parameter $aksRestoreRequest
     ```
 
-## Track the restore job
+## Track the restore job for AKS cluster
 
 Track all the jobs using the `Get-AzDataProtectionJob` cmdlet. You can list all jobs and fetch a particular job detail. Alternatively, use Az.ResourceGraph to track jobs across all Backup vaults.
 

articles/backup/azure-kubernetes-service-cluster-restore-using-powershell.md

@@ -184,7 +184,7 @@ If you're not using an LLM framework integration, you can interact with the sess
 
 ## Execute code in a session
 
-To execute code in a session, send a `POST` request to the `code/execute` endpoint with the code to run in the request body.
+To execute code in a session, send a `POST` request to the `code/execute` endpoint with the code to run in the request body. Each code execution is limited to a maximum runtime of 220 seconds.
 
 The following example prints `Hello, world!` in Python.
 

articles/container-apps/sessions-code-interpreter.md

@@ -10,8 +10,6 @@ items:
     href: overview-reliability-guidance.md
   - name: AI and machine learning
     items:
-    - name: Azure AI Health Insights
-      href: reliability-health-insights.md
     - name: Azure AI Search
       href: reliability-ai-search.md
     - name: Azure Bot Service