Sways should not be shareable with people outside the organization
This check looks at the Sway service setting that lets people in your organization share their Sways with external people. The safe setting is to leave that option switched off, so Sways can only be shared inside the organization.
Why it matters
Sway is a presentation and newsletter tool that sits inside Microsoft 365. Anyone with a licence can build a Sway from internal material and then share it by link. When external sharing is allowed, a Sway made from internal figures, plans or screenshots can leave the organization with one click and without any review.
Microsoft documents the setting in its Sway administrator guide and notes that external sharing is turned on by default, so a tenant that has never touched the setting allows it. See the sources below.
How to check it yourself
Sign in to the Microsoft 365 admin center as an administrator and open Settings → Settings (shown as Org settings in some tenants). On the Services page choose Sway. Look at the box Let the people in your organization share their Sways with external people. It should be cleared.
Microsoft does not document a PowerShell cmdlet or Graph call that reads this setting, so there is no supported read-only command to offer here. The portal view is the reliable check, and it changes nothing.
How to fix it
In the same Sway settings page, clear the box Let the people in your organization share their Sways with external people and select Save changes. This is a portal-only change; Microsoft publishes no script for it.
You make this change yourself. ConfigCobra reads your tenant with read-only permissions and never changes a setting. It reports the finding and suggests these steps.
What changes when you fix it
Users no longer see external sharing destinations inside Sway, so they can share their Sways only with people in your organization. Anyone who currently sends Sways to customers, partners or the public will notice straight away, so ask the marketing, training and communications teams first.
Microsoft's page does not say whether Sways that were already shared externally are affected, so look at your important public Sways after the change instead of assuming they still work. Where you do need an outside audience, agree another route, such as publishing the content on your website or sharing a file through a controlled sharing site.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft 365 Foundations v7.0.0 | 1.3.8 | E3 Level 2 |
More checks in Microsoft 365 admin center
- The password expiration policy should be set to never expireCIS 1.3.1
- Idle session timeout for unmanaged devices should be three hours or lessCIS 1.3.2
- External calendar sharing should be turned offCIS 1.3.3
- User-owned apps and services should be restrictedCIS 1.3.4
- Internal phishing protection for Microsoft Forms should be enabledCIS 1.3.5
Go further
- Microsoft 365 admin center15 controls in this section
- CIS Microsoft 365 Foundations v7.0.0160 controls
- CIS Microsoft 365 Foundations checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Microsoft 365
ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.