Native CAPTCHA deprecation on Marketing Forms (D365 CI-J)

(0) Share

Report

Posted on by Dirk Cuthbertson

We've just been informed as part of a case with MS support that the native CATCHA on Marketing Forms is going to be deprecated on 1-March-2026, the only option with be reCAPTCHA. The only method to deploy that currently is not, in my option, a realistic one for your average marketer: Integrate reCAPTCHA service with Customer Insights - Journeys forms - Dynamics 365 Customer Insights | Microsoft Learn. We've been told "The Product Team is actively working on improvements that will make its deployment easier".

Has anyone else heard similar or any other insights? My primary concern is what happens if you have the native CAPTCHA deployed on live forms.

Categories:

Dynamics 365 Customer Insights - Journeys

I have the same question (0)

All responses (1)

Answers (0)

Dirk Cuthbertson 37 on at

Like (0)

Report
Copy link

Link copied!
We've had some clarification...

The current native CAPTCHA for Real-time Marketing forms will be deprecated in March 2026 and fully decommissioned by June 30, 2026.

From the February release, a new reCAPTCHA option will be available in the Form Editor, requiring configuration of a Site Key and Secret Key.

After the March release, native CAPTCHA will no longer be available in the Form Editor, though it will continue to function on already-published forms until June.

In June 2026, native CAPTCHA will be automatically removed from all forms.

Public documentation and formal communication for this change are currently being finalized and will be published soon.

To help you prepare for the upcoming change:

Take an inventory of all live and draft forms currently using the native CAPTCHA.

Begin testing reCAPTCHA on a small number of non‑production or low‑impact forms once it becomes available in the February release

Plan to transition all live forms from native CAPTCHA to reCAPTCHA well ahead of the June 30, 2026 decommissioning date.

Avoid long‑term reliance on native CAPTCHA, as it will no longer be configurable after the March release and will be automatically removed in June.

Was this reply helpful? Yes No