Sign in to Streavent with Microsoft Entra ID

Streavent is registered in Microsoft Entra ID, formerly Azure Active Directory, as an enterprise application over SAML 2.0 or OpenID Connect. Your team then signs in to the event with the same Microsoft work account it uses for Microsoft 365. Entra confirms the identity and applies your sign-in policies, and Streavent maps each account to a role that sets what it can access. Granting and removing access happens through Entra group assignment, like any other enterprise app.

Yes. Microsoft renamed Azure Active Directory to Microsoft Entra ID, and the two are the same identity service. If your organization uses Microsoft 365, you already have Entra ID, and Streavent connects to it as an enterprise application. Nothing changes about how your users sign in, they use the Microsoft account they already have.

Yes. Because sign-in runs through Entra ID, your conditional access rules, multi-factor prompts and sign-in risk policies apply to the event exactly as they do to your other applications. Streavent does not replace or bypass any of it. You keep one perimeter for the whole organization, event access included.

Yes. You assign the Streavent enterprise application to the Entra groups that should have access, and only their members can sign in. Inside Streavent, each account maps to a role, so organizers reach the admin areas while staff see only what they need. Access is added and removed through group membership, so offboarding in Entra removes event access with it.