Single sign-on (SSO) means that users do not need to sign in to every application they use with separate credentials. A user logs into Entra ID once, and these credentials are used for other applications such as Sales Force, Slack, Zendesk and many others. If you're an end-user, you probably aren't too interested in information about SSO. You just want to use productivity apps without entering a password every time. And we will help you to make it happen.

Single sign-on is a next step in the evolution of the user experience with third-party applications. SSO-based authentication systems are often referred to as "modern authentication". Modern authentication and single sign-on fall into a category of computing called Identity and Access Management (IAM).

IT Partner responsibilities #

1. Check prerequisites for SSO implementation
2. Create an Enterprise application for the required service
3. Configure this application according to the requirements
4. Configure the required third-party service
5. SSO enabling and testing

Client responsibilities #

1. Coordinate Client resources and staff schedules
2. Provide a dedicated point of contact responsible for working with IT Partner
3. Coordinate any outside vendor resources and schedules
4. Provide administrative access to Microsoft 365 tenant
5. Notify users about new services
6. Review and approve engagement deliverables in a timely manner

Additional cost items not provided by this project #

1. Migration of any data to Azure, such as applications, mail, virtual machines, databases and files (can be purchased as an additional service).
2. Installation of user programs (except for the office suite) on virtual machines (this setting can be is discussed individually).
3. Workstation configuration.

Upon completion of the project, we will provide a project closeout report. This document will indicate the final project status, including acceptance criteria matching, any outstanding issues, and the final budget. If you require more extensive documentation, it can be provided for an additional fee.

Prerequisites #

1. You have administrative access to your company tenant
2. You have administrative access to the service you want to connect to Azure with SSO 2.1. This service supports SAML authentication

Plan #

The plan may vary depending on your needs.

1. Kickoff meeting
2. Collecting data required for the project
3. Connection to the client’s tenant
4. Connection to the third-party service
5. SSO configuration
6. Verification and fixing issues.

Success Criteria #

1. You have SSO enabled on Azure with the necessary application.
2. Selected users can authorize on the desired service using Entra ID credentials