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/azure-arc/data/deploy-automatic-active-directory-connector.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,17 +27,13 @@ Before you proceed, you must have:
27
27
28
28
The AD domain service account should have sufficient permissions to create users, groups, and machine accounts automatically inside the provided organizational unit (OU) in the active directory.
29
29
30
+
30
31
The sufficient permission including the following:
- Fix [Hide the IDMS dependency from dependency tracker.](https://github.com/microsoft/ApplicationInsights-SnapshotCollector/issues/17)
24
+
- Fix [ArgumentException: telemetryProcessorTypedoes not implement ITelemetryProcessor.](https://github.com/microsoft/ApplicationInsights-SnapshotCollector/issues/19)
25
+
<br>Snapshot Collector used via SDK is not supported when Interop feature is enabled. [See more not supported scenarios.](https://docs.microsoft.com/azure/azure-monitor/app/snapshot-debugger-troubleshoot#not-supported-scenarios)
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/faq-smb.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.workload: storage
6
6
ms.topic: conceptual
7
7
author: b-hchen
8
8
ms.author: anfdocs
9
-
ms.date: 03/31/2022
9
+
ms.date: 04/06/2022
10
10
---
11
11
# SMB FAQs for Azure NetApp Files
12
12
@@ -67,6 +67,14 @@ No. However, you can create a new SMB volume with the new share name from a snap
67
67
68
68
Alternatively, you can use [Windows Server DFS Namespace](/windows-server/storage/dfs-namespaces/dfs-overview) where a DFS Namespace with the new share name can point to the Azure NetApp Files SMB volume with the old share name.
69
69
70
+
## Does Azure NetApp Files support SMB change notification and file locking?
71
+
72
+
Yes.
73
+
74
+
Azure NetApp Files supports [`CHANGE_NOTIFY` response](/openspecs/windows_protocols/ms-smb2/14f9d050-27b2-49df-b009-54e08e8bf7b5). This response is for the client’s request that comes in the form of a [`CHANGE_NOTIFY` request](/openspecs/windows_protocols/ms-smb2/598f395a-e7a2-4cc8-afb3-ccb30dd2df7c).
75
+
76
+
Azure NetApp Files also supports [`LOCK` response](/openspecs/windows_protocols/ms-smb2/e215700a-102c-450a-a598-7ec2a99cd82c). This response is for the client’s request that comes in the form of a [`LOCK` request](/openspecs/windows_protocols/ms-smb2/6178b960-48b6-4999-b589-669f88e9017d).
77
+
70
78
## Next steps
71
79
72
80
-[FAQs about SMB performance for Azure NetApp Files](azure-netapp-files-smb-performance.md)
Copy file name to clipboardExpand all lines: articles/cdn/cdn-create-new-endpoint.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ author: duongau
5
5
ms.assetid: 4ca51224-5423-419b-98cf-89860ef516d2
6
6
ms.service: azure-cdn
7
7
ms.topic: quickstart
8
-
ms.date: 04/30/2020
8
+
ms.date: 04/06/2022
9
9
ms.author: duau
10
10
ms.custom: mvc, mode-other
11
11
---
12
12
# Quickstart: Create an Azure CDN profile and endpoint
13
13
14
-
In this quickstart, you enable Azure Content Delivery Network (CDN) by creating a new CDN profile, which is a collection of one or more CDN endpoints. After you have created a profile and an endpoint, you can start delivering content to your customers.
14
+
In this quickstart, you enable Azure Content Delivery Network (CDN) by creating a new CDN profile, which is a collection of one or more CDN endpoints. After you've created a profile and an endpoint, you can start delivering content to your customers.
15
15
16
16
## Prerequisites
17
17
@@ -58,15 +58,15 @@ After you've created a CDN profile, you use it to create an endpoint.
58
58
The time it takes for the endpoint to propagate depends on the pricing tier selected when you created the profile. **Standard Akamai** usually completes within one minute, **Standard Microsoft** in 10 minutes, and **Standard Verizon** and **Premium Verizon** in up to 30 minutes.
59
59
60
60
> [!NOTE]
61
-
> For *Verizon CDN endpoints*, when an endpoint is **disabled** or **stopped** for any reason, all resources configured through the Verizon supplemental portal will be cleaned up. These configurations can't be restored automatically by restarting the endpoint. You will need to make those configuration changes again.
61
+
> For *Verizon CDN endpoints*, when an endpoint is **disabled** or **stopped** for any reason, all resources configured through the Verizon supplemental portal will be cleaned up. These configurations can't be restored automatically by restarting the endpoint. You will need to make the configuration change again.
62
62
63
63
## Clean up resources
64
64
65
65
In the preceding steps, you created a CDN profile and an endpoint in a resource group. Save these resources if you want to go to [Next steps](#next-steps) and learn how to add a custom domain to your endpoint. However, if you don't expect to use these resources in the future, you can delete them by deleting the resource group, thus avoiding additional charges:
66
66
67
67
1. From the left-hand menu in the Azure portal, select **Resource groups** and then select **CDNQuickstart-rg**.
68
68
69
-
2. On the **Resource group** page, select **Delete resource group**, enter *CDNQuickstart-rg* in the text box, then select **Delete**. This action delete the resource group, profile, and endpoint that you created in this quickstart.
69
+
2. On the **Resource group** page, select **Delete resource group**, enter *CDNQuickstart-rg* in the text box, then select **Delete**. This action deletes the resource group, profile, and endpoint that you created in this quickstart.
Copy file name to clipboardExpand all lines: articles/event-grid/onboard-partner.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
@@ -31,7 +31,7 @@ For step #5, you should decide what kind of user experience you want to provide.
31
31
This article shows you how to **onboard as an Azure Event Grid partner** using the **Azure portal**.
32
32
33
33
## Communicate your interest in becoming a partner
34
-
Fill out [this form](https://aka.ms/gridpartnerform) and contact the Event Grid team at [[email protected]](mailto:[email protected]). We'll have a conversation with you providing detailed information on Partner Events’ use cases, personas, onboarding process, functionality, pricing, and more.
34
+
Contact the Event Grid team at [[email protected]](mailto:[email protected]) communicating your interest in becoming a partner. We'll have a conversation with you providing detailed information on Partner Events’ use cases, personas, onboarding process, functionality, pricing, and more.
35
35
36
36
## Prerequisites
37
37
To complete the remaining steps, make sure you have:
0 commit comments