Merge pull request #186323 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)

Author: huypub

articles/active-directory/authentication/tutorial-enable-sspr.md

@@ -29,6 +29,10 @@ In this tutorial you learn how to:
 > * Set up authentication methods and registration options
 > * Test the SSPR process as a user
 
+## Video tutorial
+
+You can also follow along in a related video: [How to enable and configure SSPR in Azure AD](https://www.youtube.com/embed/rA8TvhNcCvQ?azure-portal=true).
+
 ## Prerequisites
 
 To finish this tutorial, you need the following resources and privileges:

articles/active-directory/saas-apps/github-enterprise-managed-user-tutorial.md

@@ -45,10 +45,10 @@ To configure the integration of GitHub Enterprise Managed User into Azure AD, yo
 
 1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
 1. On the left navigation pane, select the **Azure Active Directory** service.
-1. Navigate to **Enterprise Applications** and then select **All Applications**.
+1. Navigate to **Enterprise Applications**.
 1. To add new application, select **New application**.
-1. In the **Add from the gallery** section, type **GitHub Enterprise Managed User** in the search box.
-1. Select **GitHub Enterprise Managed User** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
+1. Type **GitHub Enterprise Managed User** in the search box.
+1. Select **GitHub Enterprise Managed User** from results panel and then click on the **Create** button. Wait a few seconds while the app is added to your tenant.
 
 
 ## Configure and test Azure AD SSO for GitHub Enterprise Managed User
@@ -133,4 +133,4 @@ In this section, you'll take the information provided from AAD above and enter t
 
 ## Next steps
 
-GitHub Enterprise Managed User **requires** all accounts to be created through automatic user provisioning, you can find more details [here](./github-enterprise-managed-user-provisioning-tutorial.md) on how to configure automatic user provisioning.
+GitHub Enterprise Managed User **requires** all accounts to be created through automatic user provisioning, you can find more details [here](./github-enterprise-managed-user-provisioning-tutorial.md) on how to configure automatic user provisioning.

articles/applied-ai-services/metrics-advisor/includes/quickstarts/csharp.md

@@ -59,7 +59,7 @@ Build succeeded.
 If you are using an IDE other than Visual Studio you can install the Metrics Advisor client library for .NET with the following command:
 
 ```console
-dotnet add package Azure.AI.MetricsAdvisor --version 1.0.0
+dotnet add package Azure.AI.MetricsAdvisor --version 1.1.0
 ```
 
 > [!TIP]
@@ -151,64 +151,45 @@ Replace `connection_String` with your own SQL server connection string, and repl
 string sqlServerConnectionString = "<connection_String>";
 string sqlServerQuery = "<query>";
 
-var dataFeedName = "Sample data feed";
-var dataFeedSource = new SqlServerDataFeedSource(sqlServerConnectionString, sqlServerQuery);
-var dataFeedGranularity = new DataFeedGranularity(DataFeedGranularityType.Daily);
+var dataFeed = new DataFeed();
+dataFeed.Name = "Sample data feed";
 
-var dataFeedMetrics = new List<DataFeedMetric>()
-{
-    new DataFeedMetric("cost"),
-    new DataFeedMetric("revenue")
-};
-var dataFeedDimensions = new List<DataFeedDimension>()
-{
-    new DataFeedDimension("category"),
-    new DataFeedDimension("city")
-};
-var dataFeedSchema = new DataFeedSchema(dataFeedMetrics)
-{
-    DimensionColumns = dataFeedDimensions
-};
-
-var ingestionStartTime = DateTimeOffset.Parse("2020-01-01T00:00:00Z");
-var dataFeedIngestionSettings = new DataFeedIngestionSettings(ingestionStartTime);
-
-var dataFeed = new DataFeed()
-{
-    Name = dataFeedName,
-    DataSource = dataFeedSource,
-    Granularity = dataFeedGranularity,
-    Schema = dataFeedSchema,
-    IngestionSettings = dataFeedIngestionSettings,
-};
+dataFeed.DataSource = new SqlServerDataFeedSource(sqlServerConnectionString, sqlServerQuery);
+dataFeed.Granularity = new DataFeedGranularity(DataFeedGranularityType.Daily);
 
-Response<string> response = await adminClient.CreateDataFeedAsync(dataFeed);
+dataFeed.Schema = new DataFeedSchema();
+dataFeed.Schema.MetricColumns.Add(new DataFeedMetric("cost"));
+dataFeed.Schema.MetricColumns.Add(new DataFeedMetric("revenue"));
+dataFeed.Schema.DimensionColumns.Add(new DataFeedDimension("category"));
+dataFeed.Schema.DimensionColumns.Add(new DataFeedDimension("city"));
 
-string dataFeedId = response.Value;
+dataFeed.IngestionSettings = new DataFeedIngestionSettings(DateTimeOffset.Parse("2020-01-01T00:00:00Z"));
 
-Console.WriteLine($"Data feed ID: {dataFeedId}");
 
-// Note that only the ID of the data feed is known at this point. You can perform another
-// service call to GetDataFeedAsync or GetDataFeed to get more information, such as status,
-// created time, the list of administrators, or the metric IDs.
+Response<DataFeed> response = await adminClient.CreateDataFeedAsync(dataFeed);
 
-Response<DataFeed> response = await adminClient.GetDataFeedAsync(dataFeedId);
+DataFeed createdDataFeed = response.Value;
 
-DataFeed dataFeed = response.Value;
-
-Console.WriteLine($"Data feed status: {dataFeed.Status.Value}");
-Console.WriteLine($"Data feed created time: {dataFeed.CreatedTime.Value}");
+Console.WriteLine($"Data feed ID: {createdDataFeed.Id}");
+Console.WriteLine($"Data feed status: {createdDataFeed.Status.Value}");
+Console.WriteLine($"Data feed created time: {createdDataFeed.CreatedOn.Value}");
 
 Console.WriteLine($"Data feed administrators:");
-foreach (string admin in dataFeed.AdministratorEmails)
+foreach (string admin in createdDataFeed.Administrators)
 {
     Console.WriteLine($" - {admin}");
 }
 
 Console.WriteLine($"Metric IDs:");
-foreach (DataFeedMetric metric in dataFeed.Schema.MetricColumns)
+foreach (DataFeedMetric metric in createdDataFeed.Schema.MetricColumns)
 {
-    Console.WriteLine($" - {metric.MetricName}: {metric.MetricId}");
+    Console.WriteLine($" - {metric.Name}: {metric.Id}");
+}
+
+Console.WriteLine($"Dimensions:");
+foreach (DataFeedDimension dimension in createdDataFeed.Schema.DimensionColumns)
+{
+    Console.WriteLine($" - {dimension.Name}");
 }
 ```
 
@@ -254,29 +235,31 @@ Create an anomaly detection configuration to tell the service which data points
 string metricId = "<metricId>";
 string configurationName = "Sample anomaly detection configuration";
 
-var hardThresholdSuppressCondition = new SuppressCondition(1, 100);
-var hardThresholdCondition = new HardThresholdCondition(AnomalyDetectorDirection.Down, hardThresholdSuppressCondition)
+var detectionConfiguration = new AnomalyDetectionConfiguration()
 {
-    LowerBound = 5.0
+    MetricId = metricId,
+    Name = configurationName,
+    WholeSeriesDetectionConditions = new MetricWholeSeriesDetectionCondition()
 };
 
-var smartDetectionSuppressCondition = new SuppressCondition(4, 50);
-var smartDetectionCondition = new SmartDetectionCondition(10.0, AnomalyDetectorDirection.Up, smartDetectionSuppressCondition);
+var detectCondition = detectionConfiguration.WholeSeriesDetectionConditions;
 
-var detectionCondition = new MetricWholeSeriesDetectionCondition()
+var hardSuppress = new SuppressCondition(1, 100);
+detectCondition.HardThresholdCondition = new HardThresholdCondition(AnomalyDetectorDirection.Down, hardSuppress)
 {
-    HardThresholdCondition = hardThresholdCondition,
-    SmartDetectionCondition = smartDetectionCondition,
-    CrossConditionsOperator = DetectionConditionsOperator.Or
+    LowerBound = 5.0
 };
 
-var detectionConfiguration = new AnomalyDetectionConfiguration(metricId, configurationName, detectionCondition);
+var smartSuppress = new SuppressCondition(4, 50);
+detectCondition.SmartDetectionCondition = new SmartDetectionCondition(10.0, AnomalyDetectorDirection.Up, smartSuppress);
+
+detectCondition.ConditionOperator = DetectionConditionOperator.Or;
 
-Response<string> response = await adminClient.CreateDetectionConfigurationAsync(detectionConfiguration);
+Response<AnomalyDetectionConfiguration> response = await adminClient.CreateDetectionConfigurationAsync(detectionConfiguration);
 
-string detectionConfigurationId = response.Value;
+AnomalyDetectionConfiguration createdDetectionConfiguration = response.Value;
 
-Console.WriteLine($"Anomaly detection configuration ID: {detectionConfigurationId}");
+Console.WriteLine($"Anomaly detection configuration ID: {createdDetectionConfiguration.Id}");
 ```
 
 ### Create a hook
@@ -285,19 +268,16 @@ Metrics Advisor supports the `EmailNotificationHook` and `WebNotificationHook` c
 
 ```csharp
 string hookName = "Sample hook";
-var emailsToAlert = new List<string>()
-{
-    "[email protected]",
-    "[email protected]"
-};
+var emailHook = new EmailNotificationHook(hookName);
 
-var emailHook = new EmailNotificationHook(hookName, emailsToAlert);
+emailHook.EmailsToAlert.Add("[email protected]");
+emailHook.EmailsToAlert.Add("[email protected]");
 
-Response<string> response = await adminClient.CreateHookAsync(emailHook);
+Response<NotificationHook> response = await adminClient.CreateHookAsync(emailHook);
 
-string hookId = response.Value;
+NotificationHook createdHook = response.Value;
 
-Console.WriteLine($"Hook ID: {hookId}");
+Console.WriteLine($"Hook ID: {createdHook.Id}");
 ```
 
 ##  Create an alert configuration

articles/cosmos-db/how-to-configure-private-endpoints.md

@@ -689,6 +689,8 @@ The following limitations apply when you're using Private Link with an Azure Cos
 
 * A network administrator should be granted at least the `Microsoft.DocumentDB/databaseAccounts/PrivateEndpointConnectionsApproval/action` permission at the Azure Cosmos account scope to create automatically approved private endpoints.
 
+* Currently, you can't approve a rejected private endpoint connection. Instead, re-create the private endpoint to resume the private connectivity. The Cosmos DB private link service automatically approves the re-created private endpoint.
+
 ### Limitations to private DNS zone integration
 
 Unless you're using a private DNS zone group, DNS records in the private DNS zone are not removed automatically when you delete a private endpoint or you remove a region from the Azure Cosmos account. You must manually remove the DNS records before:

articles/postgresql/flexible-server/concepts-high-availability.md

@@ -68,7 +68,7 @@ For flexible servers configured with high availability, these maintenance activi
 Unplanned outages include software bugs or infrastructure component failures that impact the availability of the database. If the primary server becomes unavailable, it is detected by the monitoring system and initiates a failover process.  The process includes a few seconds of wait time to make sure it is not a false positive. The replication to the standby replica is severed and the standby replica is activated to be the primary database server. That includes the standby to recovery any residual WAL files. Once it is fully recovered, DNS for the same end point is updated with the standby server's IP address. Clients can then retry connecting to the database server using the same connection string and resume their operations. 
 
 >[!NOTE]
-> Flexible servers configured with zone-redundant high availability provide a recovery point objective (RPO) of **Zero** (no data loss.The recovery tome objective (RTO) is expected to be **less than 120s** in typical cases. However, depending on the activity in the primary database server at the time of the failover, the failover may take longer. 
+> Flexible servers configured with zone-redundant high availability provide a recovery point objective (RPO) of **Zero** (no data loss). The recovery time objective (RTO) is expected to be **less than 120s** in typical cases. However, depending on the activity in the primary database server at the time of the failover, the failover may take longer. 
 
 After the failover, while a new standby server is being provisioned, applications can still connect to the primary server and proceed with their read/write operations. Once the standby server is established, it will start recovering the logs that were generated after the failover. 
 

articles/storage/common/sas-expiration-policy.md

@@ -105,7 +105,7 @@ The SAS expiration period appears in the console output.
 
 To log the creation of a SAS that is valid over a longer interval than the SAS expiration policy recommends, first create a diagnostic setting that sends logs to an Azure Log Analytics workspace. For more information, see [Send logs to Azure Log Analytics](../blobs/monitor-blob-storage.md#send-logs-to-azure-log-analytics).
 
-Next, use an Azure Monitor log query to determine whether a SAS has expired. Create a new query in your Log Analytics workspace, add the following query text, and press **Run**.
+Next, use an Azure Monitor log query to monitor whether policy has been violated. Create a new query in your Log Analytics workspace, add the following query text, and press **Run**.
 
 ```kusto
 StorageBlobLogs | where SasExpiryStatus startswith "Policy Violated" 
@@ -116,4 +116,4 @@ StorageBlobLogs | where SasExpiryStatus startswith "Policy Violated"
 - [Grant limited access to Azure Storage resources using shared access signatures (SAS)](storage-sas-overview.md)
 - [Create a service SAS](/rest/api/storageservices/create-service-sas)
 - [Create a user delegation SAS](/rest/api/storageservices/create-user-delegation-sas)
-- [Create an account SAS](/rest/api/storageservices/create-account-sas)
+- [Create an account SAS](/rest/api/storageservices/create-account-sas)

articles/synapse-analytics/security/how-to-connect-to-workspace-from-restricted-network.md

@@ -91,7 +91,7 @@ On the **Resource** tab:
 To access the linked storage with the storage explorer in Azure Synapse Analytics Studio workspace, you must create one private endpoint. The steps for this are similar to those of step 3. 
 
 On the **Resource** tab:
-* For **Resource type**, select **Microsoft.Synapse/storageAccounts**.
+* For **Resource type**, select **Microsoft.Storage/storageAccounts**.
 * For **Resource**, select the storage account name that you created previously.
 * For **Target sub-resource**, select the endpoint type:
   * **blob** is for Azure Blob Storage.

articles/virtual-machines/linux/create-upload-centos.md

@@ -417,7 +417,7 @@ Preparing a CentOS 7 virtual machine for Azure is very similar to CentOS 6, howe
     * Use a cloud-init directive baked into the image that will do this every time the VM is created:
 
         ```console
-		echo 'DefaultEnvironment="CLOUD_CFG=/etc/cloud/cloud.cfg.d/00-azure-swap.cfg"' >> /etc/systemd/system.conf	
+        echo 'DefaultEnvironment="CLOUD_CFG=/etc/cloud/cloud.cfg.d/00-azure-swap.cfg"' >> /etc/systemd/system.conf	
         cat > /etc/cloud/cloud.cfg.d/00-azure-swap.cfg << EOF
         #cloud-config
         # Generated by Azure cloud image build
@@ -433,7 +433,7 @@ Preparing a CentOS 7 virtual machine for Azure is very similar to CentOS 6, howe
             filesystem: swap
         mounts:
           - ["ephemeral0.1", "/mnt"]
-          - ["ephemeral0.2", "none", "swap", "sw", "0", "0"]
+          - ["ephemeral0.2", "none", "swap", "sw,nofail,x-systemd.requires=cloud-init.service,x-systemd.device-timeout=2", "0", "0"]
         EOF
         ```
 
@@ -454,4 +454,4 @@ Preparing a CentOS 7 virtual machine for Azure is very similar to CentOS 6, howe
 
 ## Next steps
 
-You're now ready to use your CentOS Linux virtual hard disk to create new virtual machines in Azure. If this is the first time that you're uploading the .vhd file to Azure, see [Create a Linux VM from a custom disk](upload-vhd.md#option-1-upload-a-vhd).
+You're now ready to use your CentOS Linux virtual hard disk to create new virtual machines in Azure. If this is the first time that you're uploading the .vhd file to Azure, see [Create a Linux VM from a custom disk](upload-vhd.md#option-1-upload-a-vhd).

articles/virtual-machines/linux/suse-create-upload-vhd.md

@@ -117,6 +117,7 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (Bring Your
     * Use a cloud-init directive baked into the image that will do this every time the VM is created:
 
         ```console
+        echo 'DefaultEnvironment="CLOUD_CFG=/etc/cloud/cloud.cfg.d/00-azure-swap.cfg"' >> /etc/systemd/system.conf
         cat > /etc/cloud/cloud.cfg.d/00-azure-swap.cfg << EOF
         #cloud-config
         # Generated by Azure cloud image build
@@ -132,7 +133,7 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (Bring Your
             filesystem: swap
         mounts:
           - ["ephemeral0.1", "/mnt"]
-          - ["ephemeral0.2", "none", "swap", "sw", "0", "0"]
+          - ["ephemeral0.2", "none", "swap", "sw,nofail,x-systemd.requires=cloud-init.service,x-systemd.device-timeout=2", "0", "0"]
         EOF
         ```