https://microsoft.com
Scanned Apr 15, 2026 · 20.7s
Your website score is
Grade
BannerConsent Banner
No
Regulatory Compliance
Multi-regulation overview — click any regulation for details
Technical scan only. A passing score does not equal legal compliance. Consult qualified legal counsel for your jurisdiction.
Tag Leak detected 12 user data leaks before consent on microsoft.com, including Advertising Tracker, Microsoft Clarity.
Security Headers
1/6 presentStrict-Transport-Security
max-age=31536000; includeSubDomains
Content-Security-Policy
Add a Content-Security-Policy header to prevent XSS and code injection attacks
X-Frame-Options
Add X-Frame-Options header to prevent clickjacking attacks
X-Content-Type-Options
Set X-Content-Type-Options to 'nosniff' to prevent MIME type sniffing
Referrer-Policy
Set a Referrer-Policy header to control how much referrer information is shared
Permissions-Policy
Add a Permissions-Policy header to restrict browser features like camera, microphone, and geolocation
Google Consent Mode
Not DetectedGoogle Consent Mode v2 was not found on this page. GCM v2 allows Google's tags to adjust their behavior based on user consent, and is required for compliant advertising measurement in the EU. Without it, your Google Ads and GA4 conversions may be impacted after consent is declined.
Post-Rejection Audit
Reject Button
Missing
Post-Rejection Fires
0 vendors
Consent Mode
Not Detected
GTM Load
Not detected
Consent Mode V2: Not Detected
Google Consent Mode was not detected on this site.
Consent Record Audit
Issues detectedConsent record stored after interaction
GDPR Art. 7(1)No consent record written — cannot prove consent was given
No CMP consent cookie or localStorage entry was found after the consent interaction. GDPR requires controllers to demonstrate consent was given.
Consent withdrawal mechanism accessible
GDPR Art. 7(3)No way for users to withdraw consent found on page
No cookie settings link, footer link, or floating consent button was detected. GDPR requires users to withdraw consent as easily as they gave it.
Why this matters
Under GDPR Article 7, controllers must be able to demonstrate that consent was given (Art. 7(1)) and ensure users can withdraw consent at any time, as easily as giving it (Art. 7(3)). Sites with no consent record or no withdrawal mechanism cannot legally rely on consent as a lawful basis.
Tracker categories detected
Critical8
Microsoft Clarity3 findingsID trackedwww.clarity.ms, scripts.clarity.ms, i.clarity.ms

www.clarity.ms, scripts.clarity.ms, i.clarity.ms

Microsoft Clarity (Microsoft) loaded before consent: Session recording and heatmap analytics

Microsoft Clarity (Microsoft) loaded before consent: Session recording and heatmap analytics

Microsoft Clarity (Microsoft) loaded before consent: Session recording and heatmap analytics
advertising tracker at rum.hlx.page loaded before consent
No consent banner detected — all cookies and tags fire without user consent
No "reject all" option found — users cannot refuse non-essential cookies (ICO guidance requires this)
No recognizable consent cookie or storage entry detected after interaction — GDPR Article 7(1) requires controllers to demonstrate consent was given (server-side storage cannot be verified)
No recognizable consent withdrawal mechanism detected — GDPR Article 7(3) requires users can withdraw consent as easily as giving it (cookie settings link or floating button expected)
Warnings7
Unknown third-party request to c.s-microsoft.com before consent
Unknown third-party request to mem.gfx.ms before consent
Unknown third-party request to login.microsoftonline.com before consent
Unknown third-party request to login.live.com before consent
Unknown third-party request to assets.onestore.ms before consent
Unknown third-party request to img-prod-cms-rt-microsoft-com.akamaized.net before consent
sessionStorage key "msameid" written before consent
Info8

Microsoft (cdn) loaded before consent
Azure / Microsoft4 findingsASLBSA, ASLBSACORS, fpc, stsservicecookie

ASLBSA, ASLBSACORS, fpc, stsservicecookie

Azure / Microsoft cookie "ASLBSA" set before consent — Microsoft App Service and Front Door Affinity Cookies. These cookies are used to direct your browser to use the appropriate backend server.

Azure / Microsoft cookie "ASLBSACORS" set before consent — Microsoft App Service and Front Door Affinity Cookies. These cookies are used to direct your browser to use the appropriate backend server.

Azure / Microsoft cookie "fpc" set before consent — This cookie is used by Microsoft to securely verify your login information

Azure / Microsoft cookie "stsservicecookie" set before consent — Cookie for Azure Active Directory B2C-verification

Microsoft cookie "esctx-ZhKyh6DpRNc" set before consent — This cookie is set by Microsoft for secure authentication of the users' login details

Bing / Microsoft cookie "x-ms-gateway-slice" set before consent — Identifies a gateway for load balancing.
Akamai bot management session — necessary for site protection
Is this your site?
Run a full multi-page scan with monitoring and get detailed remediation steps
Scan microsoft.com →This audit is based on publicly observable website behavior. To request removal from the index, email support@tagleak.com