Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,7 @@ Set-SPOSite [-Identity] <SpoSitePipeBind> [-Owner <String>] [-Title <String>] [-
[-ListsShowHeaderAndNavigation <Boolean>] [-HidePeoplePreviewingFiles <Boolean>]
[-HidePeopleWhoHaveListsOpen <Boolean>] [-IsAuthoritative <Boolean>] [-AllowFileArchive <Boolean>]
[-AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled <Boolean>] [-DisableSiteBranding <Boolean>]
[-DisableClassicPageBaselineSecurityMode <Boolean>]
[-WhatIf] [-Confirm] [<CommonParameters>]
```

Expand Down Expand Up @@ -522,6 +523,26 @@ Accept pipeline input: False
Accept wildcard characters: False
```

### -DisableClassicPageBaselineSecurityMode

> Applicable: SharePoint Online

Allows a site to disable baseline security mode for classic pages. When `DisableClassicPageBaselineSecurityMode` is set to `$true`, users can create and edit classic pages even if baseline security mode is enabled at the tenant level.
Copy link
Contributor

@samkabue samkabue Nov 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

enabled at the tenant level

baseline security mode is enabled at the tenant level.

@libihan so is there an equivalent tenant-level property that can be set to $true | $false?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@samkabue Yes, there is a tenant-level property — not supported in the PowerShell cmdlets, but will be available to tenants in CY26H1 through the Microsoft Admin Center (market name: Baseline security mode – Block creation and editing of classic pages in SharePoint sites).

We added this site-level opt-out early to support MSIT in January.

Copy link
Contributor

@samkabue samkabue Nov 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@libihan I'd suggest you guys also update the documentation for the tenant-level one, then reference it from here at that time. for now, this current PR is good to go.


PARAMVALUE: True | False

```yaml
Type: System.Boolean
Parameter Sets: ParamSet1
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -AnonymousLinkExpirationInDays

> Applicable: SharePoint Online
Expand Down