Merge pull request #246706 from alexbuckgit/alexbuckgit/docutune-autopr-20230729-210233-6011453-ignore-build

[BULK] DocuTune - Fix formatting issues (part 1)

Author: prmerger-automator[bot]

articles/active-directory/app-provisioning/inbound-provisioning-api-grant-access.md

@@ -55,10 +55,11 @@ This section describes how you can assign the necessary permissions to a managed
 
       [![Screenshot of managed identity name.](media/inbound-provisioning-api-grant-access/managed-identity-name.png)](media/inbound-provisioning-api-grant-access/managed-identity-name.png#lightbox) 
 
-1. Run the following PowerShell script to assign permissions to your managed identity. 
+1. Run the following PowerShell script to assign permissions to your managed identity.
+
       ```powershell
       Install-Module Microsoft.Graph -Scope CurrentUser
-     
+
       Connect-MgGraph -Scopes "Application.Read.All","AppRoleAssignment.ReadWrite.All,RoleManagement.ReadWrite.Directory"
       Select-MgProfile Beta
       $graphApp = Get-MgServicePrincipal -Filter "AppId eq '00000003-0000-0000-c000-000000000000'"
@@ -75,7 +76,7 @@ This section describes how you can assign the necessary permissions to a managed
       $managedID = Get-MgServicePrincipal -Filter "DisplayName eq 'CSV2SCIMBulkUpload'"
       New-MgServicePrincipalAppRoleAssignment -PrincipalId $managedID.Id -ServicePrincipalId $managedID.Id -ResourceId $graphApp.Id -AppRoleId $AppRole.Id
       ```
-1. To confirm that the permission was applied, find the managed identity service principal under **Enterprise Applications** in Azure AD. Remove the **Application type** filter to see all service principals. 
+1. To confirm that the permission was applied, find the managed identity service principal under **Enterprise Applications** in Azure AD. Remove the **Application type** filter to see all service principals.
       [![Screenshot of managed identity principal.](media/inbound-provisioning-api-grant-access/managed-identity-principal.png)](media/inbound-provisioning-api-grant-access/managed-identity-principal.png#lightbox) 
 1. Click on the **Permissions** blade under **Security**. Ensure the permission is set. 
       [![Screenshot of managed identity permissions.](media/inbound-provisioning-api-grant-access/managed-identity-permissions.png)](media/inbound-provisioning-api-grant-access/managed-identity-permissions.png#lightbox) 

articles/active-directory/app-provisioning/inbound-provisioning-api-powershell.md

@@ -82,8 +82,8 @@ The PowerShell sample script published in the [Microsoft Entra ID inbound provis
      - Test-ScriptCommands.ps1 (sample usage commands)
      - UseClientCertificate.ps1 (script to generate self-signed certificate and upload it as service principal credential for use in OAuth flow)
      - `Sample1` (folder with more examples of how CSV file columns can be mapped to SCIM standard attributes. If you get different CSV files for employees, contractors, interns, you can create a separate AttributeMapping.psd1 file for each entity.)
-1. Download and install the latest version of PowerShell. 
-1. Run the command to enable execution of remote signed scripts: 
+1. Download and install the latest version of PowerShell.
+1. Run the command to enable execution of remote signed scripts:
     ```powershell
     set-executionpolicy remotesigned
     ```

articles/active-directory/app-provisioning/user-provisioning-sync-attributes-for-mapping.md

@@ -49,7 +49,7 @@ Once schema extensions are created, these extension attributes are automatically
 When you've more than 1000 service principals, you may find extensions missing in the source attribute list. If an attribute you've created doesn't automatically appear, then verify the attribute was created and add it manually to your schema. To verify it was created, use Microsoft Graph and [Graph Explorer](/graph/graph-explorer/graph-explorer-overview). To add it manually to your schema, see [Editing the list of supported attributes](customize-application-attributes.md#editing-the-list-of-supported-attributes).
 
 ### Create an extension attribute for cloud only users using Microsoft Graph
-You can extend the schema of Azure AD users using [Microsoft Graph](/graph/overview). 
+You can extend the schema of Azure AD users using [Microsoft Graph](/graph/overview).
 
 First, list the apps in your tenant to get the ID of the app you're working on. To learn more, see [List extensionProperties](/graph/api/application-list-extensionproperty).
 
@@ -67,7 +67,7 @@ Content-type: application/json
     "name": "extensionName",
     "dataType": "string",
     "targetObjects": [
-    	"User"
+      "User"
     ]
 }
 ```
@@ -89,10 +89,10 @@ GET https://graph.microsoft.com/v1.0/users/{id}?$select=displayName,extension_in
 
 
 ### Create an extension attribute on a cloud only user using PowerShell
-Create a custom extension using PowerShell and assign a value to a user. 
+Create a custom extension using PowerShell and assign a value to a user.
 
 ```
-#Connect to your Azure AD tenant   
+#Connect to your Azure AD tenant
 Connect-AzureAD
 
 #Create an application (you can instead use an existing application if you would like)
@@ -123,7 +123,7 @@ Cloud sync will automatically discover your extensions in on-premises Active Dir
 4. Select the configuration you wish to add the extension attribute and mapping.
 5. Under **Manage attributes** select **click to edit mappings**.
 6. Click **Add attribute mapping**.  The attributes will automatically be discovered.
-7. The new attributes will be available in the drop-down under **source attribute**.  
+7. The new attributes will be available in the drop-down under **source attribute**.
 8. Fill in the type of mapping you want and click **Apply**.
    [![Custom attribute mapping](media/user-provisioning-sync-attributes-for-mapping/schema-1.png)](media/user-provisioning-sync-attributes-for-mapping/schema-1.png#lightbox)
 
@@ -142,11 +142,11 @@ If users who will access the applications originate in on-premises Active Direct
 1. Open the Azure AD Connect wizard, choose Tasks, and then choose **Customize synchronization options**.
 
    ![Azure Active Directory Connect wizard Additional tasks page](./media/user-provisioning-sync-attributes-for-mapping/active-directory-connect-customize.png)
- 
-2. Sign in as an Azure AD Global Administrator. 
+
+2. Sign in as an Azure AD Global Administrator.
 
 3. On the **Optional Features** page, select **Directory extension attribute sync**.
- 
+
    ![Azure Active Directory Connect wizard Optional features page](./media/user-provisioning-sync-attributes-for-mapping/active-directory-connect-directory-extension-attribute-sync.png)
 
 4. Select the attribute(s) you want to extend to Azure AD.
@@ -156,13 +156,13 @@ If users who will access the applications originate in on-premises Active Direct
    ![Screenshot that shows the "Directory extensions" selection page](./media/user-provisioning-sync-attributes-for-mapping/active-directory-connect-directory-extensions.png)
 
 5. Finish the Azure AD Connect wizard and allow a full synchronization cycle to run. When the cycle is complete, the schema is extended and the new values are synchronized between your on-premises AD and Azure AD.
- 
+
 6. In the Azure portal, while you’re [editing user attribute mappings](customize-application-attributes.md), the **Source attribute** list will now contain the added attribute in the format `<attributename> (extension_<appID>_<attributename>)`, where appID is the identifier of a placeholder application in your tenant. Select the attribute and map it to the target application for provisioning.
 
    ![Azure Active Directory Connect wizard Directory extensions selection page](./media/user-provisioning-sync-attributes-for-mapping/attribute-mapping-extensions.png)
 
 > [!NOTE]
-> The ability to provision reference attributes from on-premises AD, such as **managedby** or **DN/DistinguishedName**, is not supported today. You can request this feature on [User Voice](https://feedback.azure.com/d365community/forum/22920db1-ad25-ec11-b6e6-000d3a4f0789). 
+> The ability to provision reference attributes from on-premises AD, such as **managedby** or **DN/DistinguishedName**, is not supported today. You can request this feature on [User Voice](https://feedback.azure.com/d365community/forum/22920db1-ad25-ec11-b6e6-000d3a4f0789).
 
 
 ## Next steps

articles/active-directory/enterprise-users/groups-settings-v2-cmdlets.md

@@ -270,7 +270,7 @@ To disable group creation for non-admin users:
 
 2. If it returns `UsersPermissionToCreateGroupsEnabled : True`, then non-admin users can create groups. To disable this feature:
 
-   ```powershell 
+   ```powershell
    Set-MsolCompanySettings -UsersPermissionToCreateGroupsEnabled $False
    ```
 

articles/active-directory/external-identities/allow-deny-list.md

@@ -104,12 +104,12 @@ If the module is not installed, or you don't have a required version, do one of
 
 - If no results are returned, run the following command to install the latest version of the AzureADPreview module:
 
-   ```powershell  
+   ```powershell
    Install-Module AzureADPreview
    ```
 - If only the AzureAD module is shown in the results, run the following commands to install the AzureADPreview module: 
 
-   ```powershell 
+   ```powershell
    Uninstall-Module AzureAD 
    Install-Module AzureADPreview 
    ```

articles/active-directory/external-identities/customers/how-to-web-app-dotnet-sign-in-sign-out.md

@@ -58,7 +58,7 @@ After installing the NuGet packages and adding necessary code for authentication
 
 1. Next, add a reference to `_LoginPartial` in the *Layout.cshtml* file, which is located in the same folder. It's recommended to place this after the `navbar-collapse` class as shown in the following snippet:
 
-	```html
+    ```html
     <div class="navbar-collapse collapse d-sm-inline-flex flex-sm-row-reverse">
         <partial name="_LoginPartial" />
     </div>

articles/active-directory/external-identities/customers/tutorial-single-page-app-react-sign-in-prepare-app.md

@@ -195,7 +195,7 @@ All parts of the app that require authentication must be wrapped in the [`MsalPr
     root.render(
         <App instance={msalInstance}/>
     );
-	```
+    ```
 
 ## Next steps
 

articles/active-directory/manage-apps/grant-admin-consent.md

@@ -184,7 +184,7 @@ In the example, the resource enterprise application is Microsoft Graph of object
 
 1. Grant the delegated permissions to the client enterprise application by running the following request.
 
-   ```http   
+   ```http
    POST https://graph.microsoft.com/v1.0/oauth2PermissionGrants
    
    Request body

articles/active-directory/manage-apps/grant-consent-single-user.md

@@ -138,7 +138,7 @@ In the example, the resource enterprise application is Microsoft Graph of object
 
 1. Grant the delegated permissions to the client enterprise application on behalf of the user by running the following request.
 
-   ```http   
+   ```http
    POST https://graph.microsoft.com/v1.0/oauth2PermissionGrants
    
    Request body