Update keylight-tutorial.md

[ryelowNavex]

The purpose of this update is to reflect a branding change from Lockpath/Keylight to NAVEX IRM to make it easier for users to ensure they are reading the right documentation.

[ghost]

All CLA requirements met.

[PRMerger15]

@ryelowNavex : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[jborsecnik]

@jeevansd,

Can you review the proposed changes?

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

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

[ryelowNavex]

Hello @jeevansd,

I'm hoping to get this pull request reviewed as soon as possible. We have customers that have requested this change because Lockpath/Keylight is no longer the name of the organization. It is now NAVEX IRM. We are trying to avoid confusion for anyone who looks to this documentation for help using our platform.

Thank you,

Ryan Logan Product Analyst NAVEX

[fisher1916]

@jeevansd - As @ryelowNavex mentioned, it is important for us at NAVEX to update this documentation to accurately reflect our current product. Please review the changes proposed, and sign off as soon as possible.

Thank you, Erica Fisher Sr. Product Analyst @ NAVEX

[Jak-MS]

@CelesteDG - can you take a look? thanks!

#assign: @CelesteDG

[ryelowNavex]

Hello @jeevansd,

I'm hoping to get this pull request reviewed as soon as possible. We have customers that have requested this change because Lockpath/Keylight is no longer the name of the organization. It is now NAVEX IRM. We are trying to avoid confusion for anyone who looks to this documentation for help using our platform.

Thank you,

Ryan Logan Product Analyst NAVEX

[ryelowNavex]

Hello @CelesteDG ,

I'm hoping to get this pull request reviewed as soon as possible. We have customers that have requested this change because Lockpath/Keylight is no longer the name of the organization. It is now NAVEX IRM. We are trying to avoid confusion for anyone who looks to this documentation for help using our platform.

Thank you,

Ryan Logan Product Analyst NAVEX

[ryelowNavex]

Hello @CelesteDG ,

I'm hoping to get this pull request reviewed as soon as possible. We have customers that have requested this change because Lockpath/Keylight is no longer the name of the organization. It is now NAVEX IRM. We are trying to avoid confusion for anyone who looks to this documentation for help using our platform.

Thank you,

Ryan Logan Product Analyst NAVEX

[CelesteDG]

@ryelowNavex - Hello and apologies for the delay. I've been on vacation most of August and just got back. I'm running the changes by our SaaS apps team to sync with any changes on their end. Thanks for your continued patience.

[v-hgampala]

@ryelowNavex, Thanks for creating this pull request!

I could see the screenshots in the document are still having from Lockpath, will you please share the latest images to update in the document?

Please open the PR again., it was in closed state.

[Jak-MS]

@v-hgampala - reopened the PR.

fyi, @CelesteDG

[cmcclister]

Docs Build status updates of commit 1cc2a1d:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/active-directory/saas-apps/keylight-tutorial.md	:warning:Warning		Details

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

• Line 57, Column 6: [Warning: bookmark-not-found] Cannot find bookmark '#configure-lockpath-keylight-sso' in 'articles/active-directory/saas-apps/keylight-tutorial.md'.
• Line 58, Column 10: [Warning: bookmark-not-found] Cannot find bookmark '#create-lockpath-keylight-test-user' in 'articles/active-directory/saas-apps/keylight-tutorial.md'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[ryelowNavex]

@v-hgampala I will get you the updated screenshots as soon as possible. Thank you.

[prmerger-automator[bot]]

@ryelowNavex : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[prmerger-automator[bot]]

@ryelowNavex : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[ryelowNavex]

@v-hgampala I uploaded the files on this pull request. Let me know when you can get the changes approved. Thanks

[cmcclister]

Docs Build status updates of commit 5858373:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/active-directory/saas-apps/keylight-tutorial.md	:warning:Warning		Details

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

• Line 57, Column 6: [Warning: bookmark-not-found] Cannot find bookmark '#configure-lockpath-keylight-sso' in 'articles/active-directory/saas-apps/keylight-tutorial.md'.
• Line 58, Column 10: [Warning: bookmark-not-found] Cannot find bookmark '#create-lockpath-keylight-test-user' in 'articles/active-directory/saas-apps/keylight-tutorial.md'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[cmcclister]

Docs Build status updates of commit 9094084:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/active-directory/saas-apps/keylight-tutorial.md	:warning:Warning		Details
articles/active-directory/saas-apps/common/Navex1.png	:white_check_mark:Succeeded
articles/active-directory/saas-apps/common/Navex2.png	:white_check_mark:Succeeded
articles/active-directory/saas-apps/common/Navex3.png	:white_check_mark:Succeeded
articles/active-directory/saas-apps/common/Navex4.png	:white_check_mark:Succeeded

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

• Line 57, Column 6: [Warning: bookmark-not-found] Cannot find bookmark '#configure-lockpath-keylight-sso' in 'articles/active-directory/saas-apps/keylight-tutorial.md'.
• Line 58, Column 10: [Warning: bookmark-not-found] Cannot find bookmark '#create-lockpath-keylight-test-user' in 'articles/active-directory/saas-apps/keylight-tutorial.md'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[v-hgampala]

@ryelowNavex, we created a separate PR for these changes in our private repo, the changes will commit into the main article within 24 hours. #please-close

[ryelowNavex]

@v-hgampala Thank you for doing this. Please make sure to change the name of the .md file from keylight-tutorial to Navex IRM (keylight/lockpath)-tutorial

[ryelowNavex]

@v-hgampala Also, I just noticed that the navigation window to the left when viewing the documentation lists this documentation under L-M, it should be under N-O. The goal is for this documentation to be searchable when the user enters "Navex" Link to the exact location below:

https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/tutorial-list