Set up Prism access

Use this guide if sign-in works but chat or connections don't, or your company requires app approval.

Check this browser

These checks run from your browser. A failed connection can mean a network restriction, browser setting, or service problem; it doesn't prove your company blocked it.

  • Prism APIChecking…
  • Sign-in and account dataChecking…
  • Live chatChecked when you open a conversation

API and sign-in availability don't confirm live chat access or account permissions. After fixing access, reload your conversation to check live chat again.

Request company approval

Microsoft app consent approves account permissions. IT may also need to approve the domains below in your firewall, proxy, or Microsoft Defender policy. Prism cannot grant that approval for your company.

Before choosing Continue with Microsoft or connecting Microsoft 365, copy the note below. Include it in Microsoft’s request justification if your organization offers that option, or send it to IT separately.

Required domains and protocols
Loading requirements…

Microsoft may use additional sign-in domains covered by your organization's Microsoft endpoint policy. Other connectors need their own provider access.

Select the request manually

Restore access

  1. Check your internet connection. Ask IT whether company browser settings, extensions, or a proxy are restricting the listed domains.
  2. Ask IT to allow HTTPS and secure WebSocket upgrades on TCP port 443 under your company's policy.
  3. If Microsoft Defender for Cloud Apps session controls apply, ask IT to review Discovered domains and the app’s User-defined domains. Microsoft’s setup instructions.
  4. Run the checks again, then reload Prism. If access still fails, share the failed domain, time, and visible error with support. Omit passwords, tokens, and private messages.
Return to Prism