End-to-End Call Flow

Below is the end-to-end call flow process by which third-party users first engage with your Evolve business solutions.


  1. The external user enters the Portal URL they received in email into the browser.


  2. The Portal UI directs them to Azure AD B2C for authentication.


  3. Azure AD B2C displays the Login/Sign-up screen.


  4. The user enters their details and logs in.


  5. Azure AD B2C validates the external user login details and generates a token.


  6. With the token, Azure AD B2C directs the user to the Portal UI.


  7. The Portal UI raises a request to the Portal service to get the relay connection information with the B2C token in the header.


  8. The Portal service validates the token and returns the connection information to the Portal UI.


  9. The Portal UI calls the Azure relay service to create a connection, using the information returned by the Portal service.


  10. The Azure relay service relays the message to the relay worker who is connected using the hybrid connection.


  11. The relay worker sends the request to Evolve to validate the user. If validated, the user is given permissions.


  12. The Portal UI receives the response that the user is validated and logs in the user.


  13. All subsequent requests from the Portal UI go directly to the Azure relay service. (This works on an ongoing basis because the connection has been established.)


  14. The Azure relay service relays the request to the relay worker. The relay worker sends the request to Evolve. Evolve returns the response to the relay worker – which in turn sends it to the browser.