Merge pull request #177355 from alexbuckgit/alexbuckgit/docutune-autopr-20211025-033632-5614060

DocuTune: Clear blank lines

Author: PRMerger19

articles/active-directory/app-provisioning/application-provisioning-config-problem-no-users-provisioned.md

@@ -22,8 +22,7 @@ After automatic provisioning has been configured for an application (including v
 -   Which users and groups have been **assigned** to the application. Note that provisioning nested groups are not supported. For more information on assignment, see [Assign a user or group to an enterprise app in Azure Active Directory](../manage-apps/assign-user-or-group-access-portal.md).
 -   Whether or not **attribute mappings** are enabled, and configured to sync valid attributes from Azure AD to the app. For more information on attribute mappings, see [Customizing User Provisioning Attribute Mappings for SaaS Applications in Azure Active Directory](customize-application-attributes.md).
 -   Whether or not there is a **scoping filter** present that is filtering users based on specific attribute values. For more information on scoping filters, see [Attribute-based application provisioning with scoping filters](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
-  
-  
+
 If you observe that users are not being provisioned, consult the [Provisioning logs (preview)](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context) in Azure AD. Search for log entries for a specific user.
 
 You can access the provisioning logs in the Azure portal by selecting **Azure Active Directory** > **Enterprise Apps** > **Provisioning logs (preview)** in the **Activity** section. You can search the provisioning data based on the name of the user or the identifier in either the source system or the target system. For details, see [Provisioning logs (preview)](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). 

articles/active-directory/app-provisioning/application-provisioning-config-problem-scim-compatibility.md

@@ -50,14 +50,14 @@ Use the following URL to update PATCH behavior and ensure SCIM compliance. The f
 - Requests to add a single-value string attribute
 - Requests to replace multiple attributes
 - Requests to remove a group member        
-                                                                                     
+
 This behavior is currently only available when using the flag, but will become the default behavior over the next few months. Note this feature flag currently does not work with on-demand provisioning. 
   * **URL (SCIM Compliant):** aadOptscim062020
   * **SCIM RFC references:** 
     * https://tools.ietf.org/html/rfc7644#section-3.5.2    
 
 Below are sample requests to help outline what the sync engine currently sends versus the requests that are sent once the feature flag is enabled. 
-                           
+
 **Requests made to disable users:**
 
 **Without feature flag**
@@ -232,41 +232,41 @@ Below are sample requests to help outline what the sync engine currently sends v
 
 
   * **Downgrade URL:** Once the new SCIM compliant behavior becomes the default on the non-gallery application, you can use the following URL to roll back to the old, non SCIM compliant behavior: AzureAdScimPatch2017
-  
+
 
 
 ## Upgrading from the older customappsso job to the SCIM job
 Following the steps below will delete your existing customappsso job and create a new scim job. 
- 
+
 1. Sign into the Azure portal at https://portal.azure.com.
 2. In the **Azure Active Directory > Enterprise Applications** section of the Azure portal, locate and select your existing SCIM application.
 3. In the **Properties** section of your existing SCIM app, copy the **Object ID**.
 4. In a new web browser window, go to https://developer.microsoft.com/graph/graph-explorer 
    and sign in as the administrator for the Azure AD tenant where your app is added.
 5. In the Graph Explorer, run the command below to locate the ID of your provisioning job. Replace "[object-id]" with the service principal ID (object ID) copied from the third step.
- 
+
    `GET https://graph.microsoft.com/beta/servicePrincipals/[object-id]/synchronization/jobs` 
 
    ![Get Jobs](media/application-provisioning-config-problem-scim-compatibility/get-jobs.PNG "Get Jobs") 
 
 
 6. In the results, copy the full "ID" string that begins with either "customappsso" or "scim".
 7. Run the command below to retrieve the attribute-mapping configuration, so you can make a backup. Use the same [object-id] as before, and replace [job-id] with the provisioning job ID copied from the last step.
- 
+
    `GET https://graph.microsoft.com/beta/servicePrincipals/[object-id]/synchronization/jobs/[job-id]/schema`
- 
+
    ![Get Schema](media/application-provisioning-config-problem-scim-compatibility/get-schema.PNG "Get Schema") 
 
 8. Copy the JSON output from the last step, and save it to a text file. The JSON contains any custom attribute-mappings that you added to your old app, and should be approximately a few thousand lines of JSON.
 9. Run the command below to delete the provisioning job:
- 
+
    `DELETE https://graph.microsoft.com/beta/servicePrincipals/[object-id]/synchronization/jobs/[job-id]`
 
 10. Run the command below to create a new provisioning job that has the latest service fixes.
 
  `POST https://graph.microsoft.com/beta/servicePrincipals/[object-id]/synchronization/jobs`
  `{   "templateId": "scim"   }`
-   
+
 11. In the results of the last step, copy the full "ID" string that begins with "scim". Optionally, reapply your old attribute-mappings by running the command below, replacing [new-job-id] with the new job ID you copied, and entering the JSON output from step #7 as the request body.
 
  `POST https://graph.microsoft.com/beta/servicePrincipals/[object-id]/synchronization/jobs/[new-job-id]/schema`
@@ -288,7 +288,7 @@ Following the steps below will delete your existing customappsso job and create
 
    `POST https://graph.microsoft.com/beta/servicePrincipals/[object-id]/synchronization/jobs`
    `{   templateId: "customappsso"   }`
- 
+
 6. Return to the first web browser window, and select the **Provisioning** tab for your application.
 7. Complete the user provisioning configuration as you normally would.
 

articles/active-directory/app-provisioning/application-provisioning-configuration-api.md

@@ -77,7 +77,7 @@ Content-type: application/json
          ],
          "publisher": "Amazon",
          "description": "Federate to a single AWS account and use SAML claims to authorize access to AWS IAM roles. If you have many AWS accounts, consider using the AWS Single Sign-On gallery application instead."    
-  
+
 }
 ```
 
@@ -242,7 +242,7 @@ Configuring provisioning requires establishing a trust between Azure AD and the
 #### Request
 ```msgraph-interactive
 PUT https://graph.microsoft.com/beta/servicePrincipals/{id}/synchronization/secrets 
- 
+
 { 
     "value": [ 
         { 

articles/active-directory/app-provisioning/application-provisioning-log-analytics.md

@@ -29,7 +29,7 @@ Once you've configured Azure monitoring, you can enable logs for application pro
 
 > [!NOTE]
 > If you have just recently provisioned a workspace, it can take some time before you can send logs to it. If you receive an error that the subscription is not registered to use *microsoft.insights* then check back after a few minutes.
- 
+
 ## Understanding the data
 The underlying data stream that Provisioning sends log viewers is almost identical. Azure Monitor logs gets nearly the same stream as the Azure portal UI and Azure API. There are only a few **differences** in the log fields as outlined in the following table. To learn more about these fields, see [List provisioningObjectSummary](/graph/api/provisioningobjectsummary-list?preserve-view=true&tabs=http&view=graph-rest-beta).
 
@@ -116,4 +116,4 @@ We're taking an open source and community-based approach to application provisio
 - [Get started with queries in Azure Monitor logs](../../azure-monitor/logs/get-started-queries.md)
 - [Create and manage alert groups in the Azure portal](../../azure-monitor/alerts/action-groups.md)
 - [Install and use the log analytics views for Azure Active Directory](../reports-monitoring/howto-install-use-log-analytics-views.md)
-- [Provisioning logs API](/graph/api/resources/provisioningobjectsummary?preserve-view=true&view=graph-rest-beta)
+- [Provisioning logs API](/graph/api/resources/provisioningobjectsummary?preserve-view=true&view=graph-rest-beta)

articles/active-directory/app-provisioning/application-provisioning-quarantine-status.md

@@ -25,7 +25,7 @@ While in quarantine:
 ## How do I know if my application is in quarantine?
 
 There are three ways to check whether an application is in quarantine:
-  
+
 - In the Azure portal, navigate to **Azure Active Directory** > **Enterprise applications** > <*application name*> > **Provisioning** and review the progress bar for a quarantine message.   
 
   ![Provisioning status bar showing quarantine status](./media/application-provisioning-quarantine-status/progress-bar-quarantined.png)
@@ -83,7 +83,7 @@ After you've resolved the issue, restart the provisioning job. Certain changes t
 - Use the Azure portal to restart the provisioning job. On the application's **Provisioning** page, select **Restart provisioning**. This action fully restarts the provisioning service, which can take some time. A full initial cycle will run again, which clears escrows, removes the app from quarantine, and clears any watermarks. The service will then evaluate all the users in the source system again and determine if they are in scope for provisioning. This can be useful when your application is currently in quarantine, as this article discusses, or you need to make a change to your attribute mappings. Note that the initial cycle takes longer to complete than the typical incremental cycle due to the number of objects that need to be evaluated. You can learn more about the performance of initial and incremental cycles [here](application-provisioning-when-will-provisioning-finish-specific-user.md).
 
 - Use Microsoft Graph to [restart the provisioning job](/graph/api/synchronization-synchronizationjob-restart?tabs=http&view=graph-rest-beta&preserve-view=true). You'll have full control over what you restart. You can choose to clear escrows (to restart the escrow counter that accrues toward quarantine status), clear quarantine (to remove the application from quarantine), or clear watermarks. Use the following request:
- 
+
 ```microsoft-graph
         POST /servicePrincipals/{id}/synchronization/jobs/{jobId}/restart
 ```

articles/dotnet-develop-multitenant-applications.md

@@ -37,7 +37,7 @@ A properly implemented multitenant application provides the following benefits t
 * **Costs**: Costs are lower than running a dedicated, single-tenant application because multi-tenancy enables the sharing of resources.
 * **Customizability**. The ability to customize the application for an individual tenant in various ways such as adding or removing features, changing colors and logos, or even adding their own code or script.
 
-In short, while there are many considerations that you must take into account to provide a highly scalable service, there are also a number of  goals and requirements that are common to many multitenant applications. Some may not be relevant in specific scenarios, and the importance of individual goals and requirements will differ in each scenario. As a provider of the multitenant application, you will also have goals and requirements such as, meeting the tenant's goals and requirements, profitability, billing, multiple service levels, provisioning, maintainability monitoring, and automation.
+In short, while there are many considerations that you must take into account to provide a highly scalable service, there are also multiple goals and requirements that are common to many multitenant applications. Some may not be relevant in specific scenarios, and the importance of individual goals and requirements will differ in each scenario. As a provider of the multitenant application, you'll also have goals and requirements, such as meeting the tenant's needs, profitability, billing, multiple service levels, provisioning, maintainability monitoring, and automation.
 
 For more information on additional design considerations of a multitenant application, see [Hosting a Multi-Tenant Application on Azure][Hosting a Multi-Tenant Application on Azure]. For information on common data architecture patterns of multi-tenant software-as-a-service (SaaS) database applications, see [Design Patterns for Multi-tenant SaaS Applications with Azure SQL Database](./azure-sql/database/saas-tenancy-app-design-patterns.md). 
 
@@ -58,7 +58,7 @@ Data management such as Azure SQL Database or Azure Storage services such as the
 * Securing Multitenant Data in SQL Database per-tenant SQL Server logins.
 * Using Azure Tables for Application Resources by specifying a container level access policy, you can have the ability to adjust permissions without having to issue new URL's for the resources protected with shared access signatures.
 * Azure Queues for Application Resources Azure queues are commonly used to drive processing on behalf of tenants, but may also be used to distribute work required for provisioning or management.
-* Service Bus Queues for Application Resources that pushes work to a shared a service, you can use a single queue where each tenant sender only has permissions (as derived from claims issued from ACS) to push to that queue, while only the receivers from the service have permission to pull from the queue the data coming from multiple tenants.
+* Service Bus Queues for Application Resources that pushes work to a shared service, you can use a single queue where each tenant sender only has permissions (as derived from claims issued from ACS) to push to that queue, while only the receivers from the service have permission to pull from the queue the data coming from multiple tenants.
 
 **Connection and Security Services**
 
@@ -80,7 +80,7 @@ Azure provides a number of ways to provision new tenants for the application. Fo
 * Worker roles allow you to provision and de-provision per tenant resources (such as when a new tenant signs-up or cancels), collect metrics for metering use, and manage scale following a certain schedule or in response to the crossing of thresholds of key performance indicators. This same role may also be used to push out updates and upgrades to the solution.
 * Azure Blobs can be used to provision compute or pre-initialized storage resources for new tenants while providing container level access policies to protect the compute service Packages, VHD images and other resources.
 * Options for provisioning SQL Database resources for a tenant include:
-  
+
   * DDL in scripts or embedded as resources within assemblies.
   * SQL Server 2008 R2 DAC Packages deployed programmatically.
   * Copying from a master reference database.
@@ -89,4 +89,4 @@ Azure provides a number of ways to provision new tenants for the application. Fo
 <!--links-->
 
 [Hosting a Multi-Tenant Application on Azure]: /previous-versions/msp-n-p/hh534480(v=pandp.10)
-[Designing Multitenant Applications on Azure]: https://msdn.microsoft.com/library/windowsazure/hh689716
+[Designing Multitenant Applications on Azure]: https://msdn.microsoft.com/library/windowsazure/hh689716

articles/vs-azure-tools-storage-explorer-files.md

@@ -68,7 +68,7 @@ The following steps illustrate how to view the contents of a file share within S
     ![Open share](media/vs-azure-tools-storage-explorer-files/image4.png)
 
 1. The main pane will display the file share's contents.
-    
+
     ![Screenshot of the main pane for a file share in Storage Explorer showing the contents of the share.](media/vs-azure-tools-storage-explorer-files/image5.png)
 
 ## Delete a file share
@@ -88,7 +88,7 @@ The following steps illustrate how to delete a file share within Storage Explore
     ![Delete](media/vs-azure-tools-storage-explorer-files/image6.png)
 
 1. Select **Yes** to the confirmation dialog.
-    
+
     ![Confirmation dialog](media/vs-azure-tools-storage-explorer-files/image7.png)
 
 ## Copy a file share
@@ -134,7 +134,7 @@ The following steps illustrate how to create a SAS for a file share:+
 1. When you're finished specifying the SAS options, select **Create**.
 
 1. A second **Shared Access Signature** dialog will then display that lists the file share along with the URL and QueryStrings you can use to access the storage resource. Select **Copy** next to the URL you wish to copy to the clipboard.
-    
+
     ![Second SAS dialog](media/vs-azure-tools-storage-explorer-files/image12.png)
 
 1. When done, select **Close**.
@@ -154,21 +154,21 @@ The following steps illustrate how to manage (add and remove) access policies fo
     ![Manage access policies context menu](media/vs-azure-tools-storage-explorer-files/image13.png)
 
 1. The **Access Policies** dialog will list any access policies already created for the selected file share.
-    
+
     ![Access Policies](media/vs-azure-tools-storage-explorer-files/image14.png)
 
 1. Follow these steps depending on the access policy management task:
-    
+
     - **Add a new access policy** - Select **Add**. Once generated, the **Access Policies** dialog will display the newly added access policy (with default settings).
 
     - **Edit an access policy** - Make any desired edits, and select **Save**.
 
     - **Remove an access policy** - Select **Remove** next to the access policy you wish to remove.
 
 1. Create a new SAS URL using the Access Policy you created earlier:
-    
+
     ![Get SAS](media/vs-azure-tools-storage-explorer-files/image15.png)
-    
+
     ![SAS name and properties](media/vs-azure-tools-storage-explorer-files/image16.png)
 
 ## Managing files in a file share
@@ -198,15 +198,15 @@ The following steps illustrate how to manage the files (and folders) within a fi
         a.  On the main pane's toolbar, select **Upload**, and then **Upload Files** from the drop-down menu.
 
         ![Upload files](media/vs-azure-tools-storage-explorer-files/image18.png)
-        
+
         b. In the **Upload files** dialog, select the ellipsis (**…**) button on the right side of the **Files** text box to select the file(s) you wish to upload.
 
         ![Adding files](media/vs-azure-tools-storage-explorer-files/image19.png)
 
         c. Select **Upload**.
 
     - **Upload a folder to a file share**
-        
+
         a. On the main pane's toolbar, select **Upload**, and then **Upload Folder** from the drop-down menu.
 
         ![Upload folder menu](media/vs-azure-tools-storage-explorer-files/image20.png)
@@ -218,21 +218,21 @@ The following steps illustrate how to manage the files (and folders) within a fi
         d. Select **Upload**.
 
     - **Download a file to your local computer**
-        
+
         a. Select the file you wish to download.
-        
+
         b. On the main pane's toolbar, select **Download**.
-        
+
         c. In the **Specify where to save the downloaded file** dialog, specify the location where you want the file downloaded, and the name you wish to give it.
 
         d. Select **Save**.
 
     - **Open a file on your local computer**
-        
+
         a.  Select the file you wish to open.
-        
+
         b.  On the main pane's toolbar, select **Open**.
-        
+
         c.  The file will be downloaded and opened using the application associated with the file's underlying file type.
 
     - **Copy a file to the clipboard**

articles/vs-azure-tools-storage-manage-with-storage-explorer.md

@@ -120,7 +120,7 @@ Storage Explorer lets you connect to individual resources, such as an Azure Data
 | File shares      | No       | No                   | Yes (URL)                      | No                 |
 | Queues           | Yes      | No                   | Yes (URL)                      | No                 |
 | Tables           | No       | No                   | Yes (URL)                      | No                 |
- 
+
 Storage Explorer can also connect to a [local storage emulator](#local-storage-emulator) using the emulator's configured ports.
 
 To connect to an individual resource, select the **Connect** button in the left-hand toolbar. Then follow the instructions for the resource type you want to connect to.
@@ -142,7 +142,7 @@ Storage Explorer can use your Azure account to connect to the following resource
 * Azure Data Lake Storage Gen2 containers
 * Azure Data Lake Storage Gen2 directories
 * Queues
- 
+
 Azure AD is the preferred option if you have data layer access to your resource but no management layer access.
 
 1. Sign in to at least one Azure account using the [steps described above](#sign-in-to-azure).