Issue Summary

The audience-specific pages can be configured with Azure SSO. It looks like we've removed the field "Page access user email node" from the SAML configuration page and because of it, users are getting errors when they sign in.

Steps to Reproduce

1. Enable SSO for audience-specific pages
2. Configure SSO with Azure and map the groups
3. When you try signing in, you will get an error. 

Expected Results

It should log us in without any problem as we are sending back appropriate groups, email and group mapping is done internally

Actual Results

The below error is thrown in the UI when we try to sign in:

Uh Oh! We couldn't create a Page Access User for you! Does this user exist on a different account?

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available