Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 12:24 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Entra ID: Retirement of duplicative properties in passkey (FIDO2) authentication methods policy

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Action date

in 12 months Act by , as Microsoft's metadata states
Microsoft's start date
19 Nov 2025
Last changed by Microsoft
19 Nov 2025
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

Introduction

Starting October 2027 and ending November 2027, we will retire the isAttestationEnforced and keyRestrictionsproperties from the existing fido2AuthenticationMethodConfiguration API schema. This change aligns with the latest update to the passkey policy API schema, which introduces support for granular group-based configurations with passkey profiles.

During the retirement period, isAttestationEnforced and keyRestrictions will remain in sync with their counterparts attestationEnforcement and keyRestrictions within the Default passkey profile.

When this will happen

Retirement begins in mid-October 2027 and is expected to complete by early November 2027.

How this affects your organization

You are receiving this message because our reporting indicates your organization may be using this feature.

Who is affected: Admins managing FIDO2 authentication configurations and any custom automations or third-party integrations using these properties.

What will happen

  • isAttestationEnforced and keyRestrictions properties will be retired.
  • New properties are available in the updated passkey policy API schema.
  • Existing properties will sync with new ones during the transition period.
  • Automations or integrations using retired properties will stop working after the change.

What you can do to prepare

  • Review your current configuration.
  • Update any custom automations and third-party integrations to support the new schema.
  • Notify your admins and update internal documentation.

Screenshot - The read arrows indicate the properties to be retired:

Learn more: fido2AuthenticationMethodConfiguration resource type | Microsoft Graph | Microsoft Learn

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 12:24 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current