Fix Set-ExternalInOutlook Enabled Parameter Not Found Error
Question details
The user needs to resolve an issue where a specific PowerShell cmdlet parameter is not recognized when attempting to configure external email settings.

- Product
- Microsoft 365 / Exchange Online
- Device & OS
- not provided
- Scenario
- Attempting to enable external sender identification in Outlook using the Exchange Online PowerShell module.
- Observed behavior
- The Set-ExternalInOutlook cmdlet fails with the error message 'A parameter cannot be found that matches parameter name Enabled', despite the module being fully updated and the Get-ExternalInOutlook cmdlet functioning correctly.
Ensure you are using the latest version of the ExchangeOnlineManagement module and are connected to Exchange Online with the appropriate administrator permissions.
Verify Tenant Configuration and Contact Microsoft Support
Since this is often a tenant-specific deployment issue or phased rollout limitation, reaching out to Microsoft Support or the community is the most effective path to resolution.
In Microsoft 365 environments, PowerShell cmdlet parameters like 'Enabled' for Set-ExternalInOutlook can sometimes be unavailable due to staggered backend feature rollouts. If the command works in one tenant but fails in another despite identical module versions, the issue is typically tied to the specific tenant's provisioning state.
Open PowerShell as an administrator and run 'Update-Module -Name ExchangeOnlineManagement' to confirm you are using the latest supported module.
Log into the Microsoft 365 admin center and verify that your user account is assigned the Exchange Administrator or Global Administrator role.
Navigate to the Support tab in the Microsoft 365 admin center and create a new service request detailing the missing 'Enabled' parameter.
Post your specific tenant behavior in the Microsoft PowerShell Community forum to get specialized troubleshooting assistance from Exchange engineers.

Switch to WPS Office for a Hassle-Free Desktop Experience
While Microsoft 365 offers complex enterprise backend features, managing tenant configurations via PowerShell can be frustrating. For everyday document creation, spreadsheet analysis, and presentations, WPS Office provides a free, lightweight, and incredibly intuitive alternative that simply works.

Frequently Asked Questions
Why does Get-ExternalInOutlook work while Set-ExternalInOutlook fails?
This discrepancy frequently occurs during phased Microsoft 365 rollouts. The 'Get' cmdlet is often deployed to the tenant before the corresponding parameters for the 'Set' cmdlet are fully activated on the Exchange Online backend.
What permissions are required to run Set-ExternalInOutlook?
To configure external sender identification settings, your account typically needs to be assigned the Organization Management or Exchange Administrator role within your Microsoft 365 tenant.
How can I check if my Exchange Online PowerShell module is updated?
You can verify and update your module by opening PowerShell as an Administrator and running 'Update-Module -Name ExchangeOnlineManagement'. After updating, reconnect your session using 'Connect-ExchangeOnline'.
Can WPS Office manage external sender settings for Outlook?
No, external sender identification is a server-side feature specific to Exchange Online. WPS Office is a desktop productivity suite focused on documents, spreadsheets, and presentations rather than server email management.




