Merge pull request #116248 from v-maudel/patch-507

L223998: Escaping mock URLs

Author: PRMerger12

articles/active-directory/b2b/redemption-experience.md

@@ -41,9 +41,9 @@ As an alternative to the invitation email, you can give a guest a direct link to
 
 > [!IMPORTANT]
 > The direct link must be tenant-specific. In other words, it must include a tenant ID or verified domain so the guest can be authenticated in your tenant, where the shared app is located. A common URL like https://myapps.microsoft.com won’t work for a guest because it will redirect to their home tenant for authentication. Here are some examples of direct links with tenant context:
- > - Apps access panel: https://myapps.microsoft.com/?tenantid=<tenant id> 
- > - Apps access panel for a verified domain: https://myapps.microsoft.com/<verified domain>
- > - Azure portal: https://portal.azure.com/<tenant id>
+ > - Apps access panel: `https://myapps.microsoft.com/?tenantid=<tenant id>`
+ > - Apps access panel for a verified domain: `https://myapps.microsoft.com/<;verified domain>`
+ > - Azure portal: `https://portal.azure.com/<tenant id>`
  > - Individual app: see how to use a [direct sign-on link](../manage-apps/end-user-experiences.md#direct-sign-on-links)
 
 There are some cases where the invitation email is recommended over a direct link. If these special cases are important to your organization, we recommend that you invite users by using methods that still send the invitation email: