You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
Copy file name to clipboardExpand all lines: articles/connectors/connectors-azure-monitor-logs.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: logic-apps
5
5
ms.suite: integration
6
6
ms.reviewer: estfan, azla
7
7
ms.topic: how-to
8
-
ms.date: 04/15/2025
8
+
ms.date: 12/09/2025
9
9
# Customer intent: As a developer, I want to get log data from my Log Analytics workspace or telemetry from my Application Insights resource to use with my workflow in Azure Logic Apps.
10
10
---
11
11
@@ -41,7 +41,9 @@ Both of the following actions can run a log query against a Log Analytics worksp
41
41
42
42
## Limitations
43
43
44
-
- The connector has the following limits, which your workflow might reach, based on the query that you use and the size of the results:
44
+
- Visualizations on the Logs page and the connector use different charting libraries. So, the connector currently doesn't include some functionality.
45
+
- Query data in Basic and Auxiliary plans isn't supported by Azure Monitor Logs connector.
46
+
- The connector has the following query limits. To avoid limits, try aggregating data to reduce the results count or volume, or adjusting the workflow recurrence to run more frequently across a smaller time range.
45
47
46
48
| Limit | Value | Notes |
47
49
|-------|-------|-------|
@@ -50,10 +52,6 @@ Both of the following actions can run a log query against a Log Analytics worksp
50
52
| Max connector timeout | 110 seconds ||
51
53
| Max query timeout | 100 seconds ||
52
54
53
-
To avoid reaching these limits, try aggregating data to reduce the results size, or adjusting the workflow recurrence to run more frequently across a smaller time range.
54
-
55
-
- Visualizations on the Logs page and the connector use different charting libraries. So, the connector currently doesn't include some functionality.
56
-
57
55
## Prerequisites
58
56
59
57
- An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
Copy file name to clipboardExpand all lines: articles/cost-management-billing/manage/mosp-ea-transfer.md
+1-26Lines changed: 1 addition & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,34 +73,9 @@ As described in the [prerequisites](#access-to-the-destination-ea) section, you
73
73
After the EA account owner is created the subscription account Administrator, who is also now an EA account owner, receives an email. It notifies the user that they're now an EA Account Owner. If the user doesn't have access to an email mailbox associated with the account specified, there's no need to worry. The email is only a notification. Information in the email isn't required to proceed. However, an email mailbox is advised for future notifications about the subscription.
74
74
75
75
### Complete the subscription transfer
76
-
77
-
Now that the subscription account administrator is also an EA account owner, they can create subscriptions under the EA.
78
-
79
-
> [!IMPORTANT]
80
-
> Before proceeding you need to understand what happens when a new EA account owner signs in to the Azure portal for the first time. Read and understand the following information before you sign in as the subscription account administrator.
81
-
82
-
The first time a new EA account owner signs in to the Azure portal, they see the following warning:
83
-
84
-
```
85
-
WARNING
86
-
87
-
You are about to associate your account (email address) to the following enrollment:
88
-
89
-
Enrollment Name: <EnrollmentName>
90
-
Enrollment Number: <EnrollmentNumber>
91
-
92
-
All Enrollment Administrators can gain access to all of your subscriptions if you proceed.
93
-
Additionally, all Azure subscriptions for which you are the account owner will be converted to your Enterprise Agreement.
94
-
This includes subscriptions which include a monthly credit (e.g. Visual Studio, Microsoft Cloud Partner Program, BizSpart, etc.) meaning you will lose the monthly credit by proceeding.
95
-
All subscriptions based on a Visual Studio subscriber offer (monthly credit for Visual Studio subscribers or Pay-As-You-Go Dev/Test) will be converted to use the Enterprise Dev/Test usage rates and be billed against this enrollment from today onwards.
96
-
If you wish to retain the monthly credits currently associated with any of your subscriptions, please cancel.
97
-
Please see additional details.
98
-
99
-
Cancel Continue
100
-
```
76
+
To complete the subscription transfer, a new EA Account owner needs to [activate account](direct-ea-administration.md#to-confirm-account-ownership-1) on the Azure portal.
101
77
102
78
The warning states the following:
103
-
104
79
***When a user is added as an account owner, any Azure subscriptions associated with the account owner that are based on either the MOSP (PAYG) Dev/Test offer or the monthly credit offers for Visual Studio subscribers will be converted to the EA Dev/Test offer. Subscriptions based on other offer types, such as MOSP (PAYG), associated with the Account Owner will be converted to the standard EA subscription offer.***
105
80
106
81
If the user understands the consequences of the warning, select **Continue** and the subscriptions associated with their account are transferred to the EA.
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-import-device-information.md
+50-15Lines changed: 50 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
2
title: Import extra data for detected OT devices - Microsoft Defender for IoT
3
3
description: Learn how to manually enhance the device data automatically detected by your Microsoft Defender for IoT OT sensor with extra, imported data.
4
-
ms.date: 01/24/2023
4
+
ms.date: 11/26/2025
5
5
ms.topic: how-to
6
6
---
7
7
8
8
# Import extra data for detected OT devices
9
9
10
-
OT networks sensors automatically monitor and analyze detected device traffic. In some cases, your organization's network policies may prevent some device data from being ingested to Microsoft Defender for IoT.
10
+
OT network sensors automatically monitor and analyze detected device traffic. In some cases, your organization's network policies might prevent some device data from being ingested to Microsoft Defender for IoT.
11
11
12
12
This article describes how you can manually import the missing data to your OT sensor and add it to the device data already detected.
13
13
@@ -21,7 +21,7 @@ Before performing the procedures in this article, you must have:
21
21
22
22
- An understanding of the extra device data you want to import. Use that understanding to choose one of the following import methods:
23
23
24
-
-**Import data from the device map** to import device names, types, groups, or Purdue layer
24
+
-**Import data from the device map** to import device names, operating systems, groups, or Purdue layer
25
25
-**Import data from system settings** to import device IP addresses, operating systems, patch levels, or authorization statuses
26
26
27
27
> [!TIP]
@@ -36,7 +36,7 @@ Before performing the procedures in this article, you must have:
36
36
1. Open the downloaded .CSV file for editing and modify *only* the following data, as needed:
37
37
38
38
-**Name**. Maximum length: 30 characters
39
-
-**Type**. Access the Defender for IoT [device settings file](https://download.microsoft.com/download/8/2/3/823c55c4-7659-4236-bfda-cc2427be2cee/CSS/devices_info_2.2.8%20and%20up.xlsx) and use one of the options listed in the **Devices type** tab
39
+
-**Device type**. The device’s functional role (for example, printer, surveillance camera, or smart appliance).
40
40
-**Group**. Maximum length: 30 characters
41
41
-**Purdue layer**. Enter one of the following: **Enterprise**, **Supervisory**, or **Process Control**
42
42
@@ -47,32 +47,66 @@ Before performing the procedures in this article, you must have:
47
47
48
48
1. When you're done, save your file to a location accessible from your OT sensor.
49
49
50
-
1. On your OT sensor, in the **Device map** page, select **Import Devices** and select your modified .CSV file.
50
+
1. On your OT sensor, in the **Device map** page, select **Import Devices** and select your modified .csv file.
51
51
52
52
Your device data is updated.
53
53
54
54
## Import data from the OT sensor system settings
55
55
56
56
**To import device IP addresses, operating systems, or patch levels**:
57
57
58
-
1.Download the Defender for IoT [device settings file](https://download.microsoft.com/download/8/2/3/823c55c4-7659-4236-bfda-cc2427be2cee/CSS/devices_info_2.2.8%20and%20up.xlsx) and open it for editing.
58
+
1.In Excel, open a blank workbook and select **Save As** to save it in `.csv` format.
59
59
60
-
1. In the downloaded file, enter the following details for each device:
60
+
1. In your .csv file, type the following details for each device:
61
61
62
62
-**IP Address**. Enter the device's IP address.
63
-
-**Device Type**. Enter one of the device types listed on the **Devices type** sheet.
63
+
-**Device OS**. Enter one of the device operating systems listed in the [supported values for the Device OS table](#supported-values-for-device-operating-system).
64
64
-**Last Update**. Enter the date that the device was last updated, in `YYYY-MM-DD` format.
65
65
66
-
1. Sign into your OT sensor and select **System settings > Import settings > Device information**.
66
+
The following sections include information to help you fill in the Device OS column: The [device information example](#device-information-example) includes sample device details, and the [supported values table](#supported-values-for-device-operating-system) includes the supported operating system values.
67
67
68
-
1. In the **Device information** pane, select **+ Import file** and then select your edited .CSV file.
68
+
### Device information example
69
69
70
-
1. Select **Close** to save your changes.
70
+
|**IP Address**|**Device OS**|**Last Update**|
71
+
|---------|---------|---------|
72
+
|192.168.19.200 | Windows 7 | 2017-11-01 |
73
+
74
+
75
+
### Supported values for Device operating system
76
+
77
+
| Windows | Windows Server | Other OS |
78
+
|---|---|---|
79
+
| Windows | Windows Server | macOS |
80
+
| Windows 11 | Windows Server 2003 | macOS X |
81
+
| Windows 10 | Windows Server 2003 R2 | Linux |
82
+
| Windows 10 32 | Windows Server 2008 | HP UX |
83
+
| Windows 10 64 | Windows Server 2008 32 | QNX |
84
+
| Windows 7 | Windows Server 2008 64 ||
85
+
| Windows 7 32 | Windows Server 2008 R2 ||
86
+
| Windows 7 64 | Windows Server 2012 ||
87
+
| Windows 8 | Windows Server 2012 R2 ||
88
+
| Windows 8 32 | Windows Server 2016 ||
89
+
| Windows 8 64 | Windows Server 2019 ||
90
+
| Windows 8.1 | Windows Server 2022 ||
91
+
| Windows 8.1 32 |||
92
+
| Windows 8.1 64 |||
93
+
| Windows NT |||
94
+
| Windows 2000 |||
95
+
| Windows Vista |||
96
+
| Windows Vista 32 |||
97
+
| Windows Vista 64 |||
98
+
| Windows XP |||
99
+
100
+
101
+
3. Sign into your OT sensor and select **System settings > Import settings > Device information**.
102
+
103
+
4. In the **Device information** pane, select **+ Import file** and then select your edited .csv file.
104
+
105
+
5. Select **Close** to save your changes.
71
106
72
-
**To import device authorization status**:
107
+
### Import device authorization status:
73
108
74
-
> [!IMPORTANT]
75
-
> After importing device authorization status, any devices *not* included in the import list are newly defined as not-authorized, and you'll start to receive new alerts about any traffic on each of these devices.
109
+
After importing device authorization status, any devices *not* included in the import list are newly defined as not-authorized, and you'll start to receive new alerts about any traffic on each of these devices.
76
110
77
111
1. Download the Defender for IoT [device authorization file](https://download.microsoft.com/download/8/2/3/823c55c4-7659-4236-bfda-cc2427be2cee/CSS/authorized_devices%20-%20example.csv) and open it for editing.
78
112
@@ -88,4 +122,5 @@ Your device data is updated.
88
122
89
123
## Next steps
90
124
91
-
For more information, see [Detect Windows workstations and servers with a local script](detect-windows-endpoints-script.md) and [Manage your OT device inventory from a sensor console](how-to-investigate-sensor-detections-in-a-device-inventory.md).
125
+
-[Detect Windows workstations and servers with a local script](detect-windows-endpoints-script.md)
126
+
-[Manage your OT device inventory from a sensor console](how-to-investigate-sensor-detections-in-a-device-inventory.md).
> ** Azure-managed certificates will no longer be supported on CDN Standard from Microsoft (classic) starting August 15, 2025. Existing managed certificates will remain valid until April 14, 2026. [Learn more](https://azure.microsoft.com/updates?id=498522)
101
+
> ** Azure-managed certificates will no longer be supported on Azure Front Door (classic) and CDN Standard from Microsoft (classic) starting August 15, 2025. Existing managed certificates will remain valid until April 14, 2026. [Learn more](https://azure.microsoft.com/updates?id=498522)
Copy file name to clipboardExpand all lines: articles/service-bus-messaging/service-bus-async-messaging.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@ Asynchronous messaging can be implemented in a variety of different ways. With q
11
11
12
12
Applications typically use asynchronous messaging patterns to enable a number of communication scenarios. You can build applications in which clients can send messages to services, even when the service is not running. For applications that experience bursts of communications, a queue can help [level the load](/azure/architecture/patterns/queue-based-load-leveling) by providing a place to buffer communications. Finally, you can get a simple but effective load balancer to distribute messages across multiple machines.
13
13
14
+
For a real-world analogy of asynchronous scalability and expected delays or retries, see Gregor Hohpe’s [Starbucks Does Not Use Two-Phase Commit](https://www.enterpriseintegrationpatterns.com/ramblings/18_starbucks.html) and the follow-up [What Starbucks Can Teach Us About Software Scalability](https://particular.net/blog/what-starbucks-can-teach-us-about-software-scalability). They offer a clear mental model for how Service Bus behaves under load.
15
+
14
16
In order to maintain availability of any of these entities, consider a number of different ways in which these entities can appear unavailable for a durable messaging system. Generally speaking, we see the entity becomes unavailable to applications we write in the following different ways:
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments