Merge pull request #248289 from alexbuckgit/alexbuckgit/docutune-autopr-20230815-060645-9343817-ignore-build

[BULK] DocuTune - Fix malformed links

Author: v-dirichards

articles/active-directory-b2c/enable-authentication-spa-app.md

@@ -215,7 +215,7 @@ To specify your Azure AD B2C user flows, do the following:
 
 1. Replace `B2C_1_SUSI` with your sign-in Azure AD B2C Policy name.
 1. Replace `B2C_1_EditProfile` with your edit profile Azure AD B2C policy name.
-1. Replace all instances of `contoso` with your [Azure AD B2C tenant name](./ tenant-management-read-tenant-name.md#get-your-tenant-name).
+1. Replace all instances of `contoso` with your [Azure AD B2C tenant name](./tenant-management-read-tenant-name.md#get-your-tenant-name).
 
 ## Step 7: Use the MSAL to sign in the user
 

articles/active-directory/app-provisioning/customize-application-attributes.md

@@ -348,7 +348,7 @@ Selecting this option forces a resynchronization of all users while the provisio
 - The attribute `IsSoftDeleted` is often part of the default mappings for an application. `IsSoftdeleted` can be true in one of four scenarios: 1) The user is out of scope due to being unassigned from the application. 2) The user is out of scope due to not meeting a scoping filter. 3) The user has been soft deleted in Azure AD. 4) The property `AccountEnabled` is set to false on the user. It's not recommended to remove the `IsSoftDeleted` attribute from your attribute mappings.
 - The Azure AD provisioning service doesn't support provisioning null values.
 - They primary key, typically "ID", shouldn't be included as a target attribute in your attribute mappings. 
-- The role attribute typically needs to be mapped using an expression, rather than a direct mapping. For more information about role mapping, see [Provisioning a role to a SCIM app](#Provisioning a role to a SCIM app). 
+- The role attribute typically needs to be mapped using an expression, rather than a direct mapping. For more information about role mapping, see [Provisioning a role to a SCIM app](#provisioning-a-role-to-a-scim-app). 
 - While you can disable groups from your mappings, disabling users isn't supported. 
 
 ## Next steps

articles/active-directory/develop/quickstart-v2-netcore-daemon.md

@@ -100,7 +100,7 @@ ms.custom: devx-track-csharp, aaddev, identityplatformtop40, "scenarios:getting-
 > > [!div class="sxs-lookup"]
 > ### How the sample works
 >
-> ![Diagram that shows how the sample app generated by this quickstart works.](./configure-app-multi-instancing.md netcore-daemon-intro.svg)
+> ![Diagram that shows how the sample app generated by this quickstart works.](./media/quickstart-v2-netcore-daemon/netcore-daemon-intro.svg)
 >
 > ### Microsoft.Identity.Web.GraphServiceClient
 >

articles/active-directory/develop/quickstart-web-app-python-sign-in.md

@@ -89,7 +89,7 @@ You can also use an integrated development environment to open the folder.
 
 1. Create a virtual environment for the app:
 
-    [!INCLUDE [Virtual environment setup](<../../app-service/includes/quickstart-python/virtual-environment-setup.md>)]
+    [!INCLUDE [Virtual environment setup](../../app-service/includes/quickstart-python/virtual-environment-setup.md)]
 
 1. Install the requirements using `pip`:
 

articles/active-directory/governance/entitlement-management-external-users.md

@@ -123,7 +123,7 @@ To ensure people outside of your organization can request access packages and ge
 
 ### Review your Microsoft 365 group sharing settings
 
-- If you want to include Microsoft 365 groups in your access packages for external users, make sure the **Let users add new guests to the organization** is set to **On** to allow guest access. For more information, see [Manage guest access to Microsoft 365 Groups](/Microsoft 365/admin/create-groups/manage-guest-access-in-groups?view=Microsoft 365-worldwide#manage-groups-guest-access).
+- If you want to include Microsoft 365 groups in your access packages for external users, make sure the **Let users add new guests to the organization** is set to **On** to allow guest access. For more information, see [Manage guest access to Microsoft 365 Groups](/microsoft-365/admin/create-groups/manage-guest-access-in-groups?view=microsoft-365-worldwide#manage-groups-guest-access).
 
 - If you want external users to be able to access the SharePoint Online site and resources associated with a Microsoft 365 group, make sure you turn on SharePoint Online external sharing. For more information, see [Turn external sharing on or off](/sharepoint/turn-external-sharing-on-or-off#change-the-organization-level-external-sharing-setting).
 

articles/active-directory/standards/memo-22-09-enterprise-wide-identity-management-system.md

@@ -76,7 +76,7 @@ For your application inventory, determine applications that use cloud-ready prot
   * LDAP
   * Basic authentication
 
-Learn more [Azure AD integrations with authentication protocols](../architecture/auth-sync-overview.md
+Learn more [Azure AD integrations with authentication protocols](../architecture/auth-sync-overview.md).
 
 #### Application and service discovery tools
 

articles/ai-services/document-intelligence/whats-new.md

@@ -878,7 +878,7 @@ The v3.1 API introduces new and updated capabilities:
 
 * New option `pages` supported by all document intelligence methods (custom forms and all prebuilt models). The argument allows you to select individual or a range of pages for multi-page PDF and TIFF documents. For individual pages, enter the page number, for example, `3`. For a range of pages (like page 2 and pages 5-7) enter the page numbers and ranges separated by commas: `2, 5-7`.
 
-* Added support for a **[ReadingOrder](/javascript/api/@azure/ai-form-recognizer/formreadingorder?view=azure-node-latest&preserve-view=true to the URL)** type to the content recognition methods. This option enables you to control the algorithm that the service uses to determine how recognized lines of text should be ordered. You can specify which reading order algorithm—`basic` or `natural`—should be applied to order the extraction of text elements. If not specified, the default value is `basic`.
+* Added support for a [ReadingOrder](/javascript/api/@azure/ai-form-recognizer/formreadingorder?view=azure-node-latest&preserve-view=true) type to the content recognition methods. This option enables you to control the algorithm that the service uses to determine how recognized lines of text should be ordered. You can specify which reading order algorithm—`basic` or `natural`—should be applied to order the extraction of text elements. If not specified, the default value is `basic`.
 
 * Split **FormField** type into several different interfaces. This update shouldn't cause any API compatibility issues except in certain edge cases (undefined valueType).
 

articles/ai-services/language-service/named-entity-recognition/concepts/ga-preview-mapping.md

@@ -27,7 +27,7 @@ Entity tags are used to further identify an entity where a detected entity is ta
 The changes introduce better flexibility for named entity recognition, including:
 * More granular entity recognition through introducing the tags list where an entity could be tagged by more than one entity tag.
 * Overlapping entities where entities could be recognized as more than one entity type and if so, this entity would be returned twice. If an entity was recognized to belong to two entity tags under the same entity type, both entity tags are returned in the tags list.
-* Filtering entities using entity tags, you can learn more about this by navigating to [this article](../how-to-call#select-which-entities-to-be-returned-(Preview API only).md).
+* Filtering entities using entity tags, you can learn more about this by navigating to [this article](../how-to-call.md#select-which-entities-to-be-returned-preview-api-only).
 * Metadata Objects which contain additional information about the entity but currently only act as a wrapper for the existing entity resolution feature. You can learn more about this new feature [here](entity-metadata.md).
 
 ## Generally available to preview API entity mappings

articles/ai-services/language-service/question-answering/how-to/network-isolation.md

@@ -62,5 +62,5 @@ After restricting access to an Azure AI services resource based on VNet, To brow
 - Grant access to your [local browser/machine](../../../cognitive-services-virtual-networks.md?tabs=portal#managing-ip-network-rules).
 - Add the **public IP address of the machine  under the Firewall** section of the **Networking** tab. By default `portal.azure.com` shows the current browsing machine's public IP (select this entry) and then select **Save**.
 
-     > [!div class="mx-imgBorder"]
-     > [ ![Screenshot of firewall and virtual networks configuration UI]( ../../../qnamaker/media/network-isolation/firewall.png) ](  ../../../qnamaker/media/network-isolation/firewall.png#lightbox)
+  > [!div class="mx-imgBorder"]
+  > [![Screenshot of firewall and virtual networks configuration UI](../../../qnamaker/media/network-isolation/firewall.png)](../../../qnamaker/media/network-isolation/firewall.png#lightbox)

articles/ai-services/qnamaker/How-To/network-isolation.md

@@ -32,12 +32,12 @@ Add-AzWebAppAccessRestrictionRule -ResourceGroupName "<resource group name>" -We
 3.  Verify the added access rule is present in the **Access Restrictions** section of the **Networking** tab:  
 
     > [!div class="mx-imgBorder"]
-    > [ ![Screenshot of access restriction rule]( ../media/network-isolation/access-restrictions.png) ](  ../media/network-isolation/access-restrictions.png#lightbox)
+    > [ ![Screenshot of access restriction rule](../media/network-isolation/access-restrictions.png) ](../media/network-isolation/access-restrictions.png#lightbox)
 
 4. To access the **Test pane** on the https://qnamaker.ai portal, add the **Public IP address of the machine** from where you want to access the portal. From the **Access Restrictions** page select **Add Rule**, and allow access to your client IP. 
 
     > [!div class="mx-imgBorder"]
-    > [ ![Screenshot of access restriction rule with the addition of public IP address]( ../media/network-isolation/public-address.png) ](  ../media/network-isolation/public-address.png#lightbox)
+    > [ ![Screenshot of access restriction rule with the addition of public IP address](../media/network-isolation/public-address.png) ](../media/network-isolation/public-address.png#lightbox)
 
 ### Outbound access from App Service
 
@@ -69,7 +69,7 @@ The App Service Environment (ASE) can be used to host the QnA Maker App Service
 4. Add CORS origin "*" on the App Service to allow access to https://qnamaker.ai portal Test pane. **CORS** is located under the API header in the App Service pane.
 
     > [!div class="mx-imgBorder"]
-    > [ ![Screenshot of CORS interface within App Service UI]( ../media/network-isolation/cross-orgin-resource-sharing.png) ](  ../media/network-isolation/cross-orgin-resource-sharing.png#lightbox)
+    > [ ![Screenshot of CORS interface within App Service UI](../media/network-isolation/cross-orgin-resource-sharing.png) ](../media/network-isolation/cross-orgin-resource-sharing.png#lightbox)
 
 5. Create a QnA Maker Azure AI services instance (Microsoft.CognitiveServices/accounts) using Azure Resource Manager. The QnA Maker endpoint should be set to the App Service Endpoint created above (`https:// mywebsite.myase.p.azurewebsite.net`). Here is a [sample Azure Resource Manager template you can use for reference](https://github.com/pchoudhari/QnAMakerBackupRestore/tree/master/QnAMakerASEArmTemplate).
 
@@ -89,31 +89,31 @@ The Cognitive Search instance can be isolated via a private endpoint after the Q
 2. Open the VNet resource, then under the **Subnets** tab create two subnets. One for the App Service **(appservicesubnet)** and another subnet **(searchservicesubnet)** for the Cognitive Search resource without delegation. 
 
     > [!div class="mx-imgBorder"]
-    > [ ![Screenshot of virtual networks subnets UI interface]( ../media/network-isolation/subnets.png) ](  ../media/network-isolation/subnets.png#lightbox)
+    > [ ![Screenshot of virtual networks subnets UI interface](../media/network-isolation/subnets.png) ](../media/network-isolation/subnets.png#lightbox)
 
 3. In the **Networking** tab in the Cognitive Search service instance switch endpoint connectivity data from public to private. This operation is a long running process and **can take up to 30 minutes** to complete.
 
     > [!div class="mx-imgBorder"]
-    > [ ![Screenshot of networking UI with public/private toggle button]( ../media/network-isolation/private.png) ](  ../media/network-isolation/private.png#lightbox)
+    > [ ![Screenshot of networking UI with public/private toggle button](../media/network-isolation/private.png) ](../media/network-isolation/private.png#lightbox)
 
 4. Once the Search resource is switched to private, select add **private endpoint**.
     - **Basics tab**: make sure you are creating your endpoint in the same region as search resource.
     - **Resource tab**: select the required search resource of type `Microsoft.Search/searchServices`.
 
     > [!div class="mx-imgBorder"]
-    > [ ![Screenshot of create a private endpoint UI window]( ../media/network-isolation/private-endpoint.png) ](  ../media/network-isolation/private-endpoint.png#lightbox)
+    > [ ![Screenshot of create a private endpoint UI window](../media/network-isolation/private-endpoint.png) ](../media/network-isolation/private-endpoint.png#lightbox)
 
     - **Configuration tab**:  use the VNet, subnet (searchservicesubnet) created in step 2. After that, in section **Private DNS integration** select the corresponding subscription and create a new private DNS zone called **privatelink.search.windows.net**.
 
      > [!div class="mx-imgBorder"]
-     > [ ![Screenshot of create private endpoint UI window with subnet field populated]( ../media/network-isolation/subnet.png) ](  ../media/network-isolation/subnet.png#lightbox)
+     > [ ![Screenshot of create private endpoint UI window with subnet field populated](../media/network-isolation/subnet.png) ](../media/network-isolation/subnet.png#lightbox)
 
 5. Enable VNET integration for the regular App Service. You can skip this step for ASE, as that already has access to the VNET.
 	- Go to App Service **Networking** section, and open **VNet Integration**.
 	- Link to the dedicated App Service VNet, Subnet (appservicevnet) created in step 2.
 
      > [!div class="mx-imgBorder"]
-     > [ ![Screenshot of VNET integration UI]( ../media/network-isolation/integration.png) ](  ../media/network-isolation/integration.png#lightbox)
+     > [ ![Screenshot of VNET integration UI](../media/network-isolation/integration.png) ](../media/network-isolation/integration.png#lightbox)
 
 [Create Private endpoints](../reference-private-endpoint.md) to the Azure Search resource.