Expand the ServusConnect tutorial

[moklett]

This expands on the original ServusConnect tutorial to add the following:

• Empasizes the eventual goal of using non-test users, in addition to an initial test user.
• Gives the full Entity ID value, which is the same for all installs.
• Describes the difference between pre-provisioned and just-in-time users.
• Provides instructions on the actual process of signing into ServusConnect, along with relevant screenshots.

[moklett]

@microsoft-github-policy-service agree company="ServusConnect"

[prmerger-automator[bot]]

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

[learn-build-service-prod[bot]]

Learn Build status updates of commit 187eee4:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	:x:Error		Details

• [Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build 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 learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@jeevansd

Can you review the proposed changes?

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

[v-hgampala]

@moklett, creating a separate PR for your changes in our private repo for better content validation, the PR will merge within 3-4 working days. #please-close