Skip to content

Commit 0d46a21

Browse files
Merge pull request #90702 from v-alje/non-breaking-space-bulk-fix
Bulk fix for Loc Non-breaking spaces aound astriscs
2 parents 679d596 + 7101844 commit 0d46a21

File tree

67 files changed

+269
-269
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

67 files changed

+269
-269
lines changed

articles/active-directory/identity-protection/faqs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: Azure Active Directory Identity Protection FAQ | Microsoft Docs
33
description: 'Frequently asked questions about Azure AD Identity Protection'
44

@@ -38,6 +38,6 @@ This article includes answers to frequently asked questions about Azure Active D
3838

3939
## How can I sort users in "Users flagged for risk"?
4040

41-
**A:** Download the users flagged for risk report by clicking **Download** on the top of the **Users flagged for risk** page. You can then sort the downloaded data based on available fields, including Last Updated (UTC).
41+
**A:** Download the users flagged for risk report by clicking **Download** on the top of the **Users flagged for risk** page. You can then sort the downloaded data based on available fields, including Last Updated (UTC).
4242

4343
---

articles/active-directory/manage-apps/application-proxy-understand-cors-issues.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: Understand and solve Azure AD Application Proxy CORS issues
33
description: Provides an understanding of CORS in Azure AD Application Proxy, and how to identify and solve CORS issues.
44
services: active-directory
@@ -47,7 +47,7 @@ In the following screenshot, selecting the **Try It** button caused a CORS error
4747

4848
## CORS challenges with Application Proxy
4949

50-
The following example shows a typical Azure AD Application Proxy CORS scenario. The internal server hosts a **CORSWebService** web API controller, and a **CORSWebClient** that calls **CORSWebService**. There's an AJAX request from **CORSWebClient** to **CORSWebService**.
50+
The following example shows a typical Azure AD Application Proxy CORS scenario. The internal server hosts a **CORSWebService** web API controller, and a **CORSWebClient** that calls **CORSWebService**. There's an AJAX request from **CORSWebClient** to **CORSWebService**.
5151

5252
![On-premises same-origin request](./media/application-proxy-understand-cors-issues/image1.png)
5353

articles/active-directory/saas-apps/arc-facilities-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with ARC Facilities | Microsoft Docs'
33
description: Learn how to configure single sign-on between Azure Active Directory and ARC Facilities.
44
services: active-directory
@@ -88,7 +88,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
8888

8989
![image](common/edit-attribute.png)
9090

91-
1. In addition to above, ARC Facilities application expects few more attributes to be passed back in SAML response. In the **User Attributes & Claims** section on the **Group Claims (Preview)** dialog, perform the following steps:
91+
1. In addition to above, ARC Facilities application expects few more attributes to be passed back in SAML response. In the **User Attributes & Claims** section on the **Group Claims (Preview)** dialog, perform the following steps:
9292

9393
a. Click the **pen** next to **Groups returned in claim**.
9494

articles/active-directory/saas-apps/cakehr-tutorial.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with CakeHR | Microsoft Docs'
33
description: Learn how to configure single sign-on between Azure Active Directory and CakeHR.
44
services: active-directory
@@ -136,11 +136,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
136136

137137
1. Open a new web browser window and sign into your CakeHR company site as an administrator.
138138

139-
2. On the top-right corner of the page, click on **Profile** and then navigate to **Settings**.
139+
2. On the top-right corner of the page, click on **Profile** and then navigate to **Settings**.
140140

141141
![CakeHR configuration](./media/cakehr-tutorial/config01.png)
142142

143-
3. From the left side of the menu bar, click on **INTEGRATIONS** > **SAML SSO** and perform the following steps:
143+
3. From the left side of the menu bar, click on **INTEGRATIONS** > **SAML SSO** and perform the following steps:
144144

145145
![CakeHR configuration](./media/cakehr-tutorial/config02.png)
146146

@@ -162,7 +162,7 @@ To enable Azure AD users to sign in to CakeHR, they must be provisioned into Cak
162162

163163
1. Sign in to CakeHR as a Security Administrator.
164164

165-
2. From the left side of the menu bar, click on **COMPANY** > **ADD**.
165+
2. From the left side of the menu bar, click on **COMPANY** > **ADD**.
166166

167167
![CakeHR configuration](./media/cakehr-tutorial/config03.png)
168168

articles/active-directory/saas-apps/cisco-webex-tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Cisco Webex Meetings | Microsoft Docs'
33
description: Learn how to configure single sign-on between Azure Active Directory and Cisco Webex Meetings.
44
services: active-directory
@@ -75,7 +75,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
7575

7676
1. In the [Azure portal](https://portal.azure.com/), on the **Cisco Webex Meetings** application integration page, find the **Manage** section and select **single sign-on**.
7777
1. On the **Select a single sign-on method** page, select **SAML**.
78-
1. On the **Set up Single Sign-On with SAML** page, you can configure the application in **IDP** initiated mode by uploading the **Service Provider metadata** file as follows:
78+
1. On the **Set up Single Sign-On with SAML** page, you can configure the application in **IDP** initiated mode by uploading the **Service Provider metadata** file as follows:
7979

8080
a. Click **Upload metadata file**.
8181

@@ -94,7 +94,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
9494

9595
b. In the **Sign on URL** textbox, type the URL using the following pattern: ` https://<customername>.my.webex.com`
9696

97-
5. Cisco Webex Meetings application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes. Click **Edit** icon to open User Attributes dialog.
97+
5. Cisco Webex Meetings application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes. Click **Edit** icon to open User Attributes dialog.
9898

9999
![image](common/edit-attribute.png)
100100

articles/active-directory/saas-apps/concur-travel-and-expense-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Concur Travel and Expense | Microsoft Docs'
33
description: Learn how to configure single sign-on between Azure Active Directory and Concur Travel and Expense.
44
services: active-directory
@@ -80,7 +80,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
8080

8181
![Edit Basic SAML Configuration](common/edit-urls.png)
8282

83-
1. On the **Basic SAML Configuration** section the application is pre-configured in **IDP** initiated mode and the necessary URLs are already pre-populated with Azure. The user needs to save the configuration by clicking the **Save** button.
83+
1. On the **Basic SAML Configuration** section the application is pre-configured in **IDP** initiated mode and the necessary URLs are already pre-populated with Azure. The user needs to save the configuration by clicking the **Save** button.
8484

8585
1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
8686

articles/active-directory/saas-apps/harness-tutorial.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Harness | Microsoft Docs'
33
description: Learn how to configure single sign-on between Azure Active Directory and Harness.
44
services: active-directory
@@ -140,11 +140,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
140140

141141
3. If you want to setup Harness manually, open a new web browser window and sign into your Harness company site as an administrator and perform the following steps:
142142

143-
4. On the top-right of the page, click on **Continuous Security** > **Access Management** > **Authentication Settings**.
143+
4. On the top-right of the page, click on **Continuous Security** > **Access Management** > **Authentication Settings**.
144144

145145
![Harness configuration](./media/harness-tutorial/configure01.png)
146146

147-
5. On the **SSO Providers** section, click on **+ Add SSO Providers** > **SAML**.
147+
5. On the **SSO Providers** section, click on **+ Add SSO Providers** > **SAML**.
148148

149149
![Harness configuration](./media/harness-tutorial/configure03.png)
150150

@@ -168,11 +168,11 @@ To enable Azure AD users to sign in to Harness, they must be provisioned into Ha
168168

169169
1. Sign in to Harness as an Administrator.
170170

171-
1. On the top-right of the page, click on **Continuous Security** > **Access Management** > **Users**.
171+
1. On the top-right of the page, click on **Continuous Security** > **Access Management** > **Users**.
172172

173173
![Harness configuration](./media/harness-tutorial/configure04.png)
174174

175-
1. On the right side of page, click on **+ Add User**.
175+
1. On the right side of page, click on **+ Add User**.
176176

177177
![Harness configuration](./media/harness-tutorial/configure05.png)
178178

articles/active-directory/saas-apps/pegasystems-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: 'Tutorial: Azure Active Directory integration with Pega Systems | Microsoft Docs'
33
description: In this tutorial, you'll learn how to configure single sign-on between Azure Active Directory and Pega Systems.
44
services: active-directory
@@ -121,7 +121,7 @@ To configure Azure AD single sign-on with Pega Systems, take these steps:
121121
> [!NOTE]
122122
> The values provided here are placeholders. You need to use the actual identifier, reply URL, sign on URL, and relay state URL. You can get the identifier and reply URL values from a Pega application, as explained later in this tutorial. To get the relay state value, contact the [Pega Systems support team](https://www.pega.com/contact-us). You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
123123

124-
6. The Pega Systems application needs the SAML assertions to be in a specific format. To get them in the correct format, you need to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the default attributes. Select the **Edit** icon to open the **User Attributes** dialog box:
124+
6. The Pega Systems application needs the SAML assertions to be in a specific format. To get them in the correct format, you need to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the default attributes. Select the **Edit** icon to open the **User Attributes** dialog box:
125125

126126
![User Attributes](common/edit-attribute.png)
127127

articles/active-directory/saas-apps/pronovos-analytics-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: 'Tutorial: Tutorial: Azure Active Directory single sign-on (SSO) integration with ProNovos Analytics | Microsoft Docs'
33
description: Learn how to configure single sign-on between Azure Active Directory and ProNovos Analytics.
44
services: active-directory
@@ -79,7 +79,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
7979

8080
![Edit Basic SAML Configuration](common/edit-urls.png)
8181

82-
1. On the **Basic SAML Configuration** section the application is pre-configured in **IDP** initiated mode and the necessary URLs are already pre-populated with Azure. The user needs to save the configuration by clicking the **Save** button.
82+
1. On the **Basic SAML Configuration** section the application is pre-configured in **IDP** initiated mode and the necessary URLs are already pre-populated with Azure. The user needs to save the configuration by clicking the **Save** button.
8383

8484
1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
8585

articles/active-directory/saas-apps/riskware-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: 'Tutorial: Azure Active Directory integration with Riskware | Microsoft Docs'
33
description: Learn how to configure single sign-on between Azure Active Directory and Riskware.
44
services: active-directory
@@ -166,7 +166,7 @@ To configure Azure AD single sign-on with Riskware, perform the following steps:
166166

167167
g. In the **XML Identity Tag Name** textbox, type attribute, which contains the unique identifier in the SAML response like NameID.
168168

169-
h. Open the downloaded **Metadata Xml** from Azure portal in notepad, copy the certificate from the Metadata file and paste it into the **Certificate** textbox
169+
h. Open the downloaded **Metadata Xml** from Azure portal in notepad, copy the certificate from the Metadata file and paste it into the **Certificate** textbox
170170

171171
i. In **Consumer URL** textbox, paste the value of **Reply URL**, which you get from the support team.
172172

0 commit comments

Comments
 (0)