Update screenshot, associated content - #2080
Conversation
Update screenshot, associated content and tone
|
Smriti S (@SmritiSatyan) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Jeevan Desarda (@jeevansd) |
|
Smriti S (@SmritiSatyan) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Jeevan Desarda (@jeevansd) |
|
Learn Build status updates of commit cfc885f: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Jackline Omondi (@omondiatieno) Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
This PR updates the Harness SSO tutorial content to match current UI flows and refreshes wording/tone alongside updated screenshots.
Changes:
- Updated metadata and reworked introductory/scenario wording for clarity.
- Revised the Harness-side configuration steps and screenshots to reflect the current navigation and dialogs.
- Renamed the closing section to “Next steps” and refined the My Apps / test-flow explanations.
Suppressed comments (1)
docs/identity/saas-apps/harness-tutorial.md:140
- Alt text uses spaced letters ("Add S A M L" / "U R L"), which can reduce readability for assistive tech. Use normal words/acronyms (SAML, URL) in alt text.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| 4. On the top-right of the page, select **Continuous Security** > **Access Management** > **Authentication Settings**. | ||
|
|
||
|  | ||
| 1. In **Authentication**, select **+ SAML Provider**. The **Add SAML ProvideR** page opens. Specify a name and select **Azure** as the SAML Provider. |
| ms.topic: how-to | ||
| ms.date: 03/25/2025 | ||
| ms.date: 08/26/2026 | ||
| ms.custom: sfi-image-nochange | ||
| # Customer intent: As an IT administrator, I want to learn how to configure single sign-on between Microsoft Entra ID and Harness so that I can control who has access to Harness, enable automatic sign-in with Microsoft Entra accounts, and manage my accounts in one central location. |
| 1. In **Authentication**, select **+ SAML Provider**. The **Add SAML ProvideR** page opens. Specify a name and select **Azure** as the SAML Provider. | ||
|
|
||
| 5. On the **SSO Providers** section, select **+ Add SSO Providers** > **SAML**. | ||
|  |
|  | ||
|
|
||
|  | ||
| a. Copy the URL under **Enter this SAML Endpoint URL as your Harness application's ACS URL**, and paste it in the **Reply URL** in your Azure app. |
| c. Select **Choose file** to upload the Federation Metadata XML file, which you have downloaded from Microsoft Entra ID. | ||
|
|
||
| d. Select **SUBMIT**. | ||
| c. Click **Add**. |
|  | ||
|
|
||
| a. In **Email Address(es)** text box, enter the email of user like `B.simon@contoso.com`. | ||
| a. In the **Users (name or email)** text box, enter the user's email address, as `B.simon@contoso.com`. |
| a. In the **Users (name or email)** text box, enter the user's email address, as `B.simon@contoso.com`. | ||
|
|
||
| b. Select your **User Groups**. | ||
| b. In the **User Group(s)** filed, click **Select User Group(s)**. Create a user group or select an existing user group. Click **Apply Selected**. |
Update screenshot, associated content and tone