We are committed to keeping you ahead of regulatory and industry changes. To ensure compliance with TCF v2.3 before the February 28, 2026 deadline:
Web CMP (script/API implementation):
Available November 12, 2025App CMP:
Already available
If you use our CMP for a website through script or API implementation:
No action required. Once released, all newly generated consent strings will automatically comply with TCF v2.3, including the Disclosed Vendors segment.
If you use our Browser SDK for a website:
You need to update your Browser SDK before February 28, 2026 to ensure all consent signals remain compliant. This SDK will be available on November 12, 2025.
If you use our CMP for a mobile application:
You need to update your App SDK to version 2.24.0 before February 28, 2026 to ensure all consent signals remain compliant. The updated SDK is already available for download:
Some customers have recently received communication from Microsoft regarding upcoming changes to IAB Europe’s Transparency & Consent Framework (TCF) v2.3 and the February 28, 2026 deadline. This article clarifies when action is required and what it means for your setup.
Do I Need to Switch to TCF?
It depends on how you use Microsoft services.
You likely need TCF if you:
- Monetize website traffic through advertising (publisher model)
- Serve personalized ads to users in the EU/EEA/UK within ecosystems that require TCF consent signals
You likely do NOT need TCF if you:
- Use Microsoft Advertising only as an advertiser (running campaigns)
- Use Microsoft Clarity for analytics only
- Do not monetize website traffic through ad networks
If you use Microsoft Advertising as an advertiser and do not operate under TCF, we recommend enabling Microsoft Consent Mode (UET integration) in your CMP configuration. This ensures that consent signals are properly passed to Microsoft Advertising without requiring a TCF setup