Merge pull request #192871 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/active-directory/authentication/concept-sspr-writeback.md

@@ -156,6 +156,9 @@ Passwords aren't written back in any of the following situations:
 > [!WARNING]
 > Use of the checkbox "User must change password at next logon" in on-premises AD DS administrative tools like Active Directory Users and Computers or the Active Directory Administrative Center is supported as a preview feature of Azure AD Connect. For more information, see [Implement password hash synchronization with Azure AD Connect sync](../hybrid/how-to-connect-password-hash-synchronization.md).
 
+> [!NOTE]
+> If a user has the option "Password never expires" set in Active Directory (AD), the force password change flag will not be set in Active Directory (AD), so the user will not be prompted to change the password during the next sign-in even if the option to force the user to change their password on next logon option is selected during an administrator-initiated end-user password reset.
+
 ## Next steps
 
 To get started with SSPR writeback, complete the following tutorial:

articles/security/fundamentals/services-technologies.md

@@ -28,7 +28,7 @@ Over time, this list will change and grow, just as Azure does. Make sure to chec
 ## General Azure security
 |Service|Description|
 |--------|--------|
-|[Azure Security Center](../../security-center/security-center-introduction.md)| A cloud workload protection solution that provides security management and advanced threat protection across hybrid cloud workloads.|
+|[Microsoft Defender for Cloud](../../security-center/security-center-introduction.md)| A cloud workload protection solution that provides security management and advanced threat protection across hybrid cloud workloads.|
 |[Azure Key Vault](../../key-vault/general/overview.md)| A secure secrets store for the passwords, connection strings, and other information you need to keep your apps working. |
 |[Azure Monitor logs](../../azure-monitor/logs/log-query-overview.md)|A monitoring service that collects telemetry and other data, and provides a query language and analytics engine to deliver operational insights for your apps and resources. Can be used alone or with other services such as Defender for Cloud. |
 |[Azure Dev/Test Labs](../../devtest-labs/devtest-lab-overview.md)|A service that helps developers and testers quickly create environments in Azure while minimizing waste and controlling cost.  |

articles/service-fabric/service-fabric-package-apps.md

@@ -41,7 +41,7 @@ The folders are named to match the **Name** attributes of each corresponding ele
 
 Typical scenarios for using **SetupEntryPoint** are when you need to run an executable before the service starts or you need to perform an operation with elevated privileges. For example:
 
-* Setting up and initializing environment variables that the service executable needs. It is not limited to only executables written via the Service Fabric programming models. For example, npm.exe needs some environment variables configured for deploying a node.js application.
+* Setting up and initializing environment variables that the service executable needs. It is not limited to only executables written via the Service Fabric programming models. For example, npm.exe needs some environment variables configured for deploying a Node.js application.
 * Setting up access control by installing security certificates.
 
 For more information on how to configure the **SetupEntryPoint**, see [Configure the policy for a service setup entry point](service-fabric-application-runas-security.md)

articles/stream-analytics/debug-user-defined-functions.md

@@ -81,9 +81,9 @@ exports.data = methods;
   
 ## Install debug support
 
-To debug, you must [download](https://nodejs.org/en/download/) and install **node.js**. Install the correct version according to the platform you're using. After you install the node.js runtime, restart Visual Studio Code to implement the changes. 
+To debug, you must [download](https://nodejs.org/en/download/) and install **node.js**. Install the correct version according to the platform you're using. After you install the Node.js runtime, restart Visual Studio Code to implement the changes. 
 
-Select **Run and Debug** or press **CTRL + SHIFT + D** to start debugging. A combo box appears where you can select **node.js** as the runtime. If you only have node.js installed, it is used by default. You should be able to step through the code and into the satellite file if needed with F11. 
+Select **Run and Debug** or press **CTRL + SHIFT + D** to start debugging. A combo box appears where you can select **node.js** as the runtime. If you only have Node.js installed, it is used by default. You should be able to step through the code and into the satellite file if needed with F11. 
 
 > [!div class="mx-imgBorder"]
 > ![Stream Analytics run and debug udf](./media/debug-user-defined-functions/run-debug-udf.png)
@@ -116,7 +116,7 @@ exports.data = methods;
 > [!div class="mx-imgBorder"]
 > ![Code added to UDA](./media/debug-user-defined-functions/uda-expose-methods.png)
 
-Select **Run and Debug** or press **CTRL + SHIFT + D** to start debugging. A combo box appears where you can select **node.js** as the runtime. If you only have node.js installed, it is used by default. You should be able to step through the code and into the satellite file if needed with F11.
+Select **Run and Debug** or press **CTRL + SHIFT + D** to start debugging. A combo box appears where you can select **node.js** as the runtime. If you only have Node.js installed, it is used by default. You should be able to step through the code and into the satellite file if needed with F11.
 
 > [!div class="mx-imgBorder"]
 > ![Stream Analytics run and debug uda](./media/debug-user-defined-functions/run-debug-uda.png)

articles/synapse-analytics/spark/apache-spark-azure-machine-learning-tutorial.md

@@ -125,16 +125,14 @@ In Azure Machine Learning, a workspace is a class that accepts your Azure subscr
 ```python
 from azureml.core import Workspace
 
-# Enter your workspace subscription, resource group, name, and region.
+# Enter your subscription id, resource group, and workspace name.
 subscription_id = "<enter your subscription ID>" #you should be owner or contributor
 resource_group = "<enter your resource group>" #you should be owner or contributor
 workspace_name = "<enter your workspace name>" #your workspace name
-workspace_region = "<enter workspace region>" #your region
 
 ws = Workspace(workspace_name = workspace_name,
                subscription_id = subscription_id,
                resource_group = resource_group)
-
 ```
 
 ## Convert a DataFrame to an Azure Machine Learning dataset
@@ -320,11 +318,11 @@ After you've validated your best model, you can register it to Azure Machine Lea
 ```python
 description = 'My automated ML model'
 model_path='outputs/model.pkl'
-model = best_run.register_model(model_name = 'NYCGreenTaxiModel', model_path = model_path, description = description)
+model = best_run.register_model(model_name = 'NYCYellowTaxiModel', model_path = model_path, description = description)
 print(model.name, model.version)
 ```
 ```Output
-NYCGreenTaxiModel 1
+NYCYellowTaxiModel 1
 ```
 ## View results in Azure Machine Learning
 You can also access the results of the iterations by going to the experiment in your Azure Machine Learning workspace. Here, you can get additional details on the status of your run, attempted models, and other model metrics. 
@@ -333,4 +331,4 @@ You can also access the results of the iterations by going to the experiment in
 
 ## Next steps
 - [Azure Synapse Analytics](../index.yml)
-- [Tutorial: Build a machine learning app with Apache Spark MLlib and Azure Synapse Analytics](./apache-spark-machine-learning-mllib-notebook.md)
+- [Tutorial: Build a machine learning app with Apache Spark MLlib and Azure Synapse Analytics](./apache-spark-machine-learning-mllib-notebook.md)

articles/synapse-analytics/spark/apache-spark-custom-conda-channel.md

@@ -81,7 +81,7 @@ mkdir -P channel/linux64
 <Add all .tar.bz2 from https://repo.anaconda.com/pkgs/main/linux-64/> 
 // Note: Add all dependent .tar.bz2 as well 
 
-cd channel1 
+cd channel 
 mkdir noarch 
 echo '{}' > noarch/repodata.json 
 bzip2 -k noarch/repodata.json 
@@ -121,7 +121,7 @@ dependencies:
 Once you've created the sample Conda file, you can create a virtual Conda environment. You can verify this locally by running the following commands:
 
 ```
-conda env create –file sample.yml  
+conda env create --file sample.yml  
 source activate env 
 conda list 
 ```

articles/virtual-machines/linux/azure-hybrid-benefit-byos-linux.md

@@ -23,7 +23,7 @@ ms.author: mathapli
 >Azure Hybrid Benefit for BYOS VMs is planned for Preview from **30 March 2022**. You can [sign up for the preview here.](https://aka.ms/ahb-linux-form) You will receive a mail from Microsoft once your subscriptions are enabled for Preview. 
 
 
-Azure Hybrid Benefit for BYOS VMs is a licensing benefit that helps you to get software updates and integrated support for Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES) virtual machines (VMs) directly from Azure infrastructure. This benefit is available to RHEL and SLES custom on-prem image VMs (VMs generated from o- prem images), and to RHEL and SLES Marketplace bring-your-own-subscription (BYOS) VMs.
+Azure Hybrid Benefit for BYOS VMs is a licensing benefit that helps you to get software updates and integrated support for Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES) virtual machines (VMs) directly from Azure infrastructure. This benefit is available to RHEL and SLES custom on-prem image VMs (VMs generated from on-prem images), and to RHEL and SLES Marketplace bring-your-own-subscription (BYOS) VMs.
 
 ## Benefit description
 Before AHB BYOS, RHEL and SLES customers who migrated their on-prem machines to Azure by creating images of on-prem systems and migrating them as VMs on Azure did not have the flexibility to get software updates directly from Azure similar to Marketplace PAYG VMs. Hence, you needed to still buy cloud access licenses from the Enterprise Linux distributors to get security support as well as software updates. With Azure Hybrid Benefit for BYOS VMs, we will allow you to get software updates and support for on-prem custom image VMs as well as RHEL and SLES BYOS VMs similar to PAYG VMs by paying the same software fees as charged to PAYG VMs. In addition, these conversions can happen without any redeployment, so you can avoid any downtime risk.  
@@ -87,7 +87,7 @@ To start using the benefit for SUSE:
 
 1. Wait for 5 minutes for the extension to read the license type value and install the repositories. 
 
-1. You should now be connected to Azure SLES Update Infrastructure and the relevant repositories will be installed in your machine.  
+1. You should now be connected to the SUSE Public Cloud Update Infrastructure on Azure and the relevant repositories will be installed in your machine.
 
 1. In case the extension is not running by itself, you can run it on demand as well.
 
@@ -140,7 +140,7 @@ you can use the `az vm update` command to update existing license type on runnin
 ## Enable and disable the benefit for SLES
 
 You can install the `AHBForSLES` extension to install the extension. After successfully installing the extension,
-you can use the `az vm update` command to update existing license type on running VMs. For SLES VMs, run the command and set `--license-type` parameter to one of the following: `SLES_STANDARD`,`SLES_SAP` or `SLES_HPC`.
+you can use the `az vm update` command to update existing license type on running VMs. For SLES VMs, run the command and set `--license-type` parameter to one of the following: `SLES_STANDARD`, `SLES_SAP` or `SLES_HPC`.
 
 ### CLI example to enable the benefit for SLES
 1. Install the Azure Hybrid Benefit extension on running VM using the portal or via Azure CLI using the command below:
@@ -162,7 +162,7 @@ you can use the `az vm update` command to update existing license type on runnin
     ```
 1. Wait for 5 minutes for the extension to read the license type value and install the repositories. 
 
-1. You should now be connected to Azure SLES Update Infrastructure and the relevant repositories will be installed in your machine. You can check the same by  performing the command below on your VM which outputs installed repository packages on your VM:
+1. You should now be connected to the SUSE Public Cloud Update Infrastructure on Azure and the relevant repositories will be installed in your machine. You can verify this by performing the command below on your VM which list SUSE repositories on your VM:
     ```bash
     zypper repos
     ```
@@ -182,7 +182,7 @@ To check the status of Azure Hybrid Benefit for BYOS VM status
 1. You can view the Azure Hybrid Benefit status of a VM by using the Azure CLI or by using Azure Instance Metadata Service.
 
     You can use the below command for this purpose. Look for a `licenseType` field in the response. If the `licenseType` field exists and the value is one of the below, your VM has the benefit enabled:
-    `RHEL_BASE`, `RHEL_EUS`, `RHEL_BASESAPAPPS`, `RHEL_SAPHA`, `RHEL_BASESAPAPPS`, `RHEL_BASESAPHA`, `SLES_STANDARD`, `SLES_SAP`, `SLES_` 
+    `RHEL_BASE`, `RHEL_EUS`, `RHEL_BASESAPAPPS`, `RHEL_SAPHA`, `RHEL_BASESAPAPPS`, `RHEL_BASESAPHA`, `SLES_STANDARD`, `SLES_SAP`, `SLES_HPC`. 
 
     ```azurecli
     az vm get-instance-view -g MyResourceGroup -n MyVm

articles/virtual-network/virtual-networks-overview.md

@@ -75,8 +75,8 @@ Virtual networks and subnets span all availability zones in a region. You don't
 
 ## Pricing
 
-There is no charge for using Azure VNet, it is free of cost. Standard charges are applicable for resources, such as Virtual Machines (VMs) and other products. To learn more, see [VNet pricing](https://azure.microsoft.com/pricing/details/virtual-network/) and the Azure [pricing calculator](https://azure.microsoft.com/pricing/calculator/).
+There is no charge for using Azure VNet; it is free of cost. Standard charges are applicable for resources, such as Virtual Machines (VMs) and other products. To learn more, see [VNet pricing](https://azure.microsoft.com/pricing/details/virtual-network/) and the Azure [pricing calculator](https://azure.microsoft.com/pricing/calculator/).
 
 ## Next steps
- - Learn about [Azure Virtual Network concepts and best practices](concepts-and-best-practices.md) .
- - To get started using a virtual network, create one, deploy a few VMs to it, and communicate between the VMs. To learn how, see the [Create a virtual network](quick-create-portal.md) quickstart.
+ - Learn about [Azure Virtual Network concepts and best practices](concepts-and-best-practices.md).
+ - To get started using a virtual network, create one, deploy a few VMs to it, and communicate between the VMs. To learn how, see the [Create a virtual network](quick-create-portal.md) quickstart.

includes/iot-hub-get-started-note.md

@@ -6,4 +6,4 @@ ms.topic: include
 ms.date: 10/26/2018
 ---
 > [!NOTE]
-> Before you start this tutorial, complete the [Raspberry Pi online simulator](../articles/iot-hub/iot-hub-raspberry-pi-web-simulator-get-started.md) tutorial or one of the device tutorials. For example, you can go to [Raspberry Pi with node.js](../articles/iot-hub/iot-hub-raspberry-pi-kit-node-get-started.md) or to one of the [Send telemetry](../articles/iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-csharp) quickstarts. In these articles, you set up your Azure IoT device and IoT hub, and you deploy a sample application to run on your device. The application sends collected sensor data to your IoT hub.
+> Before you start this tutorial, complete the [Raspberry Pi online simulator](../articles/iot-hub/iot-hub-raspberry-pi-web-simulator-get-started.md) tutorial or one of the device tutorials. For example, you can go to [Raspberry Pi with Node.js](../articles/iot-hub/iot-hub-raspberry-pi-kit-node-get-started.md) or to one of the [Send telemetry](../articles/iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-csharp) quickstarts. In these articles, you set up your Azure IoT device and IoT hub, and you deploy a sample application to run on your device. The application sends collected sensor data to your IoT hub.