Merge pull request #307419 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-27 22:00 UTC

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

articles/azure-resource-manager/bicep/resource-declaration.md

@@ -3,7 +3,7 @@ title: Declare resources in Bicep
 description: Describes how to declare resources to deploy in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 04/28/2025
+ms.date: 10/24/2025
 ---
 
 # Resource declaration in Bicep
@@ -68,6 +68,7 @@ Decorators are written in the format `@expression` and are placed above resource
 | --------- | ----------- | ------- |
 | [batchSize](./bicep-import.md#export-variables-types-and-functions) | none | Set up instances to deploy sequentially. |
 | [description](#description) | string | Provide descriptions for the resource. |
+| [onlyIfNotExists](#onlyifnotexists) | none | Deploy the resource only if it doesn't already exist in the target scope. |
 
 Decorators are in the [sys namespace](bicep-functions.md#namespaces-for-functions). If you need to differentiate a decorator from another item with the same name, preface the decorator with `sys`. For example, if your Bicep file includes a parameter named `description`, you must add the sys namespace when using the **description** decorator.
 
@@ -99,6 +100,24 @@ resource storageAccountResources 'Microsoft.Storage/storageAccounts@2024-01-01'
 
 Markdown-formatted text can be used for the description text.
 
+### onlyIfNotExists
+
+By default, when a Bicep deployment runs, Azure Resource Manager (ARM) creates the resource if it doesn’t exist or updates it if it does. If an existing resource has properties that differ from your template, ARM might attempt to update it—or fail if updates aren’t permitted.
+
+Starting with Bicep version v0.38.3, the `@onlyIfNotExists()` decorator instructs ARM to create the resource only if it does not already exist. If a resource with the resource ID is found, ARM skips creation and leaves the existing resource unchanged.
+
+```bicep
+@onlyIfNotExists()
+resource example 'Microsoft.Storage/storageAccounts@2025-01-01' = {
+  name: 'mystorageacct'
+  location: resourceGroup().location
+  kind: 'StorageV2'
+  sku: {
+    name: 'Standard_LRS'
+  }
+}
+```
+
 ## Resource name
 
 Each resource has a name. When setting the resource name, pay attention to the [rules and restrictions for resource names](../management/resource-name-rules.md).

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

@@ -267,6 +267,7 @@ items:
         href: variables.md
         displayName: configuration
       - name: Resources (resource)
+        displayName: batchsize,onlyifnotexists,description,decorators
         href: resource-declaration.md
       - name: Outputs (output)
         href: outputs.md

articles/azure-resource-manager/management/azure-services-resource-providers.md

@@ -211,26 +211,28 @@ The resource providers for management services are:
 
 | Resource provider namespace | Azure service |
 | --------------------------- | ------------- |
-| Microsoft.Advisor | [Azure Advisor](/azure/advisor/) |
+| Microsoft.Advisor | [Azure Advisor](/azure/advisor/advisor-overview) |
 | Microsoft.Authorization - [registered by default](#registration) | [Azure Resource Manager](../index.yml) |
 | Microsoft.Automation | [Automation](../../automation/index.yml) |
-| Microsoft.Billing - [registered by default](#registration) | [Cost Management and Billing](/azure/billing/) |
+| Microsoft.Billing - [registered by default](#registration) | [Cost Management and Billing](../../cost-management-billing/index.yml) |
 | Microsoft.Blueprint | [Azure Blueprints](../../governance/blueprints/index.yml) |
+| Microsoft.ChangeSafety - [registered by default](#registration) | Safety checks that help Microsoft reduce risk and improve reliability in Microsoft service deployment |
 | Microsoft.ClassicSubscription - [registered by default](#registration) | Classic deployment model |
-| Microsoft.Consumption - [registered by default](#registration) | [Cost Management](/azure/cost-management/) |
-| Microsoft.CostManagement - [registered by default](#registration) | [Cost Management](/azure/cost-management/) |
-| Microsoft.CostManagementExports | [Cost Management](/azure/cost-management/) |
+| Microsoft.Consumption - [registered by default](#registration) | [Cost Management](../../cost-management-billing/index.yml) |
+| Microsoft.CostManagement - [registered by default](#registration) | [Cost Management](../../cost-management-billing/index.yml) |
+| Microsoft.CostManagementExports | [Cost Management](../../cost-management-billing/index.yml) |
 | Microsoft.CustomProviders | [Azure Custom Providers](../custom-providers/overview.md) |
 | Microsoft.DynamicsLcs | [Lifecycle Services](https://lcs.dynamics.com/Logon/Index) |
 | Microsoft.Features - [registered by default](#registration) | [Azure Resource Manager](../index.yml) |
 | Microsoft.GuestConfiguration | [Azure Policy](../../governance/policy/index.yml) |
-| Microsoft.ManagedServices | [Azure Lighthouse](/azure/lighthouse/) |
+| Microsoft.ManagedServices | [Azure Lighthouse](/azure/lighthouse/overview) |
 | Microsoft.Management | [Management Groups](../../governance/management-groups/index.yml) |
 | Microsoft.PolicyInsights | [Azure Policy](../../governance/policy/index.yml) |
-| Microsoft.Portal - [registered by default](#registration) | [Azure portal](/azure/azure-portal/) |
+| Microsoft.Portal - [registered by default](#registration) | [Azure portal](/azure/azure-portal/azure-portal-overview) |
 | Microsoft.RecoveryServices | [Azure Site Recovery](../../site-recovery/index.yml) |
 | Microsoft.ResourceGraph - [registered by default](#registration) | [Azure Resource Graph](../../governance/resource-graph/index.yml) |
-| Microsoft.ResourceHealth | [Azure Service Health](/azure/service-health/) |
+| Microsoft.ResourceHealth | [Azure Service Health](/azure/service-health/overview) |
+| Microsoft.ResourceNotification - [registered by default](#registration) | [Azure Resource Notifications](../../event-grid/event-schema-resource-notifications.md) |
 | Microsoft.Resources - [registered by default](#registration) | [Azure Resource Manager](../index.yml) |
 | Microsoft.Scheduler | [Scheduler](../../scheduler/index.yml) |
 | Microsoft.SoftwarePlan | License |

articles/cost-management-billing/manage/understand-mca-roles.md

@@ -25,6 +25,7 @@ Watch the [Manage access to your MCA billing account](https://www.youtube.com/wa
 
 The following table describes the billing roles you use to manage your billing account, billing profiles, and invoice sections. Permissions granted at the billing account level have the highest level of permission and will inherit permission on all billing groups and invoice sections under that billing account. These inherited permissions cannot be removed at the lower level as they are linked to the role granted at the higher level. If a user only needs access to a specific billing profile or invoice section, grant permission at that level rather than providing access at the billing account scope.
 
+
 |Role|Description|
 |---|---|
 |Billing account owner |Manage everything for billing account|
@@ -211,6 +212,9 @@ To assign billing roles, you might need to use a specific navigation path in the
 6. To remove access for a user, select the user with the role assignment you want to remove. At the top of the page, select **Remove**.  
    :::image type="content" border="true" source="./media/understand-mca-roles/billing-remove-admin.png" alt-text="Screenshot that shows removing an admin from a billing account." lightbox="./media/understand-mca-roles/billing-remove-admin.png":::
 
+>[!NOTE]
+> You'll need to keep one user with “This scope” permissions. Removing the last user with this scope is not allowed.
+
 ## Check access to a Microsoft Customer Agreement
 [!INCLUDE [billing-check-mca](../../../includes/billing-check-mca.md)]
 

articles/firmware-analysis/release-notes.md

@@ -11,9 +11,27 @@ ms.service: azure
 # What's new in firmware analysis
 
 This article lists new features and feature enhancements in the firmware analysis service.
+Get notified about when to revisit this page for updates by copying and pasting this URL:
 
+> `https://learn.microsoft.com/api/search/rss?search=%22What%27s+new+in+firmware+analysis%22&locale=en-us`
 
-## October 2025
+into your RSS feed reader.
+
+
+## October 27, 2025
+
+- **Page size picker**: Added the ability for users to change the number of analysis results displayed per page, providing more flexibility when reviewing large sets of findings.
+
+- **CSV filenames**: Updated the naming convention for CSV downloads. Filenames now include Vendor / Model / Version of the firmware for easier identification and organization.
+
+- **CVE support**: Expanded support for newly disclosed CVEs across multiple libraries, including Apache, OpenSSL, Nginx, Samba, and others. This ensures broader coverage and improved vulnerability detection.
+
+- **Cramfs extraction fix**: Resolved issues with Cramfs filesystem extraction, improving reliability and accuracy of analysis results.
+
+- **jQuery detection improvement**: Enhanced identification of the jQuery library in firmware components, improving accuracy in component analysis.
+
+
+## October 7, 2025
 
 - **Firmware analysis is now GA**: We're happy to announce GA with this release.
 

articles/iot-operations/manage-mqtt-broker/howto-broker-persistence.md

@@ -6,7 +6,7 @@ ms.author: sonialopez
 ms.topic: how-to
 ms.service: azure-iot-operations
 ms.subservice: azure-mqtt-broker
-ms.date: 07/28/2025
+ms.date: 10/27/2025
 
 ---
 
@@ -63,27 +63,40 @@ To configure volume settings in the Azure portal:
 
 # [Azure CLI](#tab/azurecli)
 
-To configure volume settings using Azure CLI, prepare a Broker configuration file in JSON format:
+1. To deploy MQTT Broker with the minimum required settings to enable disk persistence, use the `az iot ops create` command.
 
-```json
-{
-  "persistence": {
-    "maxSize": "10GiB",
-    "persistentVolumeClaimSpec": {
-      "storageClassName": "example-storage-class",
-      "accessModes": [
-        "ReadWriteOncePod"
-      ]
-    }
-  }
-}
-```
+    ```azurecli
+    az iot ops create --cluster <CLUSTER_NAME> -g <RESOURCE_GROUP_NAME> --name <INSTANCE_NAME> --sr-resource-id <SCHEMA_REGISTRY_RESOURCE_ID> --ns-resource-id <NAMESPACE_RESOURCE_ID> --persist-max-size 10Gi
+    ```
 
-Then run the [az iot ops create](/cli/azure/iot/ops#az-iot-ops-create) command with the `--broker-config-file` flag to deploy IoT Operations:
+1. To deploy MQTT Broker with disk persistence, custom persistent volume claim, and custom persist mode settings, add the `--persist-pvc-sc` and `--persist-mode` flags to the `az iot ops create` command.
 
-```azurecli
-az iot ops create --broker-config-file <BROKER_CONFIG_FILE>.json --cluster <CLUSTER_NAME> --name <INSTANCE_NAME> --resource-group <RESOURCE_GROUP_NAME> --sr-resource-id <SCHEMA_REGISTRY_RESOURCE_ID>
-```
+    ```azurecli
+    az iot ops create --cluster <CLUSTER_NAME> -g <RESOURCE_GROUP_NAME> --name <INSTANCE_NAME> --sr-resource-id <SCHEMA_REGISTRY_RESOURCE_ID> --ns-resource-id <NAMESPACE_RESOURCE_ID> --persist-max-size 10Gi --persist-pvc-sc <MYSTORAGECLASS> --persist-mode retain=All stateStore=None
+    ```
+
+
+1. If you want to use a custom broker configuration file, add the `--broker-config-file` flag and include the persistence settings in the JSON file.
+
+    ```azurecli
+    az iot ops create --broker-config-file <BROKER_CONFIG_FILE>.json --cluster <CLUSTER_NAME> --name <INSTANCE_NAME> --resource-group <RESOURCE_GROUP_NAME> --sr-resource-id <SCHEMA_REGISTRY_RESOURCE_ID>
+    ```
+
+    The following is an example JSON snippet to include in your custom broker configuration file to set up persistence with a maximum size of 10 GiB and a custom storage class.
+    
+    ```json
+    {
+      "persistence": {
+        "maxSize": "10GiB",
+        "persistentVolumeClaimSpec": {
+          "storageClassName": "example-storage-class",
+          "accessModes": [
+            "ReadWriteOncePod"
+          ]
+        }
+      }
+    }
+    ```
 
 ---
 

articles/migrate/toc.yml

@@ -79,7 +79,7 @@ items:
     #       href: add-server-credentials.md
     #     - name: Appliance diagnostics
     #       href: troubleshoot-appliance-diagnostic.md 
-    - name: Discover softwares and workloads
+    - name: Discover software and workloads
       href: how-to-discover-applications.md
     - name: Deep discover database workloads
       items:

articles/oracle/oracle-db/oracle-database-regions.md

@@ -45,6 +45,7 @@ The list below mentions the Azure and corresponding OCI regions with the regiona
 |Azure region |OCI region  | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure | Oracle Database Autonomous Recovery Service@Azure| Exadata Database Service on Exascale Infrastructure@Azure | BaseDB | Golden Gate | Regional Availability |
 |------------|--|--------------------------|------------------------------| ------| ---- | ---- |----|-------|
 | France Central       |France central (Paris) | ✓   | ✓ | ✓ | ✓ | | |  Dual |
+| France South | France South (Marseille) |  ✓  | | | | | |   Single    |
 | Germany North |Germany Central (Frankfurt) | ✓  | ✓ | | | | |   Single    |
 | Germany West Central |Germany Central (Frankfurt) |  ✓  | ✓ | ✓ | ✓ | ✓ | ✓ | Dual |
 | Italy North | Italy North (Milan)   | ✓   | ✓   | ✓ |  ✓ | ✓ |  | Dual |

articles/sentinel/includes/data-connector-agent-deprecation.md

@@ -0,0 +1,9 @@
+---
+ms.topic: include
+ms.date: 10/20/2025
+ms.author: monaberdugo
+author: mberdugo
+---
+
+> [!IMPORTANT]
+> The data connector agent for SAP is being deprecated. We recommend that you migrate to the [agentless data connector](../sap/deploy-sap-security-content.md?pivots=connection-agentless).

articles/sentinel/sap/collect-sap-hana-audit-logs.md

@@ -23,7 +23,7 @@ Content in this article is intended for your **security**, **infrastructure**, a
 > Microsoft Sentinel SAP HANA support is currently in PREVIEW. The [Azure Preview Supplemental Terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 > [!NOTE]
-> This article is relevant only for the data connector agent, and isn't relevant for the [SAP agentless data connector](deployment-overview.md#data-connector) (Preview).
+> This article is relevant only for the data connector agent, and isn't relevant for the [SAP agentless data connector](deployment-overview.md#data-connector).
 >
 
 ## Prerequisites