BENCHMARK
CASE STUDY
SOLUTION
PARTNER SOLUTION

Risk Query

With Microsoft ending support for Dynamics 365 Fraud Protection in 2026, Risk Query enables seamless fraud signal sharing between Akamai APR and Azure B2C to maintain enterprise security continuity.

Summary

With Microsoft ending support for Dynamics 365 Fraud Protection in February 2026, enterprises using Azure AD B2C must find new ways to maintain fraud detection capabilities. Risk Query offers a seamless bridge between Akamai Account Protector and B2C by bypassing header restrictions and enabling secure, low-latency fraud score propagation through a distributed key-value store.

On February 3, 2026, Microsoft will sunset support for Dynamics 365 Fraud Protection (DFP), prompting enterprises to evaluate new fraud prevention strategies. Akamai Account Protector (APR) continues to offer trusted device fingerprints and risk scores, but Azure Active Directory B2C (B2C) does not propagate APR’s risk score header downstream. Risk Query bridges this gap with a lightweight, distributed key-value service that enables APR to write and B2C to read, restoring fraud protection logic.

Challenges

Header Restrictions

Azure AD B2C permits only a fixed set of headers in its Identity Experience Framework (IEF), blocking APR’s score. 

Looming DFP Retirement

With DFP feature development ending and end-of-life announced, brands need a replacement that works within B2C architectures.


Risk Query Solution

Risk Query provides an integration path between APR and B2C, bypassing header restrictions. Akamai injects fraud scores into a secure high-speed Harper key-value store. B2C reads them using native HTTP policy calls.

Outcomes

Zero Disruption – keep fraud controls after DFP retirement.

Sub-100 ms User Experience – no noticeable latency added to login flow.

Days-not-months Migration – drop-in REST calls; no schema work.

Edge Powered – distributed deployments provide global performance.

Image collage of person talking on the phone
Image collage of person talking on the phone

Speak with an Expert

Request received! We'll reach out shortly. In the meantime, check out our Dev Center for helpful development resources.
Go to Dev Center
Uh-oh! It seems your submission failed to submit. Please try again.