Microsoft Entra ID

Microsoft Entra ID, formerly Azure Active Directory, is Microsoft’s identity platform for enterprise single sign-on, common at organizations already standardized on Microsoft 365. This isn’t a claims integration, Microsoft Entra ID is about how your organization runs ProPay itself as procured enterprise software: single sign-on and provisioning.

What ProPay does with Microsoft Entra ID

ProPay supports SAML-based single sign-on through Entra ID, so your team authenticates with the same Microsoft credentials used across the rest of your Microsoft 365 environment. Access changes made in Entra ID propagate to ProPay without a separate admin step.

This sits apart from ProPay’s claim-handling integrations entirely. Microsoft Entra ID doesn’t touch claim data, parts sourcing, or payment execution, it’s the layer that governs how your team accesses and monitors ProPay as a system, the same way it governs every other vendor you run Microsoft Entra ID against.

How the Microsoft Entra ID connection works

ProPay’s authentication layer accepts Entra ID as a SAML identity provider, configured during onboarding.

This is configured during enterprise onboarding rather than left to a self-serve setup, since it touches how your team authenticates or how your operations team gets alerted.

What stays in Microsoft Entra ID

Microsoft Entra ID continues to manage identity, observability, or incident routing exactly as it does for every other tool in your stack. ProPay is one more system governed by the rules you already have in Microsoft Entra ID, not a special case.

Data handling and security

ProPay is SOC 2 compliant, with both Type I and Type II audits complete, and each client runs on a company-specific instance, a property directly relevant to how access through Microsoft Entra ID is scoped, since there’s no shared environment to accidentally expose.

Every claim recommendation ProPay makes is logged with a confidence level and its supporting inputs, independent of whatever visibility Microsoft Entra ID is configured to provide, Microsoft Entra ID adds a second layer of oversight on top of an already-audited system, not a replacement for it.

Setting this up

A dedicated Forward Deployed Engineer configures the Microsoft Entra ID connection as part of enterprise onboarding, working with whoever owns identity or operations tooling on your side.

Frequently asked questions about ProPay and Microsoft Entra ID

Is Microsoft Entra ID used for claims data, like ProPay’s other integrations?

No. Microsoft Entra ID governs how your organization accesses or monitors ProPay itself; claim, parts, and payment data move through ProPay’s separate category-specific integrations.

How does ProPay connect to Microsoft Entra ID?

ProPay’s authentication layer accepts Entra ID as a SAML identity provider, configured during onboarding.

Is Microsoft Entra ID required to use ProPay?

No. Microsoft Entra ID is available for enterprise clients who want ProPay to run under their existing identity, observability, or incident management setup, it isn’t required for ProPay’s core claims functionality.