Skip to content

Commit d72002a

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-vnetflowlogs
2 parents ada5932 + 2021c96 commit d72002a

51 files changed

Lines changed: 374 additions & 241 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
-53.9 KB
Loading
-53.9 KB
Loading

articles/azure-change-tracking-inventory/quickstart-monitor-changes-collect-inventory-azure-change-tracking-inventory.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Quickstart - Enable Azure Change Tracking and Inventory for single and multiple machines from the portal
33
description: In this quickstart, learn how to enable Azure Change Tracking and Inventory for single and multiple machines from the portal.
44
services: automation
5-
ms.date: 12/03/2025
5+
ms.date: 12/09/2025
66
ms.topic: quickstart
77
#Customer intent: As a customer, I want to enable Azure Change Tracking and Inventory so that I can further use the CTI services.
88
ms.service: azure-change-tracking-inventory
@@ -98,10 +98,6 @@ To enable Azure CTI for multiple Azure VMs using portal, follow these steps:
9898
> [!NOTE]
9999
> You can enable CTI on up to 250 virtual machines at a time.
100100
101-
1. On the **Enable Change Tracking** pane, select the banner at the top of the pane, **Click here to try new change tracking and inventory with Azure Monitor Agent (AMA) experience**.
102-
103-
:::image type="content" source="media/create-data-collection-rule/enable-change-tracking-multiple-virtual-machines-inline.png" alt-text="Screenshot showing how to select enable change tracking for multiple Virtual Machines from the portal." lightbox="media/create-data-collection-rule/enable-change-tracking-multiple-virtual-machines-expanded.png":::
104-
105101
1. On the **Enable Change Tracking** pane, you can view the list of machines that are enabled, ready to be enabled and the ones that you can't enable. You can use the filters to select the **Subscription**, **Location**, and **Resource groups**. You can select a maximum of three resource groups.
106102

107103
:::image type="content" source="media/create-data-collection-rule/change-tracking-status-inline.png" alt-text="Screenshot showing the status of multiple VMs." lightbox="media/create-data-collection-rule/change-tracking-status-expanded.png":::

articles/azure-resource-manager/bicep/bicep-core-diagnostics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ If you need more information about a particular diagnostic code, select the **Fe
139139
| <a id='BCP127' />[BCP127](./diagnostics/bcp127.md) | Error | Function `<function-name>` can't be used as a resource decorator. |
140140
| <a id='BCP128' />[BCP128](./diagnostics/bcp128.md) | Error | Function `<function-name>` can't be used as a module decorator. |
141141
| <a id='BCP129' />[BCP129](./diagnostics/bcp129.md) | Error | Function `<function-name>` can't be used as an output decorator. |
142-
| <a id='BCP130' />BCP130 | Error | Decorators aren't allowed here. |
142+
| <a id='BCP130' />[BCP130](./diagnostics/bcp130.md) | Error | Decorators aren't allowed here. |
143143
| <a id='BCP132' />[BCP132](./diagnostics/bcp132.md) | Error | Expected a declaration after the decorator. |
144144
| <a id='BCP133' />BCP133 | Error | The unicode escape sequence isn't valid. Valid unicode escape sequences range from \\u{0} to \\u{10FFFF}. |
145145
| <a id='BCP134' />BCP134 | Error | Scope `<scope-name>` isn't valid for this module. Permitted scopes: `<scope-name>`. |
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: BCP130
3+
description: Decorators are not allowed here.
4+
ms.topic: reference
5+
ms.custom: devx-track-bicep
6+
ms.date: 10/30/2025
7+
---
8+
9+
# Bicep diagnostic code - BCP130
10+
11+
This diagnostic occurs when [`decorators`](../parameters.md#use-decorators) (such as `@description`, `@allowed`, etc.) are used in contexts where they aren't supported—specifically within `.bicepparam` files. While decorators remain valid in `.bicep` files for parameter declarations, they have no effect in parameter files and are now explicitly disallowed.
12+
13+
## Description
14+
15+
Decorators are not allowed here.
16+
17+
## Level
18+
19+
Error
20+
21+
## Solutions
22+
23+
Remove decorators from Bicep parameter files. For more information about using parameters, see [Using parameters](../parameters.md#use-decorators).
24+
25+
## Examples
26+
27+
The following example raises the diagnostic because the `@description` decorator is used in a `.bicepparam` file.
28+
29+
```bicep
30+
using './main.bicep'
31+
32+
@description('The name of the storage account to create.')
33+
param storageName = 'mystorageacct'
34+
param storageSKU = 'Standard_LRS'
35+
```
36+
37+
You can fix the diagnostic by removing the `@description` decorator.
38+
39+
```bicep
40+
using './main.bicep'
41+
42+
param storageName = 'mystorageacct'
43+
param storageSKU = 'Standard_LRS'
44+
```
45+
46+
## Next steps
47+
48+
For more information about Bicep diagnostics, see [Bicep core diagnostics](../bicep-core-diagnostics.md).

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -705,6 +705,8 @@ items:
705705
href: diagnostics/bcp128.md
706706
- name: BCP129
707707
href: diagnostics/bcp129.md
708+
- name: BCP130
709+
href: diagnostics/bcp130.md
708710
- name: BCP132
709711
href: diagnostics/bcp132.md
710712
- name: BCP135

articles/azure-web-pubsub/howto-develop-event-listener.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,9 @@ Find your Azure Web PubSub service from **Azure portal**. Navigate to **Identity
6767

6868
## Test your configuration with live demo
6969

70-
1. Open this [Event Hubs Consumer Client](https://awpseventlistenerdemo.z13.web.core.windows.net/eventhub-consumer/index.html) web app, input the Event Hubs connection string to connect to an event hub as a consumer. If you get the Event Hubs connection string from an Event Hubs namespace resource instead of an event hub instance, then you need to specify the event hub name. This event hub consumer client is connected with the mode that only reads new events; the events published before aren't seen here. You can change the consumer client connection mode to read all the available events in the production environment.
70+
1. Open this [Event Hubs Consumer Client](https://aka.ms/awps/event-listener-demo/eventhub-consumer) web app, input the Event Hubs connection string to connect to an event hub as a consumer. If you get the Event Hubs connection string from an Event Hubs namespace resource instead of an event hub instance, then you need to specify the event hub name. This event hub consumer client is connected with the mode that only reads new events; the events published before aren't seen here. You can change the consumer client connection mode to read all the available events in the production environment.
7171

72-
1. Use this [WebSocket Client](https://awpseventlistenerdemo.z13.web.core.windows.net/webpubsub-client/websocket-client.html) web app to generate client events. If you've configured to send system event `connected` to that event hub, you should be able to see a printed `connected` event in the Event Hubs consumer client after connecting to Web PubSub service successfully. You can also generate a user event with the app.
72+
1. Use this [WebSocket Client](https://aka.ms/awps/event-listener-demo/websocket-client) web app to generate client events. If you've configured to send system event `connected` to that event hub, you should be able to see a printed `connected` event in the Event Hubs consumer client after connecting to Web PubSub service successfully. You can also generate a user event with the app.
7373
:::image type="content" source="media/howto-develop-event-listener/eventhub-consumer-connected-event.png" alt-text="Screenshot of a printed connected event in the Event Hubs consumer client app.":::
7474
:::image type="content" source="media/howto-develop-event-listener/web-pubsub-client-specify-event-name.png" alt-text="Screenshot showing the area of the WebSocket client app to generate a user event.":::
7575

articles/backup/backup-azure-delete-vault.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Delete a Microsoft Azure Recovery Services vault
33
description: In this article, learn how to remove dependencies and then delete an Azure Backup Recovery Services vault.
44
ms.topic: how-to
5-
ms.date: 11/18/2025
5+
ms.date: 12/09/2025
66
ms.service: azure-backup
77
author: AbhishekMallick-MS
88
ms.author: v-mallicka
@@ -82,7 +82,9 @@ To delete a vault, follow these steps:
8282
8383
- <a id="portal-delete-backup-servers">**Step 5:**</a> Delete Backup Servers
8484

85-
1. Go to the vault dashboard menu > **Backup Infrastructure** > **Protected Servers**. In Protected Servers, select the server to unregister. To delete the vault, you must unregister all the servers. Right-click each protected server and select **Unregister**.
85+
Before deleting the vault, ensure that all on-premises backup servers are unregistered from the vault. To unregister the servers, perform the following steps based on your on-premises scenario:
86+
87+
1. Go to the vault dashboard menu > **Backup Infrastructure** > **Protected Servers**. In Protected Servers, select the backup management type from the list. To delete the vault, you must unregister all the servers. On the selected backup management pane, select the **more icon ( ... )** corresponding to each protected server and select **Unregister**.
8688

8789
1. **MARS protected servers**: Go to the vault dashboard menu -> **Backup Infrastructure** -> **Protected Servers**. If you've MARS protected servers, then all servers listed here must be deleted along with their backup data. [Follow these steps](#delete-protected-items-on-premises) to delete MARS protected servers.
8890

articles/backup/backup-azure-monitor-troubleshoot.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Troubleshoot monitoring issues for Azure Backup
33
description: Learn how to troubleshoot monitoring issues for Azure Backup.
44
ms.topic: troubleshooting
5-
ms.date: 12/30/2024
5+
ms.date: 12/09/2025
66
ms.service: azure-backup
77
ms.custom: engagement-fy24
88
author: AbhishekMallick-MS
@@ -40,4 +40,5 @@ Learn [about the best practices for Azure Monitor alerts](/azure/azure-monitor/b
4040

4141
## Next steps
4242

43-
[Common questions about backup monitoring alert](backup-azure-monitor-alert-faq.yml)
43+
- [Common questions about backup monitoring alert](backup-azure-monitor-alert-faq.yml).
44+
- [Manage Azure Monitor based alerts for Azure Backup](backup-azure-monitoring-alerts.md).

articles/backup/backup-azure-monitoring-alerts.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Manage Azure Monitor based alerts for Azure Backup
33
description: Learn about the new and improved alerting capabilities via Azure Monitor and the process to configure Azure Monitor.
44
ms.topic: how-to
5-
ms.date: 07/03/2025
5+
ms.date: 12/09/2025
66
ms.service: azure-backup
77
author: AbhishekMallick-MS
88
ms.author: v-mallicka
@@ -263,4 +263,5 @@ To configure the same, run the following commands:
263263
```
264264

265265
## Next steps
266-
Learn more about [Azure Backup monitoring and reporting](monitoring-and-alerts-overview.md).
266+
- Learn more about [Azure Backup monitoring and reporting](monitoring-and-alerts-overview.md).
267+
- [Troubleshoot monitoring issues for Azure Backup](backup-azure-monitor-troubleshoot.md).

0 commit comments

Comments
 (0)