Merge pull request #91070 from MicrosoftDocs/master

Merge Master to Live, 3 AM

Author: PMEds28

.openpublishing.publish.config.json

@@ -302,11 +302,16 @@
       "url": "https://github.com/Azure-Samples/cosmos-dotnet-todo-app",
       "branch": "master"
     },
-	{
+    {
       "path_to_root": "samples-cosmosdb-dotnet-v3",
       "url": "https://github.com/Azure/azure-cosmos-dotnet-v3",
       "branch": "master"
     },
+    {
+      "path_to_root": "samples-cosmosdb-dotnet-v2",
+      "url": "https://github.com/Azure/azure-cosmos-dotnet-v2",
+      "branch": "master"
+    },
     {
       "path_to_root": "samples-cosmosdb-dotnet-change-feed-processor",
       "url": "https://github.com/Azure-Samples/cosmos-dotnet-change-feed-processor",

.openpublishing.redirection.json

@@ -143,6 +143,7 @@ Pass-through Authentication handles a user sign-in request as follows:
 
    > [!NOTE]
    > If the Authentication Agent fails during the sign-in process, the whole sign-in request is dropped. There is no hand-off of sign-in requests from one Authentication Agent to another Authentication Agent on-premises. These agents only communicate with the cloud, and not with each other.
+   
 13. The Authentication Agent forwards the result back to Azure AD STS over an outbound mutually authenticated HTTPS channel over port 443. Mutual authentication uses the certificate previously issued to the Authentication Agent during registration.
 14. Azure AD STS verifies that this result correlates with the specific sign-in request on your tenant.
 15. Azure AD STS continues with the sign-in procedure as configured. For example, if the password validation was successful, the user might be challenged for Multi-Factor Authentication or redirected back to the application.

articles/active-directory/hybrid/how-to-connect-pta-security-deep-dive.md

@@ -19,28 +19,28 @@ ms.collection: M365-identity-device-management
 
 Azure Active Directory (Azure AD) supports bulk user create and delete operations, bulk invite for guests, and supports downloading lists of users, groups, and group members.
 
-## Bulk import service limits
-
-Each bulk activity to create users can run for up to one hour. This enables bulk creation of at least 50,000 users.
-
 ## Required permissions
 
 In order to bulk create users in the administration portal, you must be signed in as a Global administrator or User administrator.
 
-## To bulk import users
+## To create users in bulk
 
 1. [Sign in to your Azure AD organization](https://aad.portal.azure.com) with an account that is a User administrator in the organization.
 1. In Azure AD, select **Users** > **Bulk create**.
-1. On the **Bulk create user** page, select **Download** to receive a valid comma-separated values (CSV) file of user properties, and then add your new users.
+1. On the **Bulk create user** page, select **Download** to receive a valid comma-separated values (CSV) file of user properties, and then add add users you want to create.
 
-   ![The CSV file contains names and IDs of the users to create](./media/users-bulk-add/add-csv-file.png)
+   ![Select a local CSV file in which you list the users you want to add](./media/users-bulk-add/upload-button.png)
 
-1. When you finish editing the CSV file or if you have one of your own ready to upload, select the file under **Upload your CSV file** to be validated.
+1. Open the CSV file and add a line for each user you want to create. The only required values are **Name**, **User principal name**, **Initial password** and **Block sign in (Yes/No)**. Then save the file.
 
-   ![Select a local CSV file in which you list the users you want to add](./media/users-bulk-add/upload-button.png)
+   ![The CSV file contains names and IDs of the users to create](./media/users-bulk-add/add-csv-file.png)
+
+1. On the **Bulk create user (Preview)** page, under Upload your CSV file, browse to the file. When you select the file and click **Submit**, validation of the CSV file starts.
+1. After the file contents are validated, you’ll see **File uploaded successfully**. If there are errors, you must fix them before you can submit the job.
+1. When your file passes validation, select **Submit** to start the Azure bulk operation that imports the new users.
+1. When the import operation completes, you'll see a notification of the bulk operation job status.
 
-1. When the file contents are validated, you must fix any errors before you can start the upload job.
-1. When your file passes validation, select **Submit** to start the Azure batch job that adds the new user information. If there are errors, you can download and view the results file on the Bulk operation results page. The file contains the reason for each error.
+If there are errors, you can download and view the results file on the **Bulk operation results** page. The file contains the reason for each error.
 
 ## Check status
 
@@ -67,6 +67,10 @@ Get-AzureADUser -Filter "UserType eq 'Member'"
 
 You should see that the users that you created are listed.
 
+## Bulk import service limits
+
+Each bulk activity to create users can run for up to one hour. This enables bulk creation of at least 50,000 users.
+
 ## Next steps
 
 - [Bulk delete users](users-bulk-delete.md)