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

(Updated) Retirement of -Credential parameter when connecting to Exchange Online PowerShell

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

Action date

Microsoft tags this a retirement but gives no action date in the notice metadata. Any date is in the text below.

Microsoft's start date
10 Mar 2026
Last changed by Microsoft
15 Jul 2026
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

Updated July 15, 2026: We have updated the timeline. Thank you for your patience.

Introduction

Microsoft is retiring the -Credential parameter used when connecting to Exchange Online PowerShell. Starting with module versions released in December 2026 and later, the -Credential parameter will be removed from both Connect-ExchangeOnline and Connect-IppsSession cmdlets. Organizations using this parameter in automation scripts must migrate to a supported authentication method before that date. This change improves security by moving away from legacy authentication methods that do not support modern protections such as multifactor authentication (MFA).

When this will happen

  • The -Credential parameter will be removed from Connect-ExchangeOnline and Connect-IppsSession cmdlets in Exchange Online PowerShell module versions released beginning end of year 2026 (previously July).
  • A separate server-side retirement of the underlying authentication flow is planned for a later date and will be communicated in advance.

How this affects your organization

Who is affected

  • Microsoft 365 administrators using Exchange Online or Security & Compliance PowerShell
  • Organizations with automation scripts that use the -Credential parameter

What will happen

  • If your organization uses the -Credential parameter in PowerShell scripts or automation workflows connecting to Exchange Online or Security & Compliance PowerShell, those scripts will break when you update to an Exchange Online PowerShell module version released beginning December 2026.
  • No impact if your organization does not use the -Credential parameter

What you can do to prepare

  • If you are using the -Credential parameter, begin migrating your scripts now. Do not wait until December 2026. Choose the appropriate alternative based on your scenario:
  • Review internal documentation and communicate changes to admins
  • If you are not using the -Credential parameter, no action is required.

Additional information

This change is currently client-side only and will not take effect automatically. Your existing scripts will continue to work if you continue using an Exchange Online PowerShell module version released before December 2026. The -Credential parameter will only be removed when you upgrade to a module version released in December 2026 and later.

A separate server-side retirement of the Credential parameter authentication flow is planned for a later date. When that occurs, the -Credential parameter will stop functioning even on older module versions. Microsoft will communicate that timeline separately and provide advance notice before any service-side changes take effect.

We strongly recommend migrating proactively rather than waiting, to avoid disruption when either change occurs. If you have questions or concerns, contact Microsoft Support or leave a comment on the Exchange Team Blog post.

Compliance considerations

Compliance areaImpact
Conditional Access policiesRetiring the -Credential parameter removes use of the ROPC authentication flow and enables enforcement of Conditional Access and multifactor authentication for Exchange Online PowerShell connections.

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

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.
  • 1 linked page has not been read yet.
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