Update Veza SSO tutorial for current UI and domain

[cookiedocs]

Updates the Veza SSO integration tutorial to reflect the newest UX and use correct domain references.

The current topic contains some outdated content, resulting in issues when configuring Veza SSO with Microsoft Entra ID.

1. Changed Sign-on URL from veza.com to vezacloud.com
2. Replaced both configuration screenshots:
   • settings.png: Updated to show the latest Sign-in Settings page
   • details.png: Updated with new SSO configuration dialog

Thank you for maintaining this documentation!

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit c0e311e:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/identity/saas-apps/media/veza-tutorial/details.png	✅Succeeded
docs/identity/saas-apps/media/veza-tutorial/settings.png	✅Succeeded
docs/identity/saas-apps/veza-tutorial.md	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Image File	This PR added or updated an image file(s).

[Copilot]

Pull Request Overview

This PR updates the Veza SSO integration tutorial to reflect current UI changes and corrects the domain from veza.com to vezacloud.com. The changes ensure users can successfully configure Veza SSO with Microsoft Entra ID using accurate, up-to-date information.

Key Changes:

• Updated Sign-on URL domain from veza.com to vezacloud.com
• Replaced outdated configuration screenshots with current UI representations

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[v-dirichards]

@nguhiu

Can you review the proposed changes?

Note: the following image must be updated before we can merge.

docs/identity/saas-apps/media/veza-tutorial/details.png

• The listed image obscures private info, but this method is not as useful to customers as agnostic or fictitious info. You can find new How to remove personal information in a website in the Contributor Guide.

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