Skip to content

Update screenshot, associated content - #2080

Open
Smriti S (SmritiSatyan) wants to merge 1 commit into
MicrosoftDocs:mainfrom
SmritiSatyan:SmritiSatyan-patch-2
Open

Update screenshot, associated content#2080
Smriti S (SmritiSatyan) wants to merge 1 commit into
MicrosoftDocs:mainfrom
SmritiSatyan:SmritiSatyan-patch-2

Conversation

@SmritiSatyan

Copy link
Copy Markdown
Contributor

Update screenshot, associated content and tone

Update screenshot, associated content and tone
@prmerger-automator

Copy link
Copy Markdown
Contributor

Smriti S (@SmritiSatyan) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Jeevan Desarda (@jeevansd)

@prmerger-automator

Copy link
Copy Markdown
Contributor

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-service-prod

Copy link
Copy Markdown
Contributor

@prmerger-automator

Copy link
Copy Markdown
Contributor

PRMerger Results

Issue Description
Added File(s) This PR contains added files. New files require human review.
File Change Percent This PR contains file(s) with more than 30% file change.
Image File This PR added or updated an image file(s).

@v-dirichards

Copy link
Copy Markdown
Contributor

Jackline Omondi (@omondiatieno)

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
    ![Screenshot that shows the "Add S A M L Provider" pop-up with the "SAML Endpoint U R L" field highlighted.](./media/harness-tutorial/endpoint-url.png)

💡 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**.

![Screenshot that shows the "Continuous Security" menu with "Access Management" and "Authentication Settings" selected.](./media/harness-tutorial/authentication.png)
1. In **Authentication**, select **+ SAML Provider**. The **Add SAML ProvideR** page opens. Specify a name and select **Azure** as the SAML Provider.
Comment on lines 4 to 7
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**.
![Screenshot that shows the "Azure" as the selected "S A M L Provider".](./media/harness-tutorial/providers.png)
![Screenshot that shows the "Add S A M L Provider" pop-up with the "SAML Endpoint U R L" field highlighted.](./media/harness-tutorial/endpoint-url.png)

![Screenshot that shows the "S A M L Provider" pop-up with the "U R L" and "Display Name" fields highlighted, and the "Choose File" and "Submit" buttons selected.](./media/harness-tutorial/file.png)
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**.
![Harness configuration](./media/harness-tutorial/configure.png)

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**.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants