Skip to content

Commit 2ff1044

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patricka-fix-command
2 parents 31bf7b0 + 628d50f commit 2ff1044

File tree

10 files changed

+74
-21
lines changed

10 files changed

+74
-21
lines changed

articles/azure-app-configuration/quickstart-python-provider.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -64,16 +64,15 @@ The Python App Configuration provider is a library in preview running on top of
6464

6565
```python
6666
from azure.appconfiguration.provider import (
67-
AzureAppConfigurationProvider,
67+
load_provider,
6868
SettingSelector
6969
)
7070
import os
7171

7272
connection_string = os.environ.get("AZURE_APPCONFIG_CONNECTION_STRING")
7373

7474
# Connect to Azure App Configuration using a connection string.
75-
config = AzureAppConfigurationProvider.load(
76-
connection_string=connection_string)
75+
config = load_provider(connection_string=connection_string)
7776

7877
# Find the key "message" and print its value.
7978
print(config["message"])
@@ -82,15 +81,13 @@ The Python App Configuration provider is a library in preview running on top of
8281

8382
# Connect to Azure App Configuration using a connection string and trimmed key prefixes.
8483
trimmed = {"test."}
85-
config = AzureAppConfigurationProvider.load(
86-
connection_string=connection_string, trimmed_key_prefixes=trimmed)
84+
config = load_provider(connection_string=connection_string, trim_prefixes=trimmed)
8785
# From the keys with trimmed prefixes, find a key with "message" and print its value.
8886
print(config["message"])
8987

9088
# Connect to Azure App Configuration using SettingSelector.
91-
selects = {SettingSelector("message*", "\0")}
92-
config = AzureAppConfigurationProvider.load(
93-
connection_string=connection_string, selects=selects)
89+
selects = {SettingSelector(key_filter="message*", label_filter="\0")}
90+
config = load_provider(connection_string=connection_string, selects=selects)
9491

9592
# Print True or False to indicate if "message" is found in Azure App Configuration.
9693
print("message found: " + str("message" in config))

articles/azure-video-analyzer/video-analyzer-docs/includes/deprecation-notice.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,7 @@ ms.author: anilmur
77
---
88

99
> [!NOTE]
10-
> We’re retiring the Azure Video Analyzer preview service, you're advised to **transition your applications off of Video Analyzer by 01 December 2022.**
11-
>
10+
> Azure Video Analyzer has been retired and is no longer available.
11+
>
1212
> Azure Video Analyzer for Media is not affected by this retirement. It is now rebranded to Azure Video Indexer. Click [here](https://vi.microsoft.com) to read more.
13-
>
14-
> **Action Required**: To minimize disruption to your workloads, transition your application from Video Analyzer per suggestions described in this [guide](../transition-from-video-analyzer.md) before December 01, 2022. After December 1, 2022 your Azure Video Analyzer account will no longer function.
15-
> Starting May 2, 2022 you will not be able to create new Video Analyzer accounts.
13+
>

articles/cloud-shell/quickstart-powershell.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,7 @@ Register-AzResourceProvider -ProviderNamespace Microsoft.CloudShell
4949
```
5050

5151
> [!NOTE]
52-
> You only need to register the namespace once per subscription. You will not be able to manage
53-
> resources using Azure Cloud Shell without registering the namespace.
52+
> You only need to register the namespace once per subscription.
5453
5554
## Run PowerShell commands
5655

articles/cloud-shell/quickstart.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,7 @@ az provider register --namespace Microsoft.CloudShell
4343
```
4444

4545
> [!NOTE]
46-
> You only need to register the namespace once per subscription. You will not be able to manage
47-
> resources using Azure Cloud Shell without registering the namespace.
46+
> You only need to register the namespace once per subscription.
4847
4948
### Set your subscription
5049

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: How to configure user engagement tracking to an email domain with Azure Communication Service resource.
3+
titleSuffix: An Azure Communication Services quick start guide
4+
description: Learn about how to enable user engagement for the email domains with Azure Communication Services resource.
5+
author: bashan-git
6+
manager: sundraman
7+
services: azure-communication-services
8+
ms.author: bashan
9+
ms.date: 02/15/2023
10+
ms.topic: quickstart
11+
ms.service: azure-communication-services
12+
---
13+
# Quickstart: How to enable user engagement tracking for the email domain with Azure Communication Service resource
14+
15+
[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
16+
17+
Configuring email engagement enables the insights on your customers' engagement with emails to help build customer relationships. Only the emails that are sent from Azure Communication Services verified Email Domains that are enabled for user engagement analysis will get the engagement tracking metrics.
18+
19+
> [!IMPORTANT]
20+
> By enabling this feature, you are acknowledging that you are enabling open/click tracking and giving consent to collect your customers' email activity
21+
22+
In this quick start, you'll learn about how to enable user engagement tracking for verified domain in Azure Communication Services.
23+
24+
## Enable email engagement
25+
1. Go the overview page of the Email Communications Service resource that you created earlier.
26+
2. Click Provision Domains on the left navigation panel. You'll see list of provisioned domains.
27+
3. Click on the Custom Domain name that you would like to update.
28+
29+
:::image type="content" source="./media/email-domains-custom-provision-domains.png" alt-text="Screenshot that shows how to get to overview page for Domain from provisioned domains list.":::
30+
31+
4. The navigation lands in Domain Overview page where you'll able to see User interaction tracking Off by default.
32+
33+
:::image type="content" source="./media/email-domains-custom-overview.png" alt-text="Screenshot that shows the overview page of the domain." lightbox="media/email-domains-custom-overview-expanded.png":::
34+
35+
5. The navigation lands in Domain Overview page where you'll able to see User interaction tracking Off by default.
36+
37+
:::image type="content" source="./media/email-domains-user-engagement.png" alt-text="Screenshot that shows the user engagement turn-on page of the domain." lightbox="media/email-domains-user-engagement-expanded.png":::
38+
39+
6. Click turn on to enable engagement tracking.
40+
41+
**Your email domain is now ready to send emails with user engagement tracking.**
42+
43+
You can now subscribe to Email User Engagement operational logs - provides information related to 'open' and 'click' user engagement metrics for messages sent from the Email service.
44+
45+
## Next steps
46+
47+
* [Get started with log analytics in Azure Communication Service](../../concepts/logging-and-diagnostics.md)
48+
49+
50+
The following documents may be interesting to you:
51+
52+
- Familiarize yourself with the [Email client library](../../concepts/email/sdk-features.md)
53+
- [Get started by connecting Email Communication Service with a Azure Communication Service resource](../../quickstarts/email/connect-email-communication-resource.md)
20.7 KB
Loading
20.7 KB
Loading

articles/communication-services/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,9 @@ items:
5050
- name: Handle Email events
5151
href: quickstarts/email/handle-email-events.md
5252
- name: Send an Email in Azure Logic Apps
53-
href: quickstarts/email/logic-app.md
53+
href: quickstarts/email/logic-app.md
54+
- name: Enable User Engagement Tracking
55+
href: quickstarts/email/enable-user-engagement-tracking.md
5456
- name: Telephony and phone numbers
5557
items:
5658
- name: Get and manage phone numbers

articles/firewall/overview.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -181,9 +181,7 @@ Untrusted customer signed certificates|Customer signed certificates aren't trust
181181
|Certificate Propagation|After a CA certificate is applied on the firewall, it may take between 5-10 minutes for the certificate to take effect.|A fix is being investigated.|
182182
|TLS 1.3 support|TLS 1.3 is partially supported. The TLS tunnel from client to the firewall is based on TLS 1.2, and from the firewall to the external Web server is based on TLS 1.3.|Updates are being investigated.|
183183
|Availability Zones for Firewall Premium in the Southeast Asia region|You can't currently deploy Azure Firewall Premium with Availability Zones in the Southeast Asia region.|Deploy the firewall in Southeast Asia without Availability Zones, or deploy in a region that supports Availability Zones.|
184-
185-
186-
184+
|TLSi intermediate CA certificate expiration|In some unique cases, the intermediate CA certificate can expire two months before the original expiration date.|Renew the intermediate CA certificate two months before the original expiration date. A fix is being investigated.|
187185

188186
## Next steps
189187

articles/virtual-machines/availability-set-overview.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,13 @@ Only VMs with managed disks can be created in a managed availability set. The nu
3737
az vm list-skus --resource-type availabilitySets --query '[?name==`Aligned`].{Location:locationInfo[0].location, MaximumFaultDomainCount:capabilities[0].value}' -o Table
3838
```
3939

40+
Under certain circumstances, two VMs in the same availability set might share a fault domain. You can confirm a shared fault domain by going to your availability set and checking the Fault Domain column. A shared fault domain might be caused by the completing following sequence when you deployed the VMs:
41+
1. Deploy the first VM.
42+
2. Stop/deallocate the first VM.
43+
3. Deploy the second VM.
44+
45+
Under these circumstances, the OS disk of the second VM might be created on the same fault domain as the first VM, so the two VMs will be on same fault domain. To avoid this issue, we recommend that you don't stop/deallocate VMs between deployments.
46+
4047
:::image type="content" source="./media/virtual-machines-common-manage-availability/md-fd-updated.png" alt-text="Diagram showing how the fault domains for disks and VMs are aligned.":::
4148

4249
## Next steps

0 commit comments

Comments
 (0)