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
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/reference-connect-faq.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -143,7 +143,7 @@ sections:
143
143
- question: |
144
144
Are single label domains (SLDs) supported?
145
145
answer: |
146
-
While we strongly recommend against this network configuration ([see article](https://support.microsoft.com/help/2269810/microsoft-support-for-single-label-domains)), using Azure AD Connect sync with a single label domain is supported, as long as the network configuration for the single level domain is functioning correctly.
146
+
While we strongly recommend against this network configuration ([see article](https://support.microsoft.com/help/2269810/microsoft-support-for-single-label-domains)), using Azure AD Connect sync with a single label domain is supported, as long as the network configuration for the single level domain is functioning correctly. In SLD scenarios where the Active Directory NetBIOS domain name differs from the FQDN domain name, it's unsupported to install Azure AD Connect.
Copy file name to clipboardExpand all lines: articles/aks/use-psa.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 @@ ms.date: 08/08/2022
11
11
12
12
Pod Security Admission enforces Pod Security Standards policies on pods running in a namespace. Pod Security Admission is enabled by default in AKS and is controlled by adding labels to a namespace. For more information about Pod Security Admission, see [Enforce Pod Security Standards with Namespace Labels][kubernetes-psa]. For more information about the Pod Security Standards used by Pod Security Admission, see [Pod Security Standards][kubernetes-pss].
13
13
14
+
Pod Security Admission is a built-in policy solution for single cluster implementations. If you are looking for enterprise-grade policy, then [Azure policy](use-azure-policy.md) is a better choice.
15
+
14
16
## Before you begin
15
17
16
18
- An Azure subscription. If you don't have an Azure subscription, you can create a [free account](https://azure.microsoft.com/free).
Copy file name to clipboardExpand all lines: articles/azure-monitor/agents/data-collection-rule-azure-monitor-agent.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,15 +29,15 @@ To send data to Log Analytics, create the data collection rule in the **same reg
29
29
1. From the **Monitor** menu, select **Data Collection Rules**.
30
30
1. Select **Create** to create a new Data Collection Rule and associations.
31
31
32
-
[](media/data-collection-rule-azure-monitor-agent/data-collection-rules-updated.png#lightbox)
32
+
[](media/data-collection-rule-azure-monitor-agent/data-collection-rules-updated.png#lightbox)
33
33
34
34
1. Provide a **Rule name** and specify a **Subscription**, **Resource Group**, **Region**, and **Platform Type**.
35
35
36
36
**Region** specifies where the DCR will be created. The virtual machines and their associations can be in any subscription or resource group in the tenant.
37
37
38
38
**Platform Type** specifies the type of resources this rule can apply to. Custom allows for both Windows and Linux types.
39
39
40
-
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-basics-updated.png#lightbox)
40
+
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-basics-updated.png#lightbox)
41
41
42
42
1. On the **Resources** tab, add the resources (virtual machines, virtual machine scale sets, Arc for servers) to which to associate the data collection rule. The portal will install Azure Monitor Agent on resources that don't already have it installed, and will also enable Azure Managed Identity.
43
43
@@ -46,23 +46,24 @@ To send data to Log Analytics, create the data collection rule in the **same reg
46
46
47
47
If you need network isolation using private links, select existing endpoints from the same region for the respective resources, or [create a new endpoint](../essentials/data-collection-endpoint-overview.md).
48
48
49
-
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-virtual-machines-with-endpoint.png#lightbox)
49
+
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-virtual-machines-with-endpoint.png#lightbox)
50
+
50
51
51
52
1. On the **Collect and deliver** tab, select **Add data source** to add a data source and set a destination.
52
53
1. Select a **Data source type**.
53
54
1. Select which data you want to collect. For performance counters, you can select from a predefined set of objects and their sampling rate. For events, you can select from a set of logs and severity levels.
54
55
55
-
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-data-source-basic-updated.png#lightbox)
56
+
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-data-source-basic-updated.png#lightbox)
56
57
57
58
1. Select **Custom** to collect logs and performance counters that are not [currently supported data sources](azure-monitor-agent-overview.md#data-sources-and-destinations) or to [filter events using XPath queries](#filter-events-using-xpath-queries). You can then specify an [XPath](https://www.w3schools.com/xml/xpath_syntax.asp) to collect any specific values. See [Sample DCR](data-collection-rule-sample-agent.md) for an example.
58
59
59
-
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-data-source-custom-updated.png#lightbox)
60
+
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-data-source-custom-updated.png#lightbox)
60
61
61
62
1. On the **Destination** tab, add one or more destinations for the data source. You can select multiple destinations of the same or different types - for instance multiple Log Analytics workspaces (known as "multi-homing").
62
63
63
64
You can send Windows event and Syslog data sources can to Azure Monitor Logs only. You can send performance counters to both Azure Monitor Metrics and Azure Monitor Logs.
64
65
65
-
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-destination.png#lightbox)
66
+
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-destination.png#lightbox)
66
67
67
68
1. Select **Add Data Source** and then **Review + create** to review the details of the data collection rule and association with the set of virtual machines.
68
69
1. Select **Create** to create the data collection rule.
@@ -117,7 +118,7 @@ In Windows, you can use Event Viewer to extract XPath queries as shown below.
117
118
118
119
When you paste the XPath query into the field on the **Add data source** screen, (step 5 in the picture below), you must append the log type category followed by '!'.
119
120
120
-
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-extract-xpath.png#lightbox)
121
+
[](media/data-collection-rule-azure-monitor-agent/data-collection-rule-extract-xpath.png#lightbox)
121
122
122
123
See [XPath 1.0 limitations](/windows/win32/wes/consuming-events#xpath-10-limitations) for a list of limitations in the XPath supported by Windows event log.
Copy file name to clipboardExpand all lines: articles/azure-vmware/includes/azure-vmware-solutions-limits.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,8 +24,8 @@ The following table describes the maximum limits for Azure VMware Solution.
24
24
| Azure VMware Solution ExpressRoute port speed | 10 Gbps<br />The virtual network gateway used determines the actual bandwidth. For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md)|
25
25
| Public IPs exposed via vWAN | 100 |
26
26
| vSAN capacity limits | 75% of total usable (keep 25% available for SLA) |
27
-
| VMware Site Recovery Manager - Number of protected Virtual Machines |1,000 |
28
-
| VMware Site Recovery Manager - Number of Virtual Machines per recovery plan |1,000 |
27
+
| VMware Site Recovery Manager - Number of protected Virtual Machines |3,000 |
28
+
| VMware Site Recovery Manager - Number of Virtual Machines per recovery plan |2,000 |
29
29
| VMware Site Recovery Manager - Number of protection groups per recovery plan | 250 |
30
30
| VMware Site Recovery Manager - RPO Values | 5 min or higher * |
31
31
| VMware Site Recovery Manager - Total number of virtual machines per protection group | 500 |
Copy file name to clipboardExpand all lines: articles/cosmos-db/sql/database-transactions-optimistic-concurrency.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ Optimistic concurrency control allows you to prevent lost updates and deletes. C
52
52
53
53
Every item stored in an Azure Cosmos container has a system defined `_etag` property. The value of the `_etag` is automatically generated and updated by the server every time the item is updated. `_etag` can be used with the client supplied `if-match` request header to allow the server to decide whether an item can be conditionally updated. The value of the `if-match` header matches the value of the `_etag` at the server, the item is then updated. If the value of the `if-match` request header is no longer current, the server rejects the operation with an "HTTP 412 Precondition failure" response message. The client then can re-fetch the item to acquire the current version of the item on the server or override the version of item in the server with its own `_etag` value for the item. In addition, `_etag` can be used with the `if-none-match` header to determine whether a refetch of a resource is needed.
54
54
55
-
The item’s `_etag` value changes every time the item is updated. For replace item operations, `if-match` must be explicitly expressed as a part of the request options. For an example, see the sample code in [GitHub](https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos.Samples/Usage/ItemManagement/Program.cs#L676-L772). `_etag` values are implicitly checked for all written items touched by the stored procedure. If any conflict is detected, the stored procedure will roll back the transaction and throw an exception. With this method, either all or no writes within the stored procedure are applied atomically. This is a signal to the application to reapply updates and retry the original client request.
55
+
The item’s `_etag` value changes every time the item is updated. For replace item operations, `if-match` must be explicitly expressed as a part of the request options. For an example, see the sample code in [GitHub](https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos.Samples/Usage/ItemManagement/Program.cs#L791-L887). `_etag` values are implicitly checked for all written items touched by the stored procedure. If any conflict is detected, the stored procedure will roll back the transaction and throw an exception. With this method, either all or no writes within the stored procedure are applied atomically. This is a signal to the application to reapply updates and retry the original client request.
56
56
57
57
### Optimistic concurrency control and global distribution
0 commit comments