diff --git a/.openpublishing.redirection.exchange.json b/.openpublishing.redirection.exchange.json
index b92868d1fd..7eb756dfc2 100644
--- a/.openpublishing.redirection.exchange.json
+++ b/.openpublishing.redirection.exchange.json
@@ -1,73 +1,73 @@
{
"redirections": [
{
- "source_path": "exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpEdmSschema.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpedmschema",
+ "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpEdmSschema.md",
+ "redirect_url": "/powershell/module/exchange/new-dlpedmschema",
"redirect_document_id": false
},
{
- "source_path": "exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-TeamsRetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancepolicy",
+ "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-TeamsRetentionCompliancePolicy.md",
+ "redirect_url": "/powershell/module/exchange/get-retentioncompliancepolicy",
"redirect_document_id": false
},
{
- "source_path": "exchange/exchange-ps/exchange/policy-and-compliance-retention/Get-TeamsRetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancerule",
+ "source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-TeamsRetentionComplianceRule.md",
+ "redirect_url": "/powershell/module/exchange/get-retentioncompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-TeamsRetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/new-retentioncompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-TeamsRetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancerule",
+ "redirect_url": "/powershell/module/exchange/new-retentioncompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-TeamsRetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/remove-retentioncompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-TeamsRetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancerule",
+ "redirect_url": "/powershell/module/exchange/remove-retentioncompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-TeamsRetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/set-retentioncompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-TeamsRetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancerule",
+ "redirect_url": "/powershell/module/exchange/set-retentioncompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpComplianceRuleV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpcompliancerule",
+ "redirect_url": "/powershell/module/exchange/get-dlpcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpComplianceRuleV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpcompliancerule",
+ "redirect_url": "/powershell/module/exchange/new-dlpcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRuleV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpcompliancerule",
+ "redirect_url": "/powershell/module/exchange/remove-dlpcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpComplianceRuleV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpcompliancerule",
+ "redirect_url": "/powershell/module/exchange/set-dlpcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/exchange-ps-v2-module/connect-exchangeonline.md",
- "redirect_url": "/powershell/module/exchangepowershell/connect-exchangeonline",
+ "redirect_url": "/powershell/module/exchange/connect-exchangeonline",
"redirect_document_id": true
},
{
@@ -162,2987 +162,2987 @@
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Add-ADPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-adpermission",
+ "redirect_url": "/powershell/module/exchange/add-adpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Dump-ProvisioningCache.md",
- "redirect_url": "/powershell/module/exchangepowershell/dump-provisioningcache",
+ "redirect_url": "/powershell/module/exchange/dump-provisioningcache",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Get-ADPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adpermission",
+ "redirect_url": "/powershell/module/exchange/get-adpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Get-ADServerSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adserversettings",
+ "redirect_url": "/powershell/module/exchange/get-adserversettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Get-ADSite.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adsite",
+ "redirect_url": "/powershell/module/exchange/get-adsite",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Get-AdSiteLink.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adsitelink",
+ "redirect_url": "/powershell/module/exchange/get-adsitelink",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Get-DomainController.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-domaincontroller",
+ "redirect_url": "/powershell/module/exchange/get-domaincontroller",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Get-OrganizationalUnit.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-organizationalunit",
+ "redirect_url": "/powershell/module/exchange/get-organizationalunit",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Get-Trust.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-trust",
+ "redirect_url": "/powershell/module/exchange/get-trust",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Get-UserPrincipalNamesSuffix.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-userprincipalnamessuffix",
+ "redirect_url": "/powershell/module/exchange/get-userprincipalnamessuffix",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Remove-ADPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-adpermission",
+ "redirect_url": "/powershell/module/exchange/remove-adpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Reset-ProvisioningCache.md",
- "redirect_url": "/powershell/module/exchangepowershell/reset-provisioningcache",
+ "redirect_url": "/powershell/module/exchange/reset-provisioningcache",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Set-ADServerSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adserversettings",
+ "redirect_url": "/powershell/module/exchange/set-adserversettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Set-ADSite.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adsite",
+ "redirect_url": "/powershell/module/exchange/set-adsite",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/active-directory/Set-AdSiteLink.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adsitelink",
+ "redirect_url": "/powershell/module/exchange/set-adsitelink",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Disable-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-antiphishrule",
+ "redirect_url": "/powershell/module/exchange/disable-antiphishrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Disable-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-safeattachmentrule",
+ "redirect_url": "/powershell/module/exchange/disable-safeattachmentrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Disable-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-safelinksrule",
+ "redirect_url": "/powershell/module/exchange/disable-safelinksrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Enable-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-antiphishrule",
+ "redirect_url": "/powershell/module/exchange/enable-antiphishrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Enable-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-safeattachmentrule",
+ "redirect_url": "/powershell/module/exchange/enable-safeattachmentrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Enable-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-safelinksrule",
+ "redirect_url": "/powershell/module/exchange/enable-safelinksrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentDetail.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-advancedthreatprotectiondocumentdetail",
+ "redirect_url": "/powershell/module/exchange/get-advancedthreatprotectiondocumentdetail",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionDocumentReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-advancedthreatprotectiondocumentreport",
+ "redirect_url": "/powershell/module/exchange/get-advancedthreatprotectiondocumentreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AdvancedThreatProtectionTrafficReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailatpreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AntiPhishPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-antiphishpolicy",
+ "redirect_url": "/powershell/module/exchange/get-antiphishpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-antiphishrule",
+ "redirect_url": "/powershell/module/exchange/get-antiphishrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-AtpPolicyForO365.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-atppolicyforo365",
+ "redirect_url": "/powershell/module/exchange/get-atppolicyforo365",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-MailDetailATPReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailatpreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-MailTrafficATPReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficatpreport",
+ "redirect_url": "/powershell/module/exchange/get-mailtrafficatpreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-PhishFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-tenantallowblocklistspoofitems",
+ "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistspoofitems",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeAttachmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safeattachmentpolicy",
+ "redirect_url": "/powershell/module/exchange/get-safeattachmentpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safeattachmentrule",
+ "redirect_url": "/powershell/module/exchange/get-safeattachmentrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeLinksPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safelinkspolicy",
+ "redirect_url": "/powershell/module/exchange/get-safelinkspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safelinksrule",
+ "redirect_url": "/powershell/module/exchange/get-safelinksrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-SpoofMailReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-spoofmailreport",
+ "redirect_url": "/powershell/module/exchange/get-spoofmailreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-UrlTrace.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safelinksaggregatereport",
+ "redirect_url": "/powershell/module/exchange/get-safelinksaggregatereport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-AntiPhishPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-antiphishpolicy",
+ "redirect_url": "/powershell/module/exchange/new-antiphishpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-antiphishrule",
+ "redirect_url": "/powershell/module/exchange/new-antiphishrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeAttachmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-safeattachmentpolicy",
+ "redirect_url": "/powershell/module/exchange/new-safeattachmentpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-safeattachmentrule",
+ "redirect_url": "/powershell/module/exchange/new-safeattachmentrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeLinksPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-safelinkspolicy",
+ "redirect_url": "/powershell/module/exchange/new-safelinkspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/New-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-safelinksrule",
+ "redirect_url": "/powershell/module/exchange/new-safelinksrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-AntiPhishPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-antiphishpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-antiphishpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-antiphishrule",
+ "redirect_url": "/powershell/module/exchange/remove-antiphishrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeAttachmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-safeattachmentpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-safeattachmentpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-safeattachmentrule",
+ "redirect_url": "/powershell/module/exchange/remove-safeattachmentrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeLinksPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-safelinkspolicy",
+ "redirect_url": "/powershell/module/exchange/remove-safelinkspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Remove-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-safelinksrule",
+ "redirect_url": "/powershell/module/exchange/remove-safelinksrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-AntiPhishPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-antiphishpolicy",
+ "redirect_url": "/powershell/module/exchange/set-antiphishpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-antiphishrule",
+ "redirect_url": "/powershell/module/exchange/set-antiphishrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-AtpPolicyForO365.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-atppolicyforo365",
+ "redirect_url": "/powershell/module/exchange/set-atppolicyforo365",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-PhishFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-tenantallowblocklistspoofitems",
+ "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistspoofitems",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeAttachmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-safeattachmentpolicy",
+ "redirect_url": "/powershell/module/exchange/set-safeattachmentpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-safeattachmentrule",
+ "redirect_url": "/powershell/module/exchange/set-safeattachmentrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeLinksPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-safelinkspolicy",
+ "redirect_url": "/powershell/module/exchange/set-safelinkspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-safelinksrule",
+ "redirect_url": "/powershell/module/exchange/set-safelinksrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-AttachmentFilterEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-attachmentfilterentry",
+ "redirect_url": "/powershell/module/exchange/add-attachmentfilterentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-ContentFilterPhrase.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-contentfilterphrase",
+ "redirect_url": "/powershell/module/exchange/add-contentfilterphrase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPAllowListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ipallowlistentry",
+ "redirect_url": "/powershell/module/exchange/add-ipallowlistentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ipallowlistprovider",
+ "redirect_url": "/powershell/module/exchange/add-ipallowlistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPBlockListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ipblocklistentry",
+ "redirect_url": "/powershell/module/exchange/add-ipblocklistentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Add-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ipblocklistprovider",
+ "redirect_url": "/powershell/module/exchange/add-ipblocklistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Delete-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/delete-quarantinemessage",
+ "redirect_url": "/powershell/module/exchange/delete-quarantinemessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Disable-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-hostedcontentfilterrule",
+ "redirect_url": "/powershell/module/exchange/disable-hostedcontentfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Disable-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-hostedoutboundspamfilterrule",
+ "redirect_url": "/powershell/module/exchange/disable-hostedoutboundspamfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Disable-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-malwarefilterrule",
+ "redirect_url": "/powershell/module/exchange/disable-malwarefilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-AntispamUpdates.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-antispamupdates",
+ "redirect_url": "/powershell/module/exchange/enable-antispamupdates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-hostedcontentfilterrule",
+ "redirect_url": "/powershell/module/exchange/enable-hostedcontentfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-hostedoutboundspamfilterrule",
+ "redirect_url": "/powershell/module/exchange/enable-hostedoutboundspamfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Enable-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-malwarefilterrule",
+ "redirect_url": "/powershell/module/exchange/enable-malwarefilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Export-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-quarantinemessage",
+ "redirect_url": "/powershell/module/exchange/export-quarantinemessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-AgentLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-agentlog",
+ "redirect_url": "/powershell/module/exchange/get-agentlog",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-AttachmentFilterEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-attachmentfilterentry",
+ "redirect_url": "/powershell/module/exchange/get-attachmentfilterentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-AttachmentFilterListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-attachmentfilterlistconfig",
+ "redirect_url": "/powershell/module/exchange/get-attachmentfilterlistconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-BlockedSenderAddress.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-blockedsenderaddress",
+ "redirect_url": "/powershell/module/exchange/get-blockedsenderaddress",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-ContentFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contentfilterconfig",
+ "redirect_url": "/powershell/module/exchange/get-contentfilterconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-ContentFilterPhrase.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contentfilterphrase",
+ "redirect_url": "/powershell/module/exchange/get-contentfilterphrase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-DkimSigningConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dkimsigningconfig",
+ "redirect_url": "/powershell/module/exchange/get-dkimsigningconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedConnectionFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedconnectionfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/get-hostedconnectionfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedContentFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedcontentfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/get-hostedcontentfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedcontentfilterrule",
+ "redirect_url": "/powershell/module/exchange/get-hostedcontentfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedoutboundspamfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/get-hostedoutboundspamfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedoutboundspamfilterrule",
+ "redirect_url": "/powershell/module/exchange/get-hostedoutboundspamfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistconfig",
+ "redirect_url": "/powershell/module/exchange/get-ipallowlistconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistentry",
+ "redirect_url": "/powershell/module/exchange/get-ipallowlistentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistprovider",
+ "redirect_url": "/powershell/module/exchange/get-ipallowlistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPAllowListProvidersConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistprovidersconfig",
+ "redirect_url": "/powershell/module/exchange/get-ipallowlistprovidersconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistconfig",
+ "redirect_url": "/powershell/module/exchange/get-ipblocklistconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistentry",
+ "redirect_url": "/powershell/module/exchange/get-ipblocklistentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistprovider",
+ "redirect_url": "/powershell/module/exchange/get-ipblocklistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-IPBlockListProvidersConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistprovidersconfig",
+ "redirect_url": "/powershell/module/exchange/get-ipblocklistprovidersconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MailboxJunkEmailConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxjunkemailconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-mailboxjunkemailconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MalwareFilteringServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilteringserver",
+ "redirect_url": "/powershell/module/exchange/get-malwarefilteringserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MalwareFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilterpolicy",
+ "redirect_url": "/powershell/module/exchange/get-malwarefilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilterrule",
+ "redirect_url": "/powershell/module/exchange/get-malwarefilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-quarantinemessage",
+ "redirect_url": "/powershell/module/exchange/get-quarantinemessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-QuarantineMessageHeader.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-quarantinemessageheader",
+ "redirect_url": "/powershell/module/exchange/get-quarantinemessageheader",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-RecipientFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recipientfilterconfig",
+ "redirect_url": "/powershell/module/exchange/get-recipientfilterconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-SenderFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-senderfilterconfig",
+ "redirect_url": "/powershell/module/exchange/get-senderfilterconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-SenderIdConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-senderidconfig",
+ "redirect_url": "/powershell/module/exchange/get-senderidconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Get-SenderReputationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-senderreputationconfig",
+ "redirect_url": "/powershell/module/exchange/get-senderreputationconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-DkimSigningConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dkimsigningconfig",
+ "redirect_url": "/powershell/module/exchange/new-dkimsigningconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hostedcontentfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/new-hostedcontentfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hostedcontentfilterrule",
+ "redirect_url": "/powershell/module/exchange/new-hostedcontentfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedOutboundSpamFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hostedoutboundspamfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/new-hostedoutboundspamfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hostedoutboundspamfilterrule",
+ "redirect_url": "/powershell/module/exchange/new-hostedoutboundspamfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-MalwareFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-malwarefilterpolicy",
+ "redirect_url": "/powershell/module/exchange/new-malwarefilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/New-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-malwarefilterrule",
+ "redirect_url": "/powershell/module/exchange/new-malwarefilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Preview-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/preview-quarantinemessage",
+ "redirect_url": "/powershell/module/exchange/preview-quarantinemessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Release-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/release-quarantinemessage",
+ "redirect_url": "/powershell/module/exchange/release-quarantinemessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-AttachmentFilterEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-attachmentfilterentry",
+ "redirect_url": "/powershell/module/exchange/remove-attachmentfilterentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-BlockedSenderAddress.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-blockedsenderaddress",
+ "redirect_url": "/powershell/module/exchange/remove-blockedsenderaddress",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-ContentFilterPhrase.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-contentfilterphrase",
+ "redirect_url": "/powershell/module/exchange/remove-contentfilterphrase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedContentFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hostedcontentfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-hostedcontentfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hostedcontentfilterrule",
+ "redirect_url": "/powershell/module/exchange/remove-hostedcontentfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hostedoutboundspamfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-hostedoutboundspamfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hostedoutboundspamfilterrule",
+ "redirect_url": "/powershell/module/exchange/remove-hostedoutboundspamfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPAllowListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ipallowlistentry",
+ "redirect_url": "/powershell/module/exchange/remove-ipallowlistentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ipallowlistprovider",
+ "redirect_url": "/powershell/module/exchange/remove-ipallowlistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPBlockListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ipblocklistentry",
+ "redirect_url": "/powershell/module/exchange/remove-ipblocklistentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ipblocklistprovider",
+ "redirect_url": "/powershell/module/exchange/remove-ipblocklistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-MalwareFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-malwarefilterpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-malwarefilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Remove-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-malwarefilterrule",
+ "redirect_url": "/powershell/module/exchange/remove-malwarefilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Rotate-DkimSigningConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/rotate-dkimsigningconfig",
+ "redirect_url": "/powershell/module/exchange/rotate-dkimsigningconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-AttachmentFilterListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-attachmentfilterlistconfig",
+ "redirect_url": "/powershell/module/exchange/set-attachmentfilterlistconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-ContentFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-contentfilterconfig",
+ "redirect_url": "/powershell/module/exchange/set-contentfilterconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-DkimSigningConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dkimsigningconfig",
+ "redirect_url": "/powershell/module/exchange/set-dkimsigningconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedConnectionFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedconnectionfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/set-hostedconnectionfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedcontentfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/set-hostedcontentfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedcontentfilterrule",
+ "redirect_url": "/powershell/module/exchange/set-hostedcontentfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedoutboundspamfilterpolicy",
+ "redirect_url": "/powershell/module/exchange/set-hostedoutboundspamfilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedoutboundspamfilterrule",
+ "redirect_url": "/powershell/module/exchange/set-hostedoutboundspamfilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPAllowListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistconfig",
+ "redirect_url": "/powershell/module/exchange/set-ipallowlistconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistprovider",
+ "redirect_url": "/powershell/module/exchange/set-ipallowlistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPAllowListProvidersConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistprovidersconfig",
+ "redirect_url": "/powershell/module/exchange/set-ipallowlistprovidersconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPBlockListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistconfig",
+ "redirect_url": "/powershell/module/exchange/set-ipblocklistconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistprovider",
+ "redirect_url": "/powershell/module/exchange/set-ipblocklistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-IPBlockListProvidersConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistprovidersconfig",
+ "redirect_url": "/powershell/module/exchange/set-ipblocklistprovidersconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MailboxJunkEmailConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxjunkemailconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-mailboxjunkemailconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MalwareFilteringServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilteringserver",
+ "redirect_url": "/powershell/module/exchange/set-malwarefilteringserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MalwareFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilterpolicy",
+ "redirect_url": "/powershell/module/exchange/set-malwarefilterpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilterrule",
+ "redirect_url": "/powershell/module/exchange/set-malwarefilterrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-RecipientFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-recipientfilterconfig",
+ "redirect_url": "/powershell/module/exchange/set-recipientfilterconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-SenderFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-senderfilterconfig",
+ "redirect_url": "/powershell/module/exchange/set-senderfilterconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-SenderIdConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-senderidconfig",
+ "redirect_url": "/powershell/module/exchange/set-senderidconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Set-SenderReputationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-senderreputationconfig",
+ "redirect_url": "/powershell/module/exchange/set-senderreputationconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Test-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-ipallowlistprovider",
+ "redirect_url": "/powershell/module/exchange/test-ipallowlistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Test-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-ipblocklistprovider",
+ "redirect_url": "/powershell/module/exchange/test-ipblocklistprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Test-SenderId.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-senderid",
+ "redirect_url": "/powershell/module/exchange/test-senderid",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/antispam-antimalware/Update-SafeList.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-safelist",
+ "redirect_url": "/powershell/module/exchange/update-safelist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Clear-TextMessagingAccount.md",
- "redirect_url": "/powershell/module/exchangepowershell/clear-textmessagingaccount",
+ "redirect_url": "/powershell/module/exchange/clear-textmessagingaccount",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Compare-TextMessagingVerificationCode.md",
- "redirect_url": "/powershell/module/exchangepowershell/compare-textmessagingverificationcode",
+ "redirect_url": "/powershell/module/exchange/compare-textmessagingverificationcode",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Disable-PushNotificationProxy.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-pushnotificationproxy",
+ "redirect_url": "/powershell/module/exchange/disable-pushnotificationproxy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Enable-PushNotificationProxy.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-pushnotificationproxy",
+ "redirect_url": "/powershell/module/exchange/enable-pushnotificationproxy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Export-AutoDiscoverConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-autodiscoverconfig",
+ "redirect_url": "/powershell/module/exchange/export-autodiscoverconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-CASMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-casmailbox",
+ "redirect_url": "/powershell/module/exchange/get-casmailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-CASMailboxPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-casmailboxplan",
+ "redirect_url": "/powershell/module/exchange/get-casmailboxplan",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessrule",
+ "redirect_url": "/powershell/module/exchange/get-clientaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-ImapSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-imapsettings",
+ "redirect_url": "/powershell/module/exchange/get-imapsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxCalendarConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxcalendarconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-mailboxcalendarconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxMessageConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxmessageconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-mailboxmessageconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxRegionalConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxregionalconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-mailboxregionalconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-MailboxSpellingConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxspellingconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-mailboxspellingconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-OutlookProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outlookprovider",
+ "redirect_url": "/powershell/module/exchange/get-outlookprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-OwaMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-owamailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/get-owamailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-PopSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-popsettings",
+ "redirect_url": "/powershell/module/exchange/get-popsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Get-TextMessagingAccount.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-textmessagingaccount",
+ "redirect_url": "/powershell/module/exchange/get-textmessagingaccount",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/New-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-clientaccessrule",
+ "redirect_url": "/powershell/module/exchange/new-clientaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/New-OutlookProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-outlookprovider",
+ "redirect_url": "/powershell/module/exchange/new-outlookprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/New-OwaMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-owamailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/new-owamailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Remove-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-clientaccessrule",
+ "redirect_url": "/powershell/module/exchange/remove-clientaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Remove-OutlookProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-outlookprovider",
+ "redirect_url": "/powershell/module/exchange/remove-outlookprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Remove-OwaMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-owamailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-owamailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Send-TextMessagingVerificationCode.md",
- "redirect_url": "/powershell/module/exchangepowershell/send-textmessagingverificationcode",
+ "redirect_url": "/powershell/module/exchange/send-textmessagingverificationcode",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-CASMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-casmailbox",
+ "redirect_url": "/powershell/module/exchange/set-casmailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/set-CASMailboxPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-casmailboxplan",
+ "redirect_url": "/powershell/module/exchange/set-casmailboxplan",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessrule",
+ "redirect_url": "/powershell/module/exchange/set-clientaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-ImapSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-imapsettings",
+ "redirect_url": "/powershell/module/exchange/set-imapsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxCalendarConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxcalendarconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-mailboxcalendarconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxMessageConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxmessageconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-mailboxmessageconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxRegionalConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxregionalconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-mailboxregionalconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-MailboxSpellingConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxspellingconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-mailboxspellingconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-OutlookProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-outlookprovider",
+ "redirect_url": "/powershell/module/exchange/set-outlookprovider",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-OwaMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-owamailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/set-owamailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-PopSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-popsettings",
+ "redirect_url": "/powershell/module/exchange/set-popsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Set-TextMessagingAccount.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-textmessagingaccount",
+ "redirect_url": "/powershell/module/exchange/set-textmessagingaccount",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-CalendarConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-calendarconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-calendarconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-clientaccessrule",
+ "redirect_url": "/powershell/module/exchange/test-clientaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-EcpConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-ecpconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-ecpconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-ImapConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-imapconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-imapconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-OutlookConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-outlookconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-outlookconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-OutlookWebServices.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-outlookwebservices",
+ "redirect_url": "/powershell/module/exchange/test-outlookwebservices",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-OwaConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-owaconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-owaconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-PopConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-popconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-popconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-PowerShellConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-powershellconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-powershellconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access/Test-WebServicesConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-webservicesconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-webservicesconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Disable-OutlookAnywhere.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-outlookanywhere",
+ "redirect_url": "/powershell/module/exchange/disable-outlookanywhere",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Enable-OutlookAnywhere.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-outlookanywhere",
+ "redirect_url": "/powershell/module/exchange/enable-outlookanywhere",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ActiveSyncVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/get-activesyncvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-AuthRedirect.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-authredirect",
+ "redirect_url": "/powershell/module/exchange/get-authredirect",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-AutodiscoverVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-autodiscovervirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/get-autodiscovervirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ClientAccessArray.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessarray",
+ "redirect_url": "/powershell/module/exchange/get-clientaccessarray",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ClientAccessServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessserver",
+ "redirect_url": "/powershell/module/exchange/get-clientaccessserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-ClientAccessService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessservice",
+ "redirect_url": "/powershell/module/exchange/get-clientaccessservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-EcpVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ecpvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/get-ecpvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-MapiVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mapivirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/get-mapivirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-OutlookAnywhere.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outlookanywhere",
+ "redirect_url": "/powershell/module/exchange/get-outlookanywhere",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-OwaVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-owavirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/get-owavirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-PowerShellVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-powershellvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/get-powershellvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-RpcClientAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-rpcclientaccess",
+ "redirect_url": "/powershell/module/exchange/get-rpcclientaccess",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Get-WebServicesVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-webservicesvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/get-webservicesvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-ActiveSyncVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-activesyncvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/new-activesyncvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-AuthRedirect.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-authredirect",
+ "redirect_url": "/powershell/module/exchange/new-authredirect",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-AutodiscoverVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-autodiscovervirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/new-autodiscovervirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-ClientAccessArray.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-clientaccessarray",
+ "redirect_url": "/powershell/module/exchange/new-clientaccessarray",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-EcpVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-ecpvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/new-ecpvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-MapiVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mapivirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/new-mapivirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-OwaVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-owavirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/new-owavirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-PowerShellVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-powershellvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/new-powershellvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-RpcClientAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-rpcclientaccess",
+ "redirect_url": "/powershell/module/exchange/new-rpcclientaccess",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/New-WebServicesVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-webservicesvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/new-webservicesvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-ActiveSyncVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/remove-activesyncvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-AuthRedirect.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-authredirect",
+ "redirect_url": "/powershell/module/exchange/remove-authredirect",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-AutodiscoverVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-autodiscovervirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/remove-autodiscovervirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-ClientAccessArray.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-clientaccessarray",
+ "redirect_url": "/powershell/module/exchange/remove-clientaccessarray",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-EcpVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ecpvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/remove-ecpvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-MapiVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mapivirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/remove-mapivirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-OwaVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-owavirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/remove-owavirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-PowerShellVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-powershellvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/remove-powershellvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-RpcClientAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-rpcclientaccess",
+ "redirect_url": "/powershell/module/exchange/remove-rpcclientaccess",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Remove-WebServicesVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-webservicesvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/remove-webservicesvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ActiveSyncVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/set-activesyncvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-AuthRedirect.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-authredirect",
+ "redirect_url": "/powershell/module/exchange/set-authredirect",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-AutodiscoverVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-autodiscovervirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/set-autodiscovervirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ClientAccessArray.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessarray",
+ "redirect_url": "/powershell/module/exchange/set-clientaccessarray",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ClientAccessServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessserver",
+ "redirect_url": "/powershell/module/exchange/set-clientaccessserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-ClientAccessService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessservice",
+ "redirect_url": "/powershell/module/exchange/set-clientaccessservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-EcpVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ecpvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/set-ecpvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-MapiVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mapivirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/set-mapivirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-OutlookAnywhere.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-outlookanywhere",
+ "redirect_url": "/powershell/module/exchange/set-outlookanywhere",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-OwaVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-owavirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/set-owavirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-PowerShellVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-powershellvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/set-powershellvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-RpcClientAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-rpcclientaccess",
+ "redirect_url": "/powershell/module/exchange/set-rpcclientaccess",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/client-access-servers/Set-WebServicesVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-webservicesvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/set-webservicesvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Add-DatabaseAvailabilityGroupServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-databaseavailabilitygroupserver",
+ "redirect_url": "/powershell/module/exchange/add-databaseavailabilitygroupserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Add-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-mailboxdatabasecopy",
+ "redirect_url": "/powershell/module/exchange/add-mailboxdatabasecopy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Get-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-databaseavailabilitygroup",
+ "redirect_url": "/powershell/module/exchange/get-databaseavailabilitygroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Get-DatabaseAvailabilityGroupNetwork.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-databaseavailabilitygroupnetwork",
+ "redirect_url": "/powershell/module/exchange/get-databaseavailabilitygroupnetwork",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Get-MailboxDatabaseCopyStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxdatabasecopystatus",
+ "redirect_url": "/powershell/module/exchange/get-mailboxdatabasecopystatus",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Move-ActiveMailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/move-activemailboxdatabase",
+ "redirect_url": "/powershell/module/exchange/move-activemailboxdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/New-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-databaseavailabilitygroup",
+ "redirect_url": "/powershell/module/exchange/new-databaseavailabilitygroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/New-DatabaseAvailabilityGroupNetwork.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-databaseavailabilitygroupnetwork",
+ "redirect_url": "/powershell/module/exchange/new-databaseavailabilitygroupnetwork",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroup",
+ "redirect_url": "/powershell/module/exchange/remove-databaseavailabilitygroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupNetwork.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroupnetwork",
+ "redirect_url": "/powershell/module/exchange/remove-databaseavailabilitygroupnetwork",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroupserver",
+ "redirect_url": "/powershell/module/exchange/remove-databaseavailabilitygroupserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Remove-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxdatabasecopy",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxdatabasecopy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Restore-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/restore-databaseavailabilitygroup",
+ "redirect_url": "/powershell/module/exchange/restore-databaseavailabilitygroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Resume-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxdatabasecopy",
+ "redirect_url": "/powershell/module/exchange/resume-mailboxdatabasecopy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-databaseavailabilitygroup",
+ "redirect_url": "/powershell/module/exchange/set-databaseavailabilitygroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Set-DatabaseAvailabilityGroupNetwork.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-databaseavailabilitygroupnetwork",
+ "redirect_url": "/powershell/module/exchange/set-databaseavailabilitygroupnetwork",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Set-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxdatabasecopy",
+ "redirect_url": "/powershell/module/exchange/set-mailboxdatabasecopy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Start-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-databaseavailabilitygroup",
+ "redirect_url": "/powershell/module/exchange/start-databaseavailabilitygroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Stop-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-databaseavailabilitygroup",
+ "redirect_url": "/powershell/module/exchange/stop-databaseavailabilitygroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Suspend-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxdatabasecopy",
+ "redirect_url": "/powershell/module/exchange/suspend-mailboxdatabasecopy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Test-ReplicationHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-replicationhealth",
+ "redirect_url": "/powershell/module/exchange/test-replicationhealth",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/database-availability-groups/Update-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-mailboxdatabasecopy",
+ "redirect_url": "/powershell/module/exchange/update-mailboxdatabasecopy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Clear-ActiveSyncDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/clear-activesyncdevice",
+ "redirect_url": "/powershell/module/exchange/clear-activesyncdevice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Clear-MobileDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/clear-mobiledevice",
+ "redirect_url": "/powershell/module/exchange/clear-mobiledevice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Export-ActiveSyncLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-activesynclog",
+ "redirect_url": "/powershell/module/exchange/export-activesynclog",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdevice",
+ "redirect_url": "/powershell/module/exchange/get-activesyncdevice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceaccessrule",
+ "redirect_url": "/powershell/module/exchange/get-activesyncdeviceaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceAutoblockThreshold.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceautoblockthreshold",
+ "redirect_url": "/powershell/module/exchange/get-activesyncdeviceautoblockthreshold",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceClass.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceclass",
+ "redirect_url": "/powershell/module/exchange/get-activesyncdeviceclass",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncDeviceStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdevicestatistics",
+ "redirect_url": "/powershell/module/exchange/get-activesyncdevicestatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncmailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/get-activesyncmailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-ActiveSyncOrganizationSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncorganizationsettings",
+ "redirect_url": "/powershell/module/exchange/get-activesyncorganizationsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConditionalAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deviceconditionalaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/get-deviceconditionalaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConditionalAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deviceconditionalaccessrule",
+ "redirect_url": "/powershell/module/exchange/get-deviceconditionalaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deviceconfigurationpolicy",
+ "redirect_url": "/powershell/module/exchange/get-deviceconfigurationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deviceconfigurationrule",
+ "redirect_url": "/powershell/module/exchange/get-deviceconfigurationrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-DevicePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-devicepolicy",
+ "redirect_url": "/powershell/module/exchange/get-devicepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceTenantPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-devicetenantpolicy",
+ "redirect_url": "/powershell/module/exchange/get-devicetenantpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-DeviceTenantRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-devicetenantrule",
+ "redirect_url": "/powershell/module/exchange/get-devicetenantrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevice",
+ "redirect_url": "/powershell/module/exchange/get-mobiledevice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDeviceMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevicemailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/get-mobiledevicemailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Get-MobileDeviceStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevicestatistics",
+ "redirect_url": "/powershell/module/exchange/get-mobiledevicestatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-ActiveSyncDeviceAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-activesyncdeviceaccessrule",
+ "redirect_url": "/powershell/module/exchange/new-activesyncdeviceaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-ActiveSyncMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-activesyncmailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/new-activesyncmailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConditionalAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deviceconditionalaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/new-deviceconditionalaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConditionalAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deviceconditionalaccessrule",
+ "redirect_url": "/powershell/module/exchange/new-deviceconditionalaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deviceconfigurationpolicy",
+ "redirect_url": "/powershell/module/exchange/new-deviceconfigurationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-DeviceConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deviceconfigurationrule",
+ "redirect_url": "/powershell/module/exchange/new-deviceconfigurationrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-DeviceTenantPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-devicetenantpolicy",
+ "redirect_url": "/powershell/module/exchange/new-devicetenantpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-DeviceTenantRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-devicetenantrule",
+ "redirect_url": "/powershell/module/exchange/new-devicetenantrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/New-MobileDeviceMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mobiledevicemailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/new-mobiledevicemailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdevice",
+ "redirect_url": "/powershell/module/exchange/remove-activesyncdevice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDeviceAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdeviceaccessrule",
+ "redirect_url": "/powershell/module/exchange/remove-activesyncdeviceaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncDeviceClass.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdeviceclass",
+ "redirect_url": "/powershell/module/exchange/remove-activesyncdeviceclass",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-ActiveSyncMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncmailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-activesyncmailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConditionalAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconditionalaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/remove-deviceconditionalaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConditionalAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconditionalaccessrule",
+ "redirect_url": "/powershell/module/exchange/remove-deviceconditionalaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconfigurationpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-deviceconfigurationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconfigurationrule",
+ "redirect_url": "/powershell/module/exchange/remove-deviceconfigurationrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceTenantPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-devicetenantpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-devicetenantpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-DeviceTenantRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-devicetenantrule",
+ "redirect_url": "/powershell/module/exchange/remove-devicetenantrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-MobileDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mobiledevice",
+ "redirect_url": "/powershell/module/exchange/remove-mobiledevice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Remove-MobileDeviceMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mobiledevicemailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-mobiledevicemailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncDeviceAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncdeviceaccessrule",
+ "redirect_url": "/powershell/module/exchange/set-activesyncdeviceaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncDeviceAutoblockThreshold.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncdeviceautoblockthreshold",
+ "redirect_url": "/powershell/module/exchange/set-activesyncdeviceautoblockthreshold",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncmailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/set-activesyncmailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-ActiveSyncOrganizationSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncorganizationsettings",
+ "redirect_url": "/powershell/module/exchange/set-activesyncorganizationsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConditionalAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deviceconditionalaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/set-deviceconditionalaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConditionalAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deviceconditionalaccessrule",
+ "redirect_url": "/powershell/module/exchange/set-deviceconditionalaccessrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deviceconfigurationpolicy",
+ "redirect_url": "/powershell/module/exchange/set-deviceconfigurationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deviceconfigurationrule",
+ "redirect_url": "/powershell/module/exchange/set-deviceconfigurationrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceTenantPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-devicetenantpolicy",
+ "redirect_url": "/powershell/module/exchange/set-devicetenantpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-DeviceTenantRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-devicetenantrule",
+ "redirect_url": "/powershell/module/exchange/set-devicetenantrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Set-MobileDeviceMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mobiledevicemailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/set-mobiledevicemailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/devices/Test-ActiveSyncConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-activesyncconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-activesyncconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Disable-AddressListPaging.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-addresslistpaging",
+ "redirect_url": "/powershell/module/exchange/disable-addresslistpaging",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Enable-AddressListPaging.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-addresslistpaging",
+ "redirect_url": "/powershell/module/exchange/enable-addresslistpaging",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-AddressBookPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-addressbookpolicy",
+ "redirect_url": "/powershell/module/exchange/get-addressbookpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-addresslist",
+ "redirect_url": "/powershell/module/exchange/get-addresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-DetailsTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-detailstemplate",
+ "redirect_url": "/powershell/module/exchange/get-detailstemplate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-emailaddresspolicy",
+ "redirect_url": "/powershell/module/exchange/get-emailaddresspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-globaladdresslist",
+ "redirect_url": "/powershell/module/exchange/get-globaladdresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-OabVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-oabvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/get-oabvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Get-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-offlineaddressbook",
+ "redirect_url": "/powershell/module/exchange/get-offlineaddressbook",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Move-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/move-addresslist",
+ "redirect_url": "/powershell/module/exchange/move-addresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Move-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/move-offlineaddressbook",
+ "redirect_url": "/powershell/module/exchange/move-offlineaddressbook",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-AddressBookPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-addressbookpolicy",
+ "redirect_url": "/powershell/module/exchange/new-addressbookpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-addresslist",
+ "redirect_url": "/powershell/module/exchange/new-addresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-emailaddresspolicy",
+ "redirect_url": "/powershell/module/exchange/new-emailaddresspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-globaladdresslist",
+ "redirect_url": "/powershell/module/exchange/new-globaladdresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-OabVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-oabvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/new-oabvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/New-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-offlineaddressbook",
+ "redirect_url": "/powershell/module/exchange/new-offlineaddressbook",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-AddressBookPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-addressbookpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-addressbookpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-addresslist",
+ "redirect_url": "/powershell/module/exchange/remove-addresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-emailaddresspolicy",
+ "redirect_url": "/powershell/module/exchange/remove-emailaddresspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-globaladdresslist",
+ "redirect_url": "/powershell/module/exchange/remove-globaladdresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-OabVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-oabvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/remove-oabvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Remove-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-offlineaddressbook",
+ "redirect_url": "/powershell/module/exchange/remove-offlineaddressbook",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Restore-DetailsTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/restore-detailstemplate",
+ "redirect_url": "/powershell/module/exchange/restore-detailstemplate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-AddressBookPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-addressbookpolicy",
+ "redirect_url": "/powershell/module/exchange/set-addressbookpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-addresslist",
+ "redirect_url": "/powershell/module/exchange/set-addresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-DetailsTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-detailstemplate",
+ "redirect_url": "/powershell/module/exchange/set-detailstemplate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-emailaddresspolicy",
+ "redirect_url": "/powershell/module/exchange/set-emailaddresspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-globaladdresslist",
+ "redirect_url": "/powershell/module/exchange/set-globaladdresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-OabVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-oabvirtualdirectory",
+ "redirect_url": "/powershell/module/exchange/set-oabvirtualdirectory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Set-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-offlineaddressbook",
+ "redirect_url": "/powershell/module/exchange/set-offlineaddressbook",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-addresslist",
+ "redirect_url": "/powershell/module/exchange/update-addresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-emailaddresspolicy",
+ "redirect_url": "/powershell/module/exchange/update-emailaddresspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-globaladdresslist",
+ "redirect_url": "/powershell/module/exchange/update-globaladdresslist",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/email-addresses-and-address-books/Update-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-offlineaddressbook",
+ "redirect_url": "/powershell/module/exchange/update-offlineaddressbook",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Enable-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-exchangecertificate",
+ "redirect_url": "/powershell/module/exchange/enable-exchangecertificate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Export-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-exchangecertificate",
+ "redirect_url": "/powershell/module/exchange/export-exchangecertificate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-DataEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dataencryptionpolicy",
+ "redirect_url": "/powershell/module/exchange/get-dataencryptionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangecertificate",
+ "redirect_url": "/powershell/module/exchange/get-exchangecertificate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-IRMConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-irmconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-irmconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-OMEConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-omeconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-omeconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-OMEMessageStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-omemessagestatus",
+ "redirect_url": "/powershell/module/exchange/get-omemessagestatus",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-RMSTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-rmstemplate",
+ "redirect_url": "/powershell/module/exchange/get-rmstemplate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates",
+ "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-SmimeConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-smimeconfig",
+ "redirect_url": "/powershell/module/exchange/get-smimeconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Import-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-exchangecertificate",
+ "redirect_url": "/powershell/module/exchange/import-exchangecertificate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Import-RMSTrustedPublishingDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates",
+ "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/New-DataEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dataencryptionpolicy",
+ "redirect_url": "/powershell/module/exchange/new-dataencryptionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/New-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-exchangecertificate",
+ "redirect_url": "/powershell/module/exchange/new-exchangecertificate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/New-OMEConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-omeconfiguration",
+ "redirect_url": "/powershell/module/exchange/new-omeconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-exchangecertificate",
+ "redirect_url": "/powershell/module/exchange/remove-exchangecertificate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-OMEConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-omeconfiguration",
+ "redirect_url": "/powershell/module/exchange/remove-omeconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates",
+ "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-DataEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dataencryptionpolicy",
+ "redirect_url": "/powershell/module/exchange/set-dataencryptionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-IRMConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-irmconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-irmconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-OMEConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-omeconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-omeconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-OMEMessageRevocation.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-omemessagerevocation",
+ "redirect_url": "/powershell/module/exchange/set-omemessagerevocation",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-RMSTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-rmstemplate",
+ "redirect_url": "/powershell/module/exchange/set-rmstemplate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates",
+ "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-SmimeConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-smimeconfig",
+ "redirect_url": "/powershell/module/exchange/set-smimeconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Test-IRMConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-irmconfiguration",
+ "redirect_url": "/powershell/module/exchange/test-irmconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Add-FederatedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-federateddomain",
+ "redirect_url": "/powershell/module/exchange/add-federateddomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Disable-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-remotemailbox",
+ "redirect_url": "/powershell/module/exchange/disable-remotemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Enable-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-remotemailbox",
+ "redirect_url": "/powershell/module/exchange/enable-remotemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederatedDomainProof.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-federateddomainproof",
+ "redirect_url": "/powershell/module/exchange/get-federateddomainproof",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederatedOrganizationIdentifier.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-federatedorganizationidentifier",
+ "redirect_url": "/powershell/module/exchange/get-federatedorganizationidentifier",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederationInformation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-federationinformation",
+ "redirect_url": "/powershell/module/exchange/get-federationinformation",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-federationtrust",
+ "redirect_url": "/powershell/module/exchange/get-federationtrust",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hybridconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-hybridconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-HybridMailflow.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hybridmailflow",
+ "redirect_url": "/powershell/module/exchange/get-hybridmailflow",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-HybridMailflowDatacenterIPs.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hybridmailflowdatacenterips",
+ "redirect_url": "/powershell/module/exchange/get-hybridmailflowdatacenterips",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-IntraOrganizationConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-intraorganizationconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-intraorganizationconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-IntraOrganizationConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-intraorganizationconnector",
+ "redirect_url": "/powershell/module/exchange/get-intraorganizationconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-OnPremisesOrganization.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-onpremisesorganization",
+ "redirect_url": "/powershell/module/exchange/get-onpremisesorganization",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-PendingFederatedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-pendingfederateddomain",
+ "redirect_url": "/powershell/module/exchange/get-pendingfederateddomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Get-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-remotemailbox",
+ "redirect_url": "/powershell/module/exchange/get-remotemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-federationtrust",
+ "redirect_url": "/powershell/module/exchange/new-federationtrust",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hybridconfiguration",
+ "redirect_url": "/powershell/module/exchange/new-hybridconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-IntraOrganizationConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-intraorganizationconnector",
+ "redirect_url": "/powershell/module/exchange/new-intraorganizationconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-OnPremisesOrganization.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-onpremisesorganization",
+ "redirect_url": "/powershell/module/exchange/new-onpremisesorganization",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/New-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-remotemailbox",
+ "redirect_url": "/powershell/module/exchange/new-remotemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-FederatedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-federateddomain",
+ "redirect_url": "/powershell/module/exchange/remove-federateddomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-federationtrust",
+ "redirect_url": "/powershell/module/exchange/remove-federationtrust",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hybridconfiguration",
+ "redirect_url": "/powershell/module/exchange/remove-hybridconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-IntraOrganizationConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-intraorganizationconnector",
+ "redirect_url": "/powershell/module/exchange/remove-intraorganizationconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-OnPremisesOrganization.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-onpremisesorganization",
+ "redirect_url": "/powershell/module/exchange/remove-onpremisesorganization",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Remove-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-remotemailbox",
+ "redirect_url": "/powershell/module/exchange/remove-remotemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-FederatedOrganizationIdentifier.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-federatedorganizationidentifier",
+ "redirect_url": "/powershell/module/exchange/set-federatedorganizationidentifier",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-federationtrust",
+ "redirect_url": "/powershell/module/exchange/set-federationtrust",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hybridconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-hybridconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-HybridMailflow.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hybridmailflow",
+ "redirect_url": "/powershell/module/exchange/set-hybridmailflow",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-IntraOrganizationConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-intraorganizationconnector",
+ "redirect_url": "/powershell/module/exchange/set-intraorganizationconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-OnPremisesOrganization.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-onpremisesorganization",
+ "redirect_url": "/powershell/module/exchange/set-onpremisesorganization",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-PendingFederatedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-pendingfederateddomain",
+ "redirect_url": "/powershell/module/exchange/set-pendingfederateddomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Set-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-remotemailbox",
+ "redirect_url": "/powershell/module/exchange/set-remotemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Test-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-federationtrust",
+ "redirect_url": "/powershell/module/exchange/test-federationtrust",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Test-FederationTrustCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-federationtrustcertificate",
+ "redirect_url": "/powershell/module/exchange/test-federationtrustcertificate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Update-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-hybridconfiguration",
+ "redirect_url": "/powershell/module/exchange/update-hybridconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/federation-and-hybrid/Update-Recipient.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-recipient",
+ "redirect_url": "/powershell/module/exchange/update-recipient",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Add-ResubmitRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-resubmitrequest",
+ "redirect_url": "/powershell/module/exchange/add-resubmitrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Disable-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-transportagent",
+ "redirect_url": "/powershell/module/exchange/disable-transportagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Enable-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-transportagent",
+ "redirect_url": "/powershell/module/exchange/enable-transportagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Export-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-message",
+ "redirect_url": "/powershell/module/exchange/export-message",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-AcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-accepteddomain",
+ "redirect_url": "/powershell/module/exchange/get-accepteddomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-AddressRewriteEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-addressrewriteentry",
+ "redirect_url": "/powershell/module/exchange/get-addressrewriteentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-DeliveryAgentConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deliveryagentconnector",
+ "redirect_url": "/powershell/module/exchange/get-deliveryagentconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-EdgeSubscription.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-edgesubscription",
+ "redirect_url": "/powershell/module/exchange/get-edgesubscription",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-EdgeSyncServiceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-edgesyncserviceconfig",
+ "redirect_url": "/powershell/module/exchange/get-edgesyncserviceconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ForeignConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-foreignconnector",
+ "redirect_url": "/powershell/module/exchange/get-foreignconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-FrontendTransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-frontendtransportservice",
+ "redirect_url": "/powershell/module/exchange/get-frontendtransportservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-InboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-inboundconnector",
+ "redirect_url": "/powershell/module/exchange/get-inboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MailboxTransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxtransportservice",
+ "redirect_url": "/powershell/module/exchange/get-mailboxtransportservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-message",
+ "redirect_url": "/powershell/module/exchange/get-message",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTrace.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetrace",
+ "redirect_url": "/powershell/module/exchange/get-messagetrace",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTraceDetail.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetracedetail",
+ "redirect_url": "/powershell/module/exchange/get-messagetracedetail",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTrackingLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetrackinglog",
+ "redirect_url": "/powershell/module/exchange/get-messagetrackinglog",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-MessageTrackingReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetrackingreport",
+ "redirect_url": "/powershell/module/exchange/get-messagetrackingreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-NetworkConnectionInfo.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-networkconnectioninfo",
+ "redirect_url": "/powershell/module/exchange/get-networkconnectioninfo",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outboundconnector",
+ "redirect_url": "/powershell/module/exchange/get-outboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-Queue.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-queue",
+ "redirect_url": "/powershell/module/exchange/get-queue",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-QueueDigest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-queuedigest",
+ "redirect_url": "/powershell/module/exchange/get-queuedigest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ReceiveConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-receiveconnector",
+ "redirect_url": "/powershell/module/exchange/get-receiveconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-RemoteDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-remotedomain",
+ "redirect_url": "/powershell/module/exchange/get-remotedomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-ResubmitRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-resubmitrequest",
+ "redirect_url": "/powershell/module/exchange/get-resubmitrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-RoutingGroupConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-routinggroupconnector",
+ "redirect_url": "/powershell/module/exchange/get-routinggroupconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-SendConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sendconnector",
+ "redirect_url": "/powershell/module/exchange/get-sendconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-SystemMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-systemmessage",
+ "redirect_url": "/powershell/module/exchange/get-systemmessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportagent",
+ "redirect_url": "/powershell/module/exchange/get-transportagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportconfig",
+ "redirect_url": "/powershell/module/exchange/get-transportconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportPipeline.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportpipeline",
+ "redirect_url": "/powershell/module/exchange/get-transportpipeline",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportserver",
+ "redirect_url": "/powershell/module/exchange/get-transportserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-TransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportservice",
+ "redirect_url": "/powershell/module/exchange/get-transportservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Get-X400AuthoritativeDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-x400authoritativedomain",
+ "redirect_url": "/powershell/module/exchange/get-x400authoritativedomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Install-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/install-transportagent",
+ "redirect_url": "/powershell/module/exchange/install-transportagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-AcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-accepteddomain",
+ "redirect_url": "/powershell/module/exchange/new-accepteddomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-AddressRewriteEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-addressrewriteentry",
+ "redirect_url": "/powershell/module/exchange/new-addressrewriteentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-DeliveryAgentConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deliveryagentconnector",
+ "redirect_url": "/powershell/module/exchange/new-deliveryagentconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-EdgeSubscription.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-edgesubscription",
+ "redirect_url": "/powershell/module/exchange/new-edgesubscription",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-EdgeSyncServiceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-edgesyncserviceconfig",
+ "redirect_url": "/powershell/module/exchange/new-edgesyncserviceconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-ForeignConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-foreignconnector",
+ "redirect_url": "/powershell/module/exchange/new-foreignconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-InboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-inboundconnector",
+ "redirect_url": "/powershell/module/exchange/new-inboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-outboundconnector",
+ "redirect_url": "/powershell/module/exchange/new-outboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-ReceiveConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-receiveconnector",
+ "redirect_url": "/powershell/module/exchange/new-receiveconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-RemoteDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-remotedomain",
+ "redirect_url": "/powershell/module/exchange/new-remotedomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-RoutingGroupConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-routinggroupconnector",
+ "redirect_url": "/powershell/module/exchange/new-routinggroupconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-SendConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sendconnector",
+ "redirect_url": "/powershell/module/exchange/new-sendconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-SystemMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-systemmessage",
+ "redirect_url": "/powershell/module/exchange/new-systemmessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/New-X400AuthoritativeDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-x400authoritativedomain",
+ "redirect_url": "/powershell/module/exchange/new-x400authoritativedomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Redirect-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/redirect-message",
+ "redirect_url": "/powershell/module/exchange/redirect-message",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-AcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-accepteddomain",
+ "redirect_url": "/powershell/module/exchange/remove-accepteddomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-AddressRewriteEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-addressrewriteentry",
+ "redirect_url": "/powershell/module/exchange/remove-addressrewriteentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-DeliveryAgentConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deliveryagentconnector",
+ "redirect_url": "/powershell/module/exchange/remove-deliveryagentconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-EdgeSubscription.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-edgesubscription",
+ "redirect_url": "/powershell/module/exchange/remove-edgesubscription",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ForeignConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-foreignconnector",
+ "redirect_url": "/powershell/module/exchange/remove-foreignconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-InboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-inboundconnector",
+ "redirect_url": "/powershell/module/exchange/remove-inboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-message",
+ "redirect_url": "/powershell/module/exchange/remove-message",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-outboundconnector",
+ "redirect_url": "/powershell/module/exchange/remove-outboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ReceiveConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-receiveconnector",
+ "redirect_url": "/powershell/module/exchange/remove-receiveconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-RemoteDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-remotedomain",
+ "redirect_url": "/powershell/module/exchange/remove-remotedomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-ResubmitRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-resubmitrequest",
+ "redirect_url": "/powershell/module/exchange/remove-resubmitrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-RoutingGroupConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-routinggroupconnector",
+ "redirect_url": "/powershell/module/exchange/remove-routinggroupconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-SendConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-sendconnector",
+ "redirect_url": "/powershell/module/exchange/remove-sendconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-SystemMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-systemmessage",
+ "redirect_url": "/powershell/module/exchange/remove-systemmessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Remove-X400AuthoritativeDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-x400authoritativedomain",
+ "redirect_url": "/powershell/module/exchange/remove-x400authoritativedomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Resume-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-message",
+ "redirect_url": "/powershell/module/exchange/resume-message",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Resume-Queue.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-queue",
+ "redirect_url": "/powershell/module/exchange/resume-queue",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Retry-Queue.md",
- "redirect_url": "/powershell/module/exchangepowershell/retry-queue",
+ "redirect_url": "/powershell/module/exchange/retry-queue",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Search-MessageTrackingReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-messagetrackingreport",
+ "redirect_url": "/powershell/module/exchange/search-messagetrackingreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-AcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-accepteddomain",
+ "redirect_url": "/powershell/module/exchange/set-accepteddomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-AddressRewriteEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-addressrewriteentry",
+ "redirect_url": "/powershell/module/exchange/set-addressrewriteentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-DeliveryAgentConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deliveryagentconnector",
+ "redirect_url": "/powershell/module/exchange/set-deliveryagentconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-EdgeSyncServiceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-edgesyncserviceconfig",
+ "redirect_url": "/powershell/module/exchange/set-edgesyncserviceconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-ForeignConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-foreignconnector",
+ "redirect_url": "/powershell/module/exchange/set-foreignconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-FrontendTransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-frontendtransportservice",
+ "redirect_url": "/powershell/module/exchange/set-frontendtransportservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-InboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-inboundconnector",
+ "redirect_url": "/powershell/module/exchange/set-inboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-MailboxTransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxtransportservice",
+ "redirect_url": "/powershell/module/exchange/set-mailboxtransportservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-outboundconnector",
+ "redirect_url": "/powershell/module/exchange/set-outboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-ReceiveConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-receiveconnector",
+ "redirect_url": "/powershell/module/exchange/set-receiveconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-RemoteDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-remotedomain",
+ "redirect_url": "/powershell/module/exchange/set-remotedomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-ResubmitRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-resubmitrequest",
+ "redirect_url": "/powershell/module/exchange/set-resubmitrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-RoutingGroupConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-routinggroupconnector",
+ "redirect_url": "/powershell/module/exchange/set-routinggroupconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-SendConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sendconnector",
+ "redirect_url": "/powershell/module/exchange/set-sendconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-SystemMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-systemmessage",
+ "redirect_url": "/powershell/module/exchange/set-systemmessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportagent",
+ "redirect_url": "/powershell/module/exchange/set-transportagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportconfig",
+ "redirect_url": "/powershell/module/exchange/set-transportconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportserver",
+ "redirect_url": "/powershell/module/exchange/set-transportserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-TransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportservice",
+ "redirect_url": "/powershell/module/exchange/set-transportservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Set-X400AuthoritativeDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-x400authoritativedomain",
+ "redirect_url": "/powershell/module/exchange/set-x400authoritativedomain",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Start-EdgeSynchronization.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-edgesynchronization",
+ "redirect_url": "/powershell/module/exchange/start-edgesynchronization",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Start-HistoricalSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-historicalsearch",
+ "redirect_url": "/powershell/module/exchange/start-historicalsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Stop-HistoricalSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-historicalsearch",
+ "redirect_url": "/powershell/module/exchange/stop-historicalsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Suspend-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-message",
+ "redirect_url": "/powershell/module/exchange/suspend-message",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Suspend-Queue.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-queue",
+ "redirect_url": "/powershell/module/exchange/suspend-queue",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Test-EdgeSynchronization.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-edgesynchronization",
+ "redirect_url": "/powershell/module/exchange/test-edgesynchronization",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Test-Mailflow.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-mailflow",
+ "redirect_url": "/powershell/module/exchange/test-mailflow",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Test-SmtpConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-smtpconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-smtpconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Uninstall-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/uninstall-transportagent",
+ "redirect_url": "/powershell/module/exchange/uninstall-transportagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mail-flow/Validate-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/validate-outboundconnector",
+ "redirect_url": "/powershell/module/exchange/validate-outboundconnector",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Clean-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/clean-mailboxdatabase",
+ "redirect_url": "/powershell/module/exchange/clean-mailboxdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Disable-MailboxQuarantine.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailboxquarantine",
+ "redirect_url": "/powershell/module/exchange/disable-mailboxquarantine",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Disable-MetaCacheDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-metacachedatabase",
+ "redirect_url": "/powershell/module/exchange/disable-metacachedatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Dismount-Database.md",
- "redirect_url": "/powershell/module/exchangepowershell/dismount-database",
+ "redirect_url": "/powershell/module/exchange/dismount-database",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Enable-MailboxQuarantine.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailboxquarantine",
+ "redirect_url": "/powershell/module/exchange/enable-mailboxquarantine",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Enable-MetaCacheDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-metacachedatabase",
+ "redirect_url": "/powershell/module/exchange/enable-metacachedatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-FailedContentIndexDocuments.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-failedcontentindexdocuments",
+ "redirect_url": "/powershell/module/exchange/get-failedcontentindexdocuments",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxdatabase",
+ "redirect_url": "/powershell/module/exchange/get-mailboxdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-MailboxRepairRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrepairrequest",
+ "redirect_url": "/powershell/module/exchange/get-mailboxrepairrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-MailboxServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxserver",
+ "redirect_url": "/powershell/module/exchange/get-mailboxserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-SearchDocumentFormat.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-searchdocumentformat",
+ "redirect_url": "/powershell/module/exchange/get-searchdocumentformat",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Get-StoreUsageStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-storeusagestatistics",
+ "redirect_url": "/powershell/module/exchange/get-storeusagestatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Mount-Database.md",
- "redirect_url": "/powershell/module/exchangepowershell/mount-database",
+ "redirect_url": "/powershell/module/exchange/mount-database",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Move-DatabasePath.md",
- "redirect_url": "/powershell/module/exchangepowershell/move-databasepath",
+ "redirect_url": "/powershell/module/exchange/move-databasepath",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/New-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxdatabase",
+ "redirect_url": "/powershell/module/exchange/new-mailboxdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/New-MailboxRepairRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxrepairrequest",
+ "redirect_url": "/powershell/module/exchange/new-mailboxrepairrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/New-SearchDocumentFormat.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-searchdocumentformat",
+ "redirect_url": "/powershell/module/exchange/new-searchdocumentformat",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxdatabase",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-MailboxRepairRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxrepairrequest",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxrepairrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-SearchDocumentFormat.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-searchdocumentformat",
+ "redirect_url": "/powershell/module/exchange/remove-searchdocumentformat",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Remove-StoreMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-storemailbox",
+ "redirect_url": "/powershell/module/exchange/remove-storemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Set-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxdatabase",
+ "redirect_url": "/powershell/module/exchange/set-mailboxdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Set-MailboxServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxserver",
+ "redirect_url": "/powershell/module/exchange/set-mailboxserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Set-SearchDocumentFormat.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-searchdocumentformat",
+ "redirect_url": "/powershell/module/exchange/set-searchdocumentformat",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Test-AssistantHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-assistanthealth",
+ "redirect_url": "/powershell/module/exchange/test-assistanthealth",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Test-ExchangeSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-exchangesearch",
+ "redirect_url": "/powershell/module/exchange/test-exchangesearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Test-MRSHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-mrshealth",
+ "redirect_url": "/powershell/module/exchange/test-mrshealth",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Update-DatabaseSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-databaseschema",
+ "redirect_url": "/powershell/module/exchange/update-databaseschema",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Update-FileDistributionService.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-filedistributionservice",
+ "redirect_url": "/powershell/module/exchange/update-filedistributionservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailbox-databases-and-servers/Update-StoreMailboxState.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-storemailboxstate",
+ "redirect_url": "/powershell/module/exchange/update-storemailboxstate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Add-MailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-mailboxfolderpermission",
+ "redirect_url": "/powershell/module/exchange/add-mailboxfolderpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Add-MailboxPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-mailboxpermission",
+ "redirect_url": "/powershell/module/exchange/add-mailboxpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Add-RecipientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-recipientpermission",
+ "redirect_url": "/powershell/module/exchange/add-recipientpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Connect-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/connect-mailbox",
+ "redirect_url": "/powershell/module/exchange/connect-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-app",
+ "redirect_url": "/powershell/module/exchange/disable-app",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-inboxrule",
+ "redirect_url": "/powershell/module/exchange/disable-inboxrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailbox",
+ "redirect_url": "/powershell/module/exchange/disable-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-ServiceEmailChannel.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-serviceemailchannel",
+ "redirect_url": "/powershell/module/exchange/disable-serviceemailchannel",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Disable-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-sweeprule",
+ "redirect_url": "/powershell/module/exchange/disable-sweeprule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-app",
+ "redirect_url": "/powershell/module/exchange/enable-app",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-inboxrule",
+ "redirect_url": "/powershell/module/exchange/enable-inboxrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailbox",
+ "redirect_url": "/powershell/module/exchange/enable-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-ServiceEmailChannel.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-serviceemailchannel",
+ "redirect_url": "/powershell/module/exchange/enable-serviceemailchannel",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Enable-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-sweeprule",
+ "redirect_url": "/powershell/module/exchange/enable-sweeprule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Export-MailboxDiagnosticLogs.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-mailboxdiagnosticlogs",
+ "redirect_url": "/powershell/module/exchange/export-mailboxdiagnosticlogs",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Export-RecipientDataProperty.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-recipientdataproperty",
+ "redirect_url": "/powershell/module/exchange/export-recipientdataproperty",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-app",
+ "redirect_url": "/powershell/module/exchange/get-app",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticAnalysis.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticanalysis",
+ "redirect_url": "/powershell/module/exchange/get-calendardiagnosticanalysis",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticlog",
+ "redirect_url": "/powershell/module/exchange/get-calendardiagnosticlog",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarDiagnosticObjects.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticobjects",
+ "redirect_url": "/powershell/module/exchange/get-calendardiagnosticobjects",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarNotification.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendarnotification",
+ "redirect_url": "/powershell/module/exchange/get-calendarnotification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-CalendarProcessing.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendarprocessing",
+ "redirect_url": "/powershell/module/exchange/get-calendarprocessing",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Clutter.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clutter",
+ "redirect_url": "/powershell/module/exchange/get-clutter",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-FocusedInbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-focusedinbox",
+ "redirect_url": "/powershell/module/exchange/get-focusedinbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-inboxrule",
+ "redirect_url": "/powershell/module/exchange/get-inboxrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailbox",
+ "redirect_url": "/powershell/module/exchange/get-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxAutoReplyConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxautoreplyconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-mailboxautoreplyconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxCalendarFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxcalendarfolder",
+ "redirect_url": "/powershell/module/exchange/get-mailboxcalendarfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxexportrequest",
+ "redirect_url": "/powershell/module/exchange/get-mailboxexportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxExportRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxexportrequeststatistics",
+ "redirect_url": "/powershell/module/exchange/get-mailboxexportrequeststatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolder",
+ "redirect_url": "/powershell/module/exchange/get-mailboxfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolderpermission",
+ "redirect_url": "/powershell/module/exchange/get-mailboxfolderpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxFolderStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolderstatistics",
+ "redirect_url": "/powershell/module/exchange/get-mailboxfolderstatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboximportrequest",
+ "redirect_url": "/powershell/module/exchange/get-mailboximportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxImportRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboximportrequeststatistics",
+ "redirect_url": "/powershell/module/exchange/get-mailboximportrequeststatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxLocation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxlocation",
+ "redirect_url": "/powershell/module/exchange/get-mailboxlocation",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxpermission",
+ "redirect_url": "/powershell/module/exchange/get-mailboxpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxplan",
+ "redirect_url": "/powershell/module/exchange/get-mailboxplan",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrestorerequest",
+ "redirect_url": "/powershell/module/exchange/get-mailboxrestorerequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxRestoreRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrestorerequeststatistics",
+ "redirect_url": "/powershell/module/exchange/get-mailboxrestorerequeststatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxSentItemsConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxsentitemsconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-mailboxsentitemsconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxstatistics",
+ "redirect_url": "/powershell/module/exchange/get-mailboxstatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MailboxUserConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxuserconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-mailboxuserconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-MessageCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagecategory",
+ "redirect_url": "/powershell/module/exchange/get-messagecategory",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-Place.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-place",
+ "redirect_url": "/powershell/module/exchange/get-place",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-RecipientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recipientpermission",
+ "redirect_url": "/powershell/module/exchange/get-recipientpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-RecoverableItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recoverableitems",
+ "redirect_url": "/powershell/module/exchange/get-recoverableitems",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-ResourceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-resourceconfig",
+ "redirect_url": "/powershell/module/exchange/get-resourceconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sweeprule",
+ "redirect_url": "/powershell/module/exchange/get-sweeprule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Get-UserPhoto.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-userphoto",
+ "redirect_url": "/powershell/module/exchange/get-userphoto",
"redirect_document_id": false
},
{
@@ -3152,1987 +3152,1987 @@
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Import-RecipientDataProperty.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-recipientdataproperty",
+ "redirect_url": "/powershell/module/exchange/import-recipientdataproperty",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-app",
+ "redirect_url": "/powershell/module/exchange/new-app",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-inboxrule",
+ "redirect_url": "/powershell/module/exchange/new-inboxrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailbox",
+ "redirect_url": "/powershell/module/exchange/new-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxexportrequest",
+ "redirect_url": "/powershell/module/exchange/new-mailboxexportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxfolder",
+ "redirect_url": "/powershell/module/exchange/new-mailboxfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboximportrequest",
+ "redirect_url": "/powershell/module/exchange/new-mailboximportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxrestorerequest",
+ "redirect_url": "/powershell/module/exchange/new-mailboxrestorerequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-MailMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailmessage",
+ "redirect_url": "/powershell/module/exchange/new-mailmessage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sitemailbox",
+ "redirect_url": "/powershell/module/exchange/new-sitemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/New-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sweeprule",
+ "redirect_url": "/powershell/module/exchange/new-sweeprule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-app",
+ "redirect_url": "/powershell/module/exchange/remove-app",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-CalendarEvents.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-calendarevents",
+ "redirect_url": "/powershell/module/exchange/remove-calendarevents",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-inboxrule",
+ "redirect_url": "/powershell/module/exchange/remove-inboxrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailbox",
+ "redirect_url": "/powershell/module/exchange/remove-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxexportrequest",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxexportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxfolderpermission",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxfolderpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboximportrequest",
+ "redirect_url": "/powershell/module/exchange/remove-mailboximportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxpermission",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxrestorerequest",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxrestorerequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-MailboxUserConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxuserconfiguration",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxuserconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-RecipientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-recipientpermission",
+ "redirect_url": "/powershell/module/exchange/remove-recipientpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-sweeprule",
+ "redirect_url": "/powershell/module/exchange/remove-sweeprule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Remove-UserPhoto.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-userphoto",
+ "redirect_url": "/powershell/module/exchange/remove-userphoto",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Restore-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/restore-mailbox",
+ "redirect_url": "/powershell/module/exchange/restore-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Restore-RecoverableItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/restore-recoverableitems",
+ "redirect_url": "/powershell/module/exchange/restore-recoverableitems",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxexportrequest",
+ "redirect_url": "/powershell/module/exchange/resume-mailboxexportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-mailboximportrequest",
+ "redirect_url": "/powershell/module/exchange/resume-mailboximportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Resume-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxrestorerequest",
+ "redirect_url": "/powershell/module/exchange/resume-mailboxrestorerequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Search-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-mailbox",
+ "redirect_url": "/powershell/module/exchange/search-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-app",
+ "redirect_url": "/powershell/module/exchange/set-app",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-CalendarNotification.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-calendarnotification",
+ "redirect_url": "/powershell/module/exchange/set-calendarnotification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-CalendarProcessing.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-calendarprocessing",
+ "redirect_url": "/powershell/module/exchange/set-calendarprocessing",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Clutter.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clutter",
+ "redirect_url": "/powershell/module/exchange/set-clutter",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-FocusedInbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-focusedinbox",
+ "redirect_url": "/powershell/module/exchange/set-focusedinbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-inboxrule",
+ "redirect_url": "/powershell/module/exchange/set-inboxrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailbox",
+ "redirect_url": "/powershell/module/exchange/set-mailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxAutoReplyConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxautoreplyconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-mailboxautoreplyconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxCalendarFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxcalendarfolder",
+ "redirect_url": "/powershell/module/exchange/set-mailboxcalendarfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxexportrequest",
+ "redirect_url": "/powershell/module/exchange/set-mailboxexportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxfolderpermission",
+ "redirect_url": "/powershell/module/exchange/set-mailboxfolderpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboximportrequest",
+ "redirect_url": "/powershell/module/exchange/set-mailboximportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxplan",
+ "redirect_url": "/powershell/module/exchange/set-mailboxplan",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxrestorerequest",
+ "redirect_url": "/powershell/module/exchange/set-mailboxrestorerequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-MailboxSentItemsConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxsentitemsconfiguration",
+ "redirect_url": "/powershell/module/exchange/set-mailboxsentitemsconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-Place.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-place",
+ "redirect_url": "/powershell/module/exchange/set-place",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-ResourceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-resourceconfig",
+ "redirect_url": "/powershell/module/exchange/set-resourceconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sweeprule",
+ "redirect_url": "/powershell/module/exchange/set-sweeprule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Set-UserPhoto.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-userphoto",
+ "redirect_url": "/powershell/module/exchange/set-userphoto",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxexportrequest",
+ "redirect_url": "/powershell/module/exchange/suspend-mailboxexportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboximportrequest",
+ "redirect_url": "/powershell/module/exchange/suspend-mailboximportrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Suspend-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxrestorerequest",
+ "redirect_url": "/powershell/module/exchange/suspend-mailboxrestorerequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Test-MAPIConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-mapiconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-mapiconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/mailboxes/Undo-SoftDeletedMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/undo-softdeletedmailbox",
+ "redirect_url": "/powershell/module/exchange/undo-softdeletedmailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Complete-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/complete-migrationbatch",
+ "redirect_url": "/powershell/module/exchange/complete-migrationbatch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Export-MigrationReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-migrationreport",
+ "redirect_url": "/powershell/module/exchange/export-migrationreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationbatch",
+ "redirect_url": "/powershell/module/exchange/get-migrationbatch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationconfig",
+ "redirect_url": "/powershell/module/exchange/get-migrationconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationEndpoint.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationendpoint",
+ "redirect_url": "/powershell/module/exchange/get-migrationendpoint",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationstatistics",
+ "redirect_url": "/powershell/module/exchange/get-migrationstatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationuser",
+ "redirect_url": "/powershell/module/exchange/get-migrationuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MigrationUserStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationuserstatistics",
+ "redirect_url": "/powershell/module/exchange/get-migrationuserstatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-moverequest",
+ "redirect_url": "/powershell/module/exchange/get-moverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-MoveRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-moverequeststatistics",
+ "redirect_url": "/powershell/module/exchange/get-moverequeststatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxmigrationrequest",
+ "redirect_url": "/powershell/module/exchange/get-publicfoldermailboxmigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMailboxMigrationRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxmigrationrequeststatistics",
+ "redirect_url": "/powershell/module/exchange/get-publicfoldermailboxmigrationrequeststatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermigrationrequest",
+ "redirect_url": "/powershell/module/exchange/get-publicfoldermigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMigrationRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermigrationrequeststatistics",
+ "redirect_url": "/powershell/module/exchange/get-publicfoldermigrationrequeststatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermoverequest",
+ "redirect_url": "/powershell/module/exchange/get-publicfoldermoverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Get-PublicFolderMoveRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermoverequeststatistics",
+ "redirect_url": "/powershell/module/exchange/get-publicfoldermoverequeststatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/New-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-migrationbatch",
+ "redirect_url": "/powershell/module/exchange/new-migrationbatch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/New-MigrationEndpoint.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-migrationendpoint",
+ "redirect_url": "/powershell/module/exchange/new-migrationendpoint",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/New-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-moverequest",
+ "redirect_url": "/powershell/module/exchange/new-moverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/New-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfoldermigrationrequest",
+ "redirect_url": "/powershell/module/exchange/new-publicfoldermigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/New-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfoldermoverequest",
+ "redirect_url": "/powershell/module/exchange/new-publicfoldermoverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-migrationbatch",
+ "redirect_url": "/powershell/module/exchange/remove-migrationbatch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MigrationEndpoint.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-migrationendpoint",
+ "redirect_url": "/powershell/module/exchange/remove-migrationendpoint",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-migrationuser",
+ "redirect_url": "/powershell/module/exchange/remove-migrationuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-moverequest",
+ "redirect_url": "/powershell/module/exchange/remove-moverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-PublicFolderMailboxMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermailboxmigrationrequest",
+ "redirect_url": "/powershell/module/exchange/remove-publicfoldermailboxmigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermigrationrequest",
+ "redirect_url": "/powershell/module/exchange/remove-publicfoldermigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Remove-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermoverequest",
+ "redirect_url": "/powershell/module/exchange/remove-publicfoldermoverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Resume-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-moverequest",
+ "redirect_url": "/powershell/module/exchange/resume-moverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Resume-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-publicfoldermigrationrequest",
+ "redirect_url": "/powershell/module/exchange/resume-publicfoldermigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Resume-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-publicfoldermoverequest",
+ "redirect_url": "/powershell/module/exchange/resume-publicfoldermoverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-migrationbatch",
+ "redirect_url": "/powershell/module/exchange/set-migrationbatch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-migrationconfig",
+ "redirect_url": "/powershell/module/exchange/set-migrationconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationEndpoint.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-migrationendpoint",
+ "redirect_url": "/powershell/module/exchange/set-migrationendpoint",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-migrationuser",
+ "redirect_url": "/powershell/module/exchange/set-migrationuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-moverequest",
+ "redirect_url": "/powershell/module/exchange/set-moverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-publicfoldermigrationrequest",
+ "redirect_url": "/powershell/module/exchange/set-publicfoldermigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Set-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-publicfoldermoverequest",
+ "redirect_url": "/powershell/module/exchange/set-publicfoldermoverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Start-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-migrationbatch",
+ "redirect_url": "/powershell/module/exchange/start-migrationbatch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Start-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-migrationuser",
+ "redirect_url": "/powershell/module/exchange/start-migrationuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Stop-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-migrationbatch",
+ "redirect_url": "/powershell/module/exchange/stop-migrationbatch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Stop-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-migrationuser",
+ "redirect_url": "/powershell/module/exchange/stop-migrationuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-moverequest",
+ "redirect_url": "/powershell/module/exchange/suspend-moverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-PublicFolderMailboxMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermailboxmigrationrequest",
+ "redirect_url": "/powershell/module/exchange/suspend-publicfoldermailboxmigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermigrationrequest",
+ "redirect_url": "/powershell/module/exchange/suspend-publicfoldermigrationrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Suspend-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermoverequest",
+ "redirect_url": "/powershell/module/exchange/suspend-publicfoldermoverequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/move-and-migration/Test-MigrationServerAvailability.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-migrationserveravailability",
+ "redirect_url": "/powershell/module/exchange/test-migrationserveravailability",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Disable-CmdletExtensionAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-cmdletextensionagent",
+ "redirect_url": "/powershell/module/exchange/disable-cmdletextensionagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Enable-CmdletExtensionAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-cmdletextensionagent",
+ "redirect_url": "/powershell/module/exchange/enable-cmdletextensionagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Enable-OrganizationCustomization.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-organizationcustomization",
+ "redirect_url": "/powershell/module/exchange/enable-organizationcustomization",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-AccessToCustomerDataRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-accesstocustomerdatarequest",
+ "redirect_url": "/powershell/module/exchange/get-accesstocustomerdatarequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-applicationaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/get-applicationaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-AuthConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-authconfig",
+ "redirect_url": "/powershell/module/exchange/get-authconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-AuthenticationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-authenticationpolicy",
+ "redirect_url": "/powershell/module/exchange/get-authenticationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-AuthServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-authserver",
+ "redirect_url": "/powershell/module/exchange/get-authserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-CmdletExtensionAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-cmdletextensionagent",
+ "redirect_url": "/powershell/module/exchange/get-cmdletextensionagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeAssistanceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangeassistanceconfig",
+ "redirect_url": "/powershell/module/exchange/get-exchangeassistanceconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeDiagnosticInfo.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangediagnosticinfo",
+ "redirect_url": "/powershell/module/exchange/get-exchangediagnosticinfo",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserver",
+ "redirect_url": "/powershell/module/exchange/get-exchangeserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServerAccessLicense.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserveraccesslicense",
+ "redirect_url": "/powershell/module/exchange/get-exchangeserveraccesslicense",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeServerAccessLicenseUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserveraccesslicenseuser",
+ "redirect_url": "/powershell/module/exchange/get-exchangeserveraccesslicenseuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-ExchangeSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangesettings",
+ "redirect_url": "/powershell/module/exchange/get-exchangesettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-Notification.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-notification",
+ "redirect_url": "/powershell/module/exchange/get-notification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-OrganizationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-organizationconfig",
+ "redirect_url": "/powershell/module/exchange/get-organizationconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-PartnerApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-partnerapplication",
+ "redirect_url": "/powershell/module/exchange/get-partnerapplication",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-PerimeterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-perimeterconfig",
+ "redirect_url": "/powershell/module/exchange/get-perimeterconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Get-SettingOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-settingoverride",
+ "redirect_url": "/powershell/module/exchange/get-settingoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/New-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-applicationaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/new-applicationaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/New-AuthenticationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-authenticationpolicy",
+ "redirect_url": "/powershell/module/exchange/new-authenticationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/New-AuthServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-authserver",
+ "redirect_url": "/powershell/module/exchange/new-authserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/New-ExchangeSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-exchangesettings",
+ "redirect_url": "/powershell/module/exchange/new-exchangesettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/New-PartnerApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-partnerapplication",
+ "redirect_url": "/powershell/module/exchange/new-partnerapplication",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/New-SettingOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-settingoverride",
+ "redirect_url": "/powershell/module/exchange/new-settingoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Remove-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-applicationaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/remove-applicationaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Remove-AuthenticationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-authenticationpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-authenticationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Remove-AuthServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-authserver",
+ "redirect_url": "/powershell/module/exchange/remove-authserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Remove-PartnerApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-partnerapplication",
+ "redirect_url": "/powershell/module/exchange/remove-partnerapplication",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Remove-SettingOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-settingoverride",
+ "redirect_url": "/powershell/module/exchange/remove-settingoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-AccessToCustomerDataRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-accesstocustomerdatarequest",
+ "redirect_url": "/powershell/module/exchange/set-accesstocustomerdatarequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-applicationaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/set-applicationaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-AuthConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-authconfig",
+ "redirect_url": "/powershell/module/exchange/set-authconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-AuthenticationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-authenticationpolicy",
+ "redirect_url": "/powershell/module/exchange/set-authenticationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-AuthServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-authserver",
+ "redirect_url": "/powershell/module/exchange/set-authserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-CmdletExtensionAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-cmdletextensionagent",
+ "redirect_url": "/powershell/module/exchange/set-cmdletextensionagent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeAssistanceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exchangeassistanceconfig",
+ "redirect_url": "/powershell/module/exchange/set-exchangeassistanceconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exchangeserver",
+ "redirect_url": "/powershell/module/exchange/set-exchangeserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-ExchangeSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exchangesettings",
+ "redirect_url": "/powershell/module/exchange/set-exchangesettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-Notification.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-notification",
+ "redirect_url": "/powershell/module/exchange/set-notification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-OrganizationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-organizationconfig",
+ "redirect_url": "/powershell/module/exchange/set-organizationconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-PartnerApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-partnerapplication",
+ "redirect_url": "/powershell/module/exchange/set-partnerapplication",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-PerimeterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-perimeterconfig",
+ "redirect_url": "/powershell/module/exchange/set-perimeterconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Set-SettingOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-settingoverride",
+ "redirect_url": "/powershell/module/exchange/set-settingoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Test-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-applicationaccesspolicy",
+ "redirect_url": "/powershell/module/exchange/test-applicationaccesspolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Test-OAuthConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-oauthconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-oauthconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Test-SystemHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-systemhealth",
+ "redirect_url": "/powershell/module/exchange/test-systemhealth",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/organization/Update-ExchangeHelp.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-exchangehelp",
+ "redirect_url": "/powershell/module/exchange/update-exchangehelp",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-JournalArchiving.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-journalarchiving",
+ "redirect_url": "/powershell/module/exchange/disable-journalarchiving",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-journalrule",
+ "redirect_url": "/powershell/module/exchange/disable-journalrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-outlookprotectionrule",
+ "redirect_url": "/powershell/module/exchange/disable-outlookprotectionrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Disable-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-transportrule",
+ "redirect_url": "/powershell/module/exchange/disable-transportrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Enable-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-journalrule",
+ "redirect_url": "/powershell/module/exchange/enable-journalrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Enable-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-outlookprotectionrule",
+ "redirect_url": "/powershell/module/exchange/enable-outlookprotectionrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Enable-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-transportrule",
+ "redirect_url": "/powershell/module/exchange/enable-transportrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Export-JournalRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-journalrulecollection",
+ "redirect_url": "/powershell/module/exchange/export-journalrulecollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Export-TransportRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-transportrulecollection",
+ "redirect_url": "/powershell/module/exchange/export-transportrulecollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-ActivityAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activityalert",
+ "redirect_url": "/powershell/module/exchange/get-activityalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-AdministrativeUnit.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-administrativeunit",
+ "redirect_url": "/powershell/module/exchange/get-administrativeunit",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-InformationBarrierPoliciesApplicationStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierpoliciesapplicationstatus",
+ "redirect_url": "/powershell/module/exchange/get-informationbarrierpoliciesapplicationstatus",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-InformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierpolicy",
+ "redirect_url": "/powershell/module/exchange/get-informationbarrierpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-InformationBarrierRecipientStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierrecipientstatus",
+ "redirect_url": "/powershell/module/exchange/get-informationbarrierrecipientstatus",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-journalrule",
+ "redirect_url": "/powershell/module/exchange/get-journalrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-Label.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-label",
+ "redirect_url": "/powershell/module/exchange/get-label",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-LabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-labelpolicy",
+ "redirect_url": "/powershell/module/exchange/get-labelpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-MessageClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messageclassification",
+ "redirect_url": "/powershell/module/exchange/get-messageclassification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-OrganizationSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-organizationsegment",
+ "redirect_url": "/powershell/module/exchange/get-organizationsegment",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outlookprotectionrule",
+ "redirect_url": "/powershell/module/exchange/get-outlookprotectionrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-ProtectionAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert",
+ "redirect_url": "/powershell/module/exchange/get-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-SupervisoryReviewPolicyV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewpolicyv2",
+ "redirect_url": "/powershell/module/exchange/get-supervisoryreviewpolicyv2",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-SupervisoryReviewRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewrule",
+ "redirect_url": "/powershell/module/exchange/get-supervisoryreviewrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportrule",
+ "redirect_url": "/powershell/module/exchange/get-transportrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-TransportRuleAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportruleaction",
+ "redirect_url": "/powershell/module/exchange/get-transportruleaction",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Get-TransportRulePredicate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportrulepredicate",
+ "redirect_url": "/powershell/module/exchange/get-transportrulepredicate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Import-JournalRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-journalrulecollection",
+ "redirect_url": "/powershell/module/exchange/import-journalrulecollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Import-TransportRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-transportrulecollection",
+ "redirect_url": "/powershell/module/exchange/import-transportrulecollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Install-UnifiedCompliancePrerequisite.md",
- "redirect_url": "/powershell/module/exchangepowershell/install-unifiedcomplianceprerequisite",
+ "redirect_url": "/powershell/module/exchange/install-unifiedcomplianceprerequisite",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-ActivityAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-activityalert",
+ "redirect_url": "/powershell/module/exchange/new-activityalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-InformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-informationbarrierpolicy",
+ "redirect_url": "/powershell/module/exchange/new-informationbarrierpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-journalrule",
+ "redirect_url": "/powershell/module/exchange/new-journalrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-Label.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-label",
+ "redirect_url": "/powershell/module/exchange/new-label",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-LabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-labelpolicy",
+ "redirect_url": "/powershell/module/exchange/new-labelpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-MessageClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-messageclassification",
+ "redirect_url": "/powershell/module/exchange/new-messageclassification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-OrganizationSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-organizationsegment",
+ "redirect_url": "/powershell/module/exchange/new-organizationsegment",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-outlookprotectionrule",
+ "redirect_url": "/powershell/module/exchange/new-outlookprotectionrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-ProtectionAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert",
+ "redirect_url": "/powershell/module/exchange/new-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-SupervisoryReviewPolicyV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-supervisoryreviewpolicyv2",
+ "redirect_url": "/powershell/module/exchange/new-supervisoryreviewpolicyv2",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-SupervisoryReviewRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-supervisoryreviewrule",
+ "redirect_url": "/powershell/module/exchange/new-supervisoryreviewrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/New-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-transportrule",
+ "redirect_url": "/powershell/module/exchange/new-transportrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-ActivityAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activityalert",
+ "redirect_url": "/powershell/module/exchange/remove-activityalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-InformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-informationbarrierpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-informationbarrierpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-journalrule",
+ "redirect_url": "/powershell/module/exchange/remove-journalrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-Label.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-label",
+ "redirect_url": "/powershell/module/exchange/remove-label",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-LabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-labelpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-labelpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-MessageClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-messageclassification",
+ "redirect_url": "/powershell/module/exchange/remove-messageclassification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-OrganizationSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-organizationsegment",
+ "redirect_url": "/powershell/module/exchange/remove-organizationsegment",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-outlookprotectionrule",
+ "redirect_url": "/powershell/module/exchange/remove-outlookprotectionrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-ProtectionAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert",
+ "redirect_url": "/powershell/module/exchange/remove-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-SupervisoryReviewPolicyV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-supervisoryreviewpolicyv2",
+ "redirect_url": "/powershell/module/exchange/remove-supervisoryreviewpolicyv2",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Remove-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-transportrule",
+ "redirect_url": "/powershell/module/exchange/remove-transportrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-ActivityAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activityalert",
+ "redirect_url": "/powershell/module/exchange/set-activityalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-InformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-informationbarrierpolicy",
+ "redirect_url": "/powershell/module/exchange/set-informationbarrierpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-journalrule",
+ "redirect_url": "/powershell/module/exchange/set-journalrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-Label.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-label",
+ "redirect_url": "/powershell/module/exchange/set-label",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-LabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-labelpolicy",
+ "redirect_url": "/powershell/module/exchange/set-labelpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-MessageClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-messageclassification",
+ "redirect_url": "/powershell/module/exchange/set-messageclassification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-OrganizationSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-organizationsegment",
+ "redirect_url": "/powershell/module/exchange/set-organizationsegment",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-outlookprotectionrule",
+ "redirect_url": "/powershell/module/exchange/set-outlookprotectionrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-ProtectionAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-protectionalert",
+ "redirect_url": "/powershell/module/exchange/set-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-SupervisoryReviewPolicyV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-supervisoryreviewpolicyv2",
+ "redirect_url": "/powershell/module/exchange/set-supervisoryreviewpolicyv2",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-SupervisoryReviewRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-supervisoryreviewrule",
+ "redirect_url": "/powershell/module/exchange/set-supervisoryreviewrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Set-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportrule",
+ "redirect_url": "/powershell/module/exchange/set-transportrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Start-InformationBarrierPoliciesApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-informationbarrierpoliciesapplication",
+ "redirect_url": "/powershell/module/exchange/start-informationbarrierpoliciesapplication",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Stop-InformationBarrierPoliciesApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-informationbarrierpoliciesapplication",
+ "redirect_url": "/powershell/module/exchange/stop-informationbarrierpoliciesapplication",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance/Test-ArchiveConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-archiveconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-archiveconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AdminAuditLogConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adminauditlogconfig",
+ "redirect_url": "/powershell/module/exchange/get-adminauditlogconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-auditconfig",
+ "redirect_url": "/powershell/module/exchange/get-auditconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-auditconfigurationpolicy",
+ "redirect_url": "/powershell/module/exchange/get-auditconfigurationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-auditconfigurationrule",
+ "redirect_url": "/powershell/module/exchange/get-auditconfigurationrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-AuditLogSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-auditlogsearch",
+ "redirect_url": "/powershell/module/exchange/get-auditlogsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-MailboxAuditBypassAssociation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxauditbypassassociation",
+ "redirect_url": "/powershell/module/exchange/get-mailboxauditbypassassociation",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Get-UnifiedAuditLogRetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-unifiedauditlogretentionpolicy",
+ "redirect_url": "/powershell/module/exchange/get-unifiedauditlogretentionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-AdminAuditLogSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-adminauditlogsearch",
+ "redirect_url": "/powershell/module/exchange/new-adminauditlogsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-AuditConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-auditconfigurationpolicy",
+ "redirect_url": "/powershell/module/exchange/new-auditconfigurationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-AuditConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-auditconfigurationrule",
+ "redirect_url": "/powershell/module/exchange/new-auditconfigurationrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-MailboxAuditLogSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxauditlogsearch",
+ "redirect_url": "/powershell/module/exchange/new-mailboxauditlogsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/New-UnifiedAuditLogRetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-unifiedauditlogretentionpolicy",
+ "redirect_url": "/powershell/module/exchange/new-unifiedauditlogretentionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Remove-AuditConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-auditconfigurationpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-auditconfigurationpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Remove-AuditConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-auditconfigurationrule",
+ "redirect_url": "/powershell/module/exchange/remove-auditconfigurationrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Remove-UnifiedAuditLogRetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedauditlogretentionpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-unifiedauditlogretentionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Search-AdminAuditLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-adminauditlog",
+ "redirect_url": "/powershell/module/exchange/search-adminauditlog",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Search-MailboxAuditLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-mailboxauditlog",
+ "redirect_url": "/powershell/module/exchange/search-mailboxauditlog",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Search-UnifiedAuditLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-unifiedauditlog",
+ "redirect_url": "/powershell/module/exchange/search-unifiedauditlog",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-AdminAuditLogConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adminauditlogconfig",
+ "redirect_url": "/powershell/module/exchange/set-adminauditlogconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-AuditConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-auditconfig",
+ "redirect_url": "/powershell/module/exchange/set-auditconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-AuditConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-auditconfigurationrule",
+ "redirect_url": "/powershell/module/exchange/set-auditconfigurationrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-MailboxAuditBypassAssociation.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxauditbypassassociation",
+ "redirect_url": "/powershell/module/exchange/set-mailboxauditbypassassociation",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Set-UnifiedAuditLogRetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-unifiedauditlogretentionpolicy",
+ "redirect_url": "/powershell/module/exchange/set-unifiedauditlogretentionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-audit/Write-AdminAuditLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/write-adminauditlog",
+ "redirect_url": "/powershell/module/exchange/write-adminauditlog",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Get-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancesearch",
+ "redirect_url": "/powershell/module/exchange/get-compliancesearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Get-ComplianceSearchAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancesearchaction",
+ "redirect_url": "/powershell/module/exchange/get-compliancesearchaction",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Get-ComplianceSecurityFilter.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancesecurityfilter",
+ "redirect_url": "/powershell/module/exchange/get-compliancesecurityfilter",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Get-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxsearch",
+ "redirect_url": "/powershell/module/exchange/get-mailboxsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Invoke-ComplianceSearchActionStep.md",
- "redirect_url": "/powershell/module/exchangepowershell/invoke-compliancesearchactionstep",
+ "redirect_url": "/powershell/module/exchange/invoke-compliancesearchactionstep",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/New-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancesearch",
+ "redirect_url": "/powershell/module/exchange/new-compliancesearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/New-ComplianceSearchAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancesearchaction",
+ "redirect_url": "/powershell/module/exchange/new-compliancesearchaction",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/New-ComplianceSecurityFilter.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancesecurityfilter",
+ "redirect_url": "/powershell/module/exchange/new-compliancesecurityfilter",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/New-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxsearch",
+ "redirect_url": "/powershell/module/exchange/new-mailboxsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Remove-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesearch",
+ "redirect_url": "/powershell/module/exchange/remove-compliancesearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Remove-ComplianceSearchAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesearchaction",
+ "redirect_url": "/powershell/module/exchange/remove-compliancesearchaction",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Remove-ComplianceSecurityFilter.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesecurityfilter",
+ "redirect_url": "/powershell/module/exchange/remove-compliancesecurityfilter",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Remove-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxsearch",
+ "redirect_url": "/powershell/module/exchange/remove-mailboxsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Set-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancesearch",
+ "redirect_url": "/powershell/module/exchange/set-compliancesearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Set-ComplianceSearchAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancesearchaction",
+ "redirect_url": "/powershell/module/exchange/set-compliancesearchaction",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Set-ComplianceSecurityFilter.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancesecurityfilter",
+ "redirect_url": "/powershell/module/exchange/set-compliancesecurityfilter",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Set-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxsearch",
+ "redirect_url": "/powershell/module/exchange/set-mailboxsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Start-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-compliancesearch",
+ "redirect_url": "/powershell/module/exchange/start-compliancesearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Start-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-mailboxsearch",
+ "redirect_url": "/powershell/module/exchange/start-mailboxsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Stop-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-compliancesearch",
+ "redirect_url": "/powershell/module/exchange/stop-compliancesearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-content-search/Stop-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-mailboxsearch",
+ "redirect_url": "/powershell/module/exchange/stop-mailboxsearch",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Export-DlpPolicyCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-dlppolicycollection",
+ "redirect_url": "/powershell/module/exchange/export-dlppolicycollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-ClassificationRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-classificationrulecollection",
+ "redirect_url": "/powershell/module/exchange/get-classificationrulecollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dataclassification",
+ "redirect_url": "/powershell/module/exchange/get-dataclassification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DataClassificationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dataclassificationconfig",
+ "redirect_url": "/powershell/module/exchange/get-dataclassificationconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpcompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/get-dlpcompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpcompliancerule",
+ "redirect_url": "/powershell/module/exchange/get-dlpcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpDetailReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpdetailreport",
+ "redirect_url": "/powershell/module/exchange/get-dlpdetailreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpDetectionsReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpdetectionsreport",
+ "redirect_url": "/powershell/module/exchange/get-dlpdetectionsreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpEdmSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpedmschema",
+ "redirect_url": "/powershell/module/exchange/get-dlpedmschema",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpKeywordDictionary.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpkeyworddictionary",
+ "redirect_url": "/powershell/module/exchange/get-dlpkeyworddictionary",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlppolicy",
+ "redirect_url": "/powershell/module/exchange/get-dlppolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpPolicyTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlppolicytemplate",
+ "redirect_url": "/powershell/module/exchange/get-dlppolicytemplate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationType.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype",
+ "redirect_url": "/powershell/module/exchange/get-dlpsensitiveinformationtype",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpSensitiveInformationTypeRulePackage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpsensitiveinformationtyperulepackage",
+ "redirect_url": "/powershell/module/exchange/get-dlpsensitiveinformationtyperulepackage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-DlpSiDetectionsReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpsidetectionsreport",
+ "redirect_url": "/powershell/module/exchange/get-dlpsidetectionsreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Get-PolicyTipConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-policytipconfig",
+ "redirect_url": "/powershell/module/exchange/get-policytipconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Import-DlpPolicyCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-dlppolicycollection",
+ "redirect_url": "/powershell/module/exchange/import-dlppolicycollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Import-DlpPolicyTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-dlppolicytemplate",
+ "redirect_url": "/powershell/module/exchange/import-dlppolicytemplate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-ClassificationRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-classificationrulecollection",
+ "redirect_url": "/powershell/module/exchange/new-classificationrulecollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dataclassification",
+ "redirect_url": "/powershell/module/exchange/new-dataclassification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpcompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/new-dlpcompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpcompliancerule",
+ "redirect_url": "/powershell/module/exchange/new-dlpcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpEdmSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpedmschema",
+ "redirect_url": "/powershell/module/exchange/new-dlpedmschema",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpFingerprint.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpfingerprint",
+ "redirect_url": "/powershell/module/exchange/new-dlpfingerprint",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpKeywordDictionary.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpkeyworddictionary",
+ "redirect_url": "/powershell/module/exchange/new-dlpkeyworddictionary",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlppolicy",
+ "redirect_url": "/powershell/module/exchange/new-dlppolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationType.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype",
+ "redirect_url": "/powershell/module/exchange/new-dlpsensitiveinformationtype",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-DlpSensitiveInformationTypeRulePackage.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpsensitiveinformationtyperulepackage",
+ "redirect_url": "/powershell/module/exchange/new-dlpsensitiveinformationtyperulepackage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-Fingerprint.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-fingerprint",
+ "redirect_url": "/powershell/module/exchange/new-fingerprint",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/New-PolicyTipConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-policytipconfig",
+ "redirect_url": "/powershell/module/exchange/new-policytipconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-ClassificationRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-classificationrulecollection",
+ "redirect_url": "/powershell/module/exchange/remove-classificationrulecollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dataclassification",
+ "redirect_url": "/powershell/module/exchange/remove-dataclassification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpcompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/remove-dlpcompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpcompliancerule",
+ "redirect_url": "/powershell/module/exchange/remove-dlpcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpEdmSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpedmschema",
+ "redirect_url": "/powershell/module/exchange/remove-dlpedmschema",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpKeywordDictionary.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpkeyworddictionary",
+ "redirect_url": "/powershell/module/exchange/remove-dlpkeyworddictionary",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlppolicy",
+ "redirect_url": "/powershell/module/exchange/remove-dlppolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpPolicyTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlppolicytemplate",
+ "redirect_url": "/powershell/module/exchange/remove-dlppolicytemplate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationType.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtype",
+ "redirect_url": "/powershell/module/exchange/remove-dlpsensitiveinformationtype",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-DlpSensitiveInformationTypeRulePackage.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtyperulepackage",
+ "redirect_url": "/powershell/module/exchange/remove-dlpsensitiveinformationtyperulepackage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Remove-PolicyTipConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-policytipconfig",
+ "redirect_url": "/powershell/module/exchange/remove-policytipconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-ClassificationRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-classificationrulecollection",
+ "redirect_url": "/powershell/module/exchange/set-classificationrulecollection",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dataclassification",
+ "redirect_url": "/powershell/module/exchange/set-dataclassification",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpcompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/set-dlpcompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpcompliancerule",
+ "redirect_url": "/powershell/module/exchange/set-dlpcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpEdmSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpedmschema",
+ "redirect_url": "/powershell/module/exchange/set-dlpedmschema",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpKeywordDictionary.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpkeyworddictionary",
+ "redirect_url": "/powershell/module/exchange/set-dlpkeyworddictionary",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlppolicy",
+ "redirect_url": "/powershell/module/exchange/set-dlppolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationType.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpsensitiveinformationtype",
+ "redirect_url": "/powershell/module/exchange/set-dlpsensitiveinformationtype",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-DlpSensitiveInformationTypeRulePackage.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpsensitiveinformationtyperulepackage",
+ "redirect_url": "/powershell/module/exchange/set-dlpsensitiveinformationtyperulepackage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-dlp/Set-PolicyTipConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-policytipconfig",
+ "redirect_url": "/powershell/module/exchange/set-policytipconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Add-ComplianceCaseMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-compliancecasemember",
+ "redirect_url": "/powershell/module/exchange/add-compliancecasemember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Add-eDiscoveryCaseAdmin.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ediscoverycaseadmin",
+ "redirect_url": "/powershell/module/exchange/add-ediscoverycaseadmin",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-CaseHoldPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-caseholdpolicy",
+ "redirect_url": "/powershell/module/exchange/get-caseholdpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-CaseHoldRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-caseholdrule",
+ "redirect_url": "/powershell/module/exchange/get-caseholdrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-ComplianceCase.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancecase",
+ "redirect_url": "/powershell/module/exchange/get-compliancecase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-ComplianceCaseMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancecasemember",
+ "redirect_url": "/powershell/module/exchange/get-compliancecasemember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Get-eDiscoveryCaseAdmin.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ediscoverycaseadmin",
+ "redirect_url": "/powershell/module/exchange/get-ediscoverycaseadmin",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/New-CaseHoldPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-caseholdpolicy",
+ "redirect_url": "/powershell/module/exchange/new-caseholdpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/New-CaseHoldRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-caseholdrule",
+ "redirect_url": "/powershell/module/exchange/new-caseholdrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/New-ComplianceCase.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancecase",
+ "redirect_url": "/powershell/module/exchange/new-compliancecase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-caseholdpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-caseholdpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-CaseHoldRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-caseholdrule",
+ "redirect_url": "/powershell/module/exchange/remove-caseholdrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCase.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancecase",
+ "redirect_url": "/powershell/module/exchange/remove-compliancecase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-ComplianceCaseMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancecasemember",
+ "redirect_url": "/powershell/module/exchange/remove-compliancecasemember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Remove-eDiscoveryCaseAdmin.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ediscoverycaseadmin",
+ "redirect_url": "/powershell/module/exchange/remove-ediscoverycaseadmin",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Set-CaseHoldPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-caseholdpolicy",
+ "redirect_url": "/powershell/module/exchange/set-caseholdpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Set-CaseHoldRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-caseholdrule",
+ "redirect_url": "/powershell/module/exchange/set-caseholdrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Set-ComplianceCase.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancecase",
+ "redirect_url": "/powershell/module/exchange/set-compliancecase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Update-ComplianceCaseMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-compliancecasemember",
+ "redirect_url": "/powershell/module/exchange/update-compliancecasemember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-ediscovery/Update-eDiscoveryCaseAdmin.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-ediscoverycaseadmin",
+ "redirect_url": "/powershell/module/exchange/update-ediscoverycaseadmin",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Enable-ComplianceTagStorage.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-compliancetagstorage",
+ "redirect_url": "/powershell/module/exchange/enable-compliancetagstorage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEvent.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-complianceretentionevent",
+ "redirect_url": "/powershell/module/exchange/get-complianceretentionevent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceRetentionEventType.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-complianceretentioneventtype",
+ "redirect_url": "/powershell/module/exchange/get-complianceretentioneventtype",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancetag",
+ "redirect_url": "/powershell/module/exchange/get-compliancetag",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ComplianceTagStorage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancetagstorage",
+ "redirect_url": "/powershell/module/exchange/get-compliancetagstorage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-DataRetentionReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dataretentionreport",
+ "redirect_url": "/powershell/module/exchange/get-dataretentionreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-HoldCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-holdcompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/get-holdcompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-HoldComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-holdcompliancerule",
+ "redirect_url": "/powershell/module/exchange/get-holdcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ManagedContentSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managedcontentsettings",
+ "redirect_url": "/powershell/module/exchange/get-managedcontentsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ManagedFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managedfolder",
+ "redirect_url": "/powershell/module/exchange/get-managedfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-ManagedFolderMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managedfoldermailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/get-managedfoldermailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/get-retentioncompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancerule",
+ "redirect_url": "/powershell/module/exchange/get-retentioncompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionEvent.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentionevent",
+ "redirect_url": "/powershell/module/exchange/get-retentionevent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentionpolicy",
+ "redirect_url": "/powershell/module/exchange/get-retentionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Get-RetentionPolicyTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentionpolicytag",
+ "redirect_url": "/powershell/module/exchange/get-retentionpolicytag",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ComplianceRetentionEvent.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-complianceretentionevent",
+ "redirect_url": "/powershell/module/exchange/new-complianceretentionevent",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ComplianceRetentionEventType.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-complianceretentioneventtype",
+ "redirect_url": "/powershell/module/exchange/new-complianceretentioneventtype",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ComplianceTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancetag",
+ "redirect_url": "/powershell/module/exchange/new-compliancetag",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-HoldCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-holdcompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/new-holdcompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-HoldComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-holdcompliancerule",
+ "redirect_url": "/powershell/module/exchange/new-holdcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ManagedContentSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managedcontentsettings",
+ "redirect_url": "/powershell/module/exchange/new-managedcontentsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ManagedFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managedfolder",
+ "redirect_url": "/powershell/module/exchange/new-managedfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-ManagedFolderMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managedfoldermailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/new-managedfoldermailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/new-retentioncompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancerule",
+ "redirect_url": "/powershell/module/exchange/new-retentioncompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentionpolicy",
+ "redirect_url": "/powershell/module/exchange/new-retentionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/New-RetentionPolicyTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentionpolicytag",
+ "redirect_url": "/powershell/module/exchange/new-retentionpolicytag",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ComplianceRetentionEventType.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-complianceretentioneventtype",
+ "redirect_url": "/powershell/module/exchange/remove-complianceretentioneventtype",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ComplianceTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancetag",
+ "redirect_url": "/powershell/module/exchange/remove-compliancetag",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-HoldCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-holdcompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/remove-holdcompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-HoldComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-holdcompliancerule",
+ "redirect_url": "/powershell/module/exchange/remove-holdcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ManagedContentSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managedcontentsettings",
+ "redirect_url": "/powershell/module/exchange/remove-managedcontentsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ManagedFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managedfolder",
+ "redirect_url": "/powershell/module/exchange/remove-managedfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-ManagedFolderMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managedfoldermailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-managedfoldermailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/remove-retentioncompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancerule",
+ "redirect_url": "/powershell/module/exchange/remove-retentioncompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentionpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-retentionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Remove-RetentionPolicyTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentionpolicytag",
+ "redirect_url": "/powershell/module/exchange/remove-retentionpolicytag",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ComplianceRetentionEventType.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-complianceretentioneventtype",
+ "redirect_url": "/powershell/module/exchange/set-complianceretentioneventtype",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ComplianceTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancetag",
+ "redirect_url": "/powershell/module/exchange/set-compliancetag",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-HoldCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-holdcompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/set-holdcompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-HoldComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-holdcompliancerule",
+ "redirect_url": "/powershell/module/exchange/set-holdcompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ManagedContentSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managedcontentsettings",
+ "redirect_url": "/powershell/module/exchange/set-managedcontentsettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ManagedFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managedfolder",
+ "redirect_url": "/powershell/module/exchange/set-managedfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-ManagedFolderMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managedfoldermailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/set-managedfoldermailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancepolicy",
+ "redirect_url": "/powershell/module/exchange/set-retentioncompliancepolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancerule",
+ "redirect_url": "/powershell/module/exchange/set-retentioncompliancerule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentionpolicy",
+ "redirect_url": "/powershell/module/exchange/set-retentionpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Set-RetentionPolicyTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentionpolicytag",
+ "redirect_url": "/powershell/module/exchange/set-retentionpolicytag",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Start-ManagedFolderAssistant.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-managedfolderassistant",
+ "redirect_url": "/powershell/module/exchange/start-managedfolderassistant",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Start-RetentionAutoTagLearning.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-retentionautotaglearning",
+ "redirect_url": "/powershell/module/exchange/start-retentionautotaglearning",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Stop-ManagedFolderAssistant.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-managedfolderassistant",
+ "redirect_url": "/powershell/module/exchange/stop-managedfolderassistant",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/policy-and-compliance-retention/Validate-RetentionRuleQuery.md",
- "redirect_url": "/powershell/module/exchangepowershell/validate-retentionrulequery",
+ "redirect_url": "/powershell/module/exchange/validate-retentionrulequery",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Connect-ExchangeOnline.md",
- "redirect_url": "/powershell/module/exchangepowershell/connect-exchangeonline",
+ "redirect_url": "/powershell/module/exchange/connect-exchangeonline",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOCasMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exocasmailbox",
+ "redirect_url": "/powershell/module/exchange/get-exocasmailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailbox",
+ "redirect_url": "/powershell/module/exchange/get-exomailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxfolderpermission",
+ "redirect_url": "/powershell/module/exchange/get-exomailboxfolderpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxFolderStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxfolderstatistics",
+ "redirect_url": "/powershell/module/exchange/get-exomailboxfolderstatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxpermission",
+ "redirect_url": "/powershell/module/exchange/get-exomailboxpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMailboxStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxstatistics",
+ "redirect_url": "/powershell/module/exchange/get-exomailboxstatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXOMobileDeviceStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomobiledevicestatistics",
+ "redirect_url": "/powershell/module/exchange/get-exomobiledevicestatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXORecipient.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exorecipient",
+ "redirect_url": "/powershell/module/exchange/get-exorecipient",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/powershell-v2-module/Get-EXORecipientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exorecipientpermission",
+ "redirect_url": "/powershell/module/exchange/get-exorecipientpermission",
"redirect_document_id": false
},
{
@@ -5207,7 +5207,7 @@
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-HistoricalSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-historicalsearch",
+ "redirect_url": "/powershell/module/exchange/get-historicalsearch",
"redirect_document_id": false
},
{
@@ -5217,7 +5217,7 @@
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-LogonStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-logonstatistics",
+ "redirect_url": "/powershell/module/exchange/get-logonstatistics",
"redirect_document_id": false
},
{
@@ -5237,52 +5237,52 @@
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailDlpPolicyReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetaildlppolicyreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetaildlppolicyreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailMalwareReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailatpreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailSpamReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailatpreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailDetailTransportRuleReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailtransportrulereport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailtransportrulereport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailFilterListReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailfilterlistreport",
+ "redirect_url": "/powershell/module/exchange/get-mailfilterlistreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficPolicyReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficpolicyreport",
+ "redirect_url": "/powershell/module/exchange/get-mailtrafficpolicyreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficreport",
+ "redirect_url": "/powershell/module/exchange/get-mailtrafficreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficSummaryReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficsummaryreport",
+ "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficTopReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficsummaryreport",
+ "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-MxRecordReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mxrecordreport",
+ "redirect_url": "/powershell/module/exchange/get-mxrecordreport",
"redirect_document_id": false
},
{
@@ -5307,27 +5307,27 @@
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-OutboundConnectorReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outboundconnectorreport",
+ "redirect_url": "/powershell/module/exchange/get-outboundconnectorreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-RecipientStatisticsReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recipientstatisticsreport",
+ "redirect_url": "/powershell/module/exchange/get-recipientstatisticsreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-ReportExecutionInstance.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-reportexecutioninstance",
+ "redirect_url": "/powershell/module/exchange/get-reportexecutioninstance",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-SCInsights.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-scinsights",
+ "redirect_url": "/powershell/module/exchange/get-scinsights",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-ServiceDeliveryReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-servicedeliveryreport",
+ "redirect_url": "/powershell/module/exchange/get-servicedeliveryreport",
"redirect_document_id": false
},
{
@@ -5372,1127 +5372,1127 @@
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewActivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewactivity",
+ "redirect_url": "/powershell/module/exchange/get-supervisoryreviewactivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewOverallProgressReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewoverallprogressreport",
+ "redirect_url": "/powershell/module/exchange/get-supervisoryreviewoverallprogressreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewPolicyReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewpolicyreport",
+ "redirect_url": "/powershell/module/exchange/get-supervisoryreviewpolicyreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewreport",
+ "redirect_url": "/powershell/module/exchange/get-supervisoryreviewreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-SupervisoryReviewTopCasesReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewtopcasesreport",
+ "redirect_url": "/powershell/module/exchange/get-supervisoryreviewtopcasesreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-TenantAnalyticsConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig",
+ "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Get-UserAnalyticsConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig",
+ "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Set-TenantAnalyticsConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/myanalyticsfeatureconfig",
+ "redirect_url": "/powershell/module/exchange/myanalyticsfeatureconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/reporting/Set-UserAnalyticsConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/myanalyticsfeatureconfig",
+ "redirect_url": "/powershell/module/exchange/myanalyticsfeatureconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Add-ManagementRoleEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-managementroleentry",
+ "redirect_url": "/powershell/module/exchange/add-managementroleentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Add-RoleGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-rolegroupmember",
+ "redirect_url": "/powershell/module/exchange/add-rolegroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managementrole",
+ "redirect_url": "/powershell/module/exchange/get-managementrole",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementRoleAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managementroleassignment",
+ "redirect_url": "/powershell/module/exchange/get-managementroleassignment",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementRoleEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managementroleentry",
+ "redirect_url": "/powershell/module/exchange/get-managementroleentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-ManagementScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managementscope",
+ "redirect_url": "/powershell/module/exchange/get-managementscope",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-RoleAssignmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-roleassignmentpolicy",
+ "redirect_url": "/powershell/module/exchange/get-roleassignmentpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-RoleGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-rolegroup",
+ "redirect_url": "/powershell/module/exchange/get-rolegroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Get-RoleGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-rolegroupmember",
+ "redirect_url": "/powershell/module/exchange/get-rolegroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-ManagementRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managementrole",
+ "redirect_url": "/powershell/module/exchange/new-managementrole",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-ManagementRoleAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managementroleassignment",
+ "redirect_url": "/powershell/module/exchange/new-managementroleassignment",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-ManagementScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managementscope",
+ "redirect_url": "/powershell/module/exchange/new-managementscope",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-RoleAssignmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-roleassignmentpolicy",
+ "redirect_url": "/powershell/module/exchange/new-roleassignmentpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/New-RoleGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-rolegroup",
+ "redirect_url": "/powershell/module/exchange/new-rolegroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managementrole",
+ "redirect_url": "/powershell/module/exchange/remove-managementrole",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementRoleAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managementroleassignment",
+ "redirect_url": "/powershell/module/exchange/remove-managementroleassignment",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementRoleEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managementroleentry",
+ "redirect_url": "/powershell/module/exchange/remove-managementroleentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-ManagementScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managementscope",
+ "redirect_url": "/powershell/module/exchange/remove-managementscope",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-RoleAssignmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-roleassignmentpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-roleassignmentpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-RoleGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-rolegroup",
+ "redirect_url": "/powershell/module/exchange/remove-rolegroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Remove-RoleGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-rolegroupmember",
+ "redirect_url": "/powershell/module/exchange/remove-rolegroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-ManagementRoleAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managementroleassignment",
+ "redirect_url": "/powershell/module/exchange/set-managementroleassignment",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-ManagementRoleEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managementroleentry",
+ "redirect_url": "/powershell/module/exchange/set-managementroleentry",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-ManagementScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managementscope",
+ "redirect_url": "/powershell/module/exchange/set-managementscope",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-RoleAssignmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-roleassignmentpolicy",
+ "redirect_url": "/powershell/module/exchange/set-roleassignmentpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Set-RoleGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-rolegroup",
+ "redirect_url": "/powershell/module/exchange/set-rolegroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/role-based-access-control/Update-RoleGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-rolegroupmember",
+ "redirect_url": "/powershell/module/exchange/update-rolegroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Add-GlobalMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-globalmonitoringoverride",
+ "redirect_url": "/powershell/module/exchange/add-globalmonitoringoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Add-ServerMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-servermonitoringoverride",
+ "redirect_url": "/powershell/module/exchange/add-servermonitoringoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-AvailabilityReportOutage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-availabilityreportoutage",
+ "redirect_url": "/powershell/module/exchange/get-availabilityreportoutage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-EventLogLevel.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-eventloglevel",
+ "redirect_url": "/powershell/module/exchange/get-eventloglevel",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-GlobalMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-globalmonitoringoverride",
+ "redirect_url": "/powershell/module/exchange/get-globalmonitoringoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-HealthReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-healthreport",
+ "redirect_url": "/powershell/module/exchange/get-healthreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-MonitoringItemHelp.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-monitoringitemhelp",
+ "redirect_url": "/powershell/module/exchange/get-monitoringitemhelp",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-MonitoringItemIdentity.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-monitoringitemidentity",
+ "redirect_url": "/powershell/module/exchange/get-monitoringitemidentity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ServerComponentState.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-servercomponentstate",
+ "redirect_url": "/powershell/module/exchange/get-servercomponentstate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ServerHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-serverhealth",
+ "redirect_url": "/powershell/module/exchange/get-serverhealth",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ServerMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-servermonitoringoverride",
+ "redirect_url": "/powershell/module/exchange/get-servermonitoringoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ThrottlingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-throttlingpolicy",
+ "redirect_url": "/powershell/module/exchange/get-throttlingpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Get-ThrottlingPolicyAssociation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-throttlingpolicyassociation",
+ "redirect_url": "/powershell/module/exchange/get-throttlingpolicyassociation",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Invoke-MonitoringProbe.md",
- "redirect_url": "/powershell/module/exchangepowershell/invoke-monitoringprobe",
+ "redirect_url": "/powershell/module/exchange/invoke-monitoringprobe",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/New-AvailabilityReportOutage.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-availabilityreportoutage",
+ "redirect_url": "/powershell/module/exchange/new-availabilityreportoutage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/New-ThrottlingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-throttlingpolicy",
+ "redirect_url": "/powershell/module/exchange/new-throttlingpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-AvailabilityReportOutage.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityreportoutage",
+ "redirect_url": "/powershell/module/exchange/remove-availabilityreportoutage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-GlobalMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-globalmonitoringoverride",
+ "redirect_url": "/powershell/module/exchange/remove-globalmonitoringoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-ServerMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-servermonitoringoverride",
+ "redirect_url": "/powershell/module/exchange/remove-servermonitoringoverride",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Remove-ThrottlingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-throttlingpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-throttlingpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-AvailabilityReportOutage.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-availabilityreportoutage",
+ "redirect_url": "/powershell/module/exchange/set-availabilityreportoutage",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-EventLogLevel.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-eventloglevel",
+ "redirect_url": "/powershell/module/exchange/set-eventloglevel",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ServerComponentState.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-servercomponentstate",
+ "redirect_url": "/powershell/module/exchange/set-servercomponentstate",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ServerMonitor.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-servermonitor",
+ "redirect_url": "/powershell/module/exchange/set-servermonitor",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ThrottlingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-throttlingpolicy",
+ "redirect_url": "/powershell/module/exchange/set-throttlingpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Set-ThrottlingPolicyAssociation.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-throttlingpolicyassociation",
+ "redirect_url": "/powershell/module/exchange/set-throttlingpolicyassociation",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/server-health-and-performance/Test-ServiceHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-servicehealth",
+ "redirect_url": "/powershell/module/exchange/test-servicehealth",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Add-AvailabilityAddressSpace.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-availabilityaddressspace",
+ "redirect_url": "/powershell/module/exchange/add-availabilityaddressspace",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Add-PublicFolderAdministrativePermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-publicfolderadministrativepermission",
+ "redirect_url": "/powershell/module/exchange/add-publicfolderadministrativepermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Add-PublicFolderClientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-publicfolderclientpermission",
+ "redirect_url": "/powershell/module/exchange/add-publicfolderclientpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Disable-MailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailpublicfolder",
+ "redirect_url": "/powershell/module/exchange/disable-mailpublicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Enable-MailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailpublicfolder",
+ "redirect_url": "/powershell/module/exchange/enable-mailpublicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-AvailabilityAddressSpace.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-availabilityaddressspace",
+ "redirect_url": "/powershell/module/exchange/get-availabilityaddressspace",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-AvailabilityConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-availabilityconfig",
+ "redirect_url": "/powershell/module/exchange/get-availabilityconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-MailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailpublicfolder",
+ "redirect_url": "/powershell/module/exchange/get-mailpublicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-organizationrelationship",
+ "redirect_url": "/powershell/module/exchange/get-organizationrelationship",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolder",
+ "redirect_url": "/powershell/module/exchange/get-publicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderAdministrativePermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderadministrativepermission",
+ "redirect_url": "/powershell/module/exchange/get-publicfolderadministrativepermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderClientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderclientpermission",
+ "redirect_url": "/powershell/module/exchange/get-publicfolderclientpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderdatabase",
+ "redirect_url": "/powershell/module/exchange/get-publicfolderdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderItemStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderitemstatistics",
+ "redirect_url": "/powershell/module/exchange/get-publicfolderitemstatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderMailboxDiagnostics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxdiagnostics",
+ "redirect_url": "/powershell/module/exchange/get-publicfoldermailboxdiagnostics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-PublicFolderStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderstatistics",
+ "redirect_url": "/powershell/module/exchange/get-publicfolderstatistics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SharingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sharingpolicy",
+ "redirect_url": "/powershell/module/exchange/get-sharingpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sitemailbox",
+ "redirect_url": "/powershell/module/exchange/get-sitemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SiteMailboxDiagnostics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sitemailboxdiagnostics",
+ "redirect_url": "/powershell/module/exchange/get-sitemailboxdiagnostics",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Get-SiteMailboxProvisioningPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sitemailboxprovisioningpolicy",
+ "redirect_url": "/powershell/module/exchange/get-sitemailboxprovisioningpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-AvailabilityConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-availabilityconfig",
+ "redirect_url": "/powershell/module/exchange/new-availabilityconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-organizationrelationship",
+ "redirect_url": "/powershell/module/exchange/new-organizationrelationship",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfolder",
+ "redirect_url": "/powershell/module/exchange/new-publicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-PublicFolderDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfolderdatabase",
+ "redirect_url": "/powershell/module/exchange/new-publicfolderdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-PublicFolderDatabaseRepairRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfolderdatabaserepairrequest",
+ "redirect_url": "/powershell/module/exchange/new-publicfolderdatabaserepairrequest",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-SharingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sharingpolicy",
+ "redirect_url": "/powershell/module/exchange/new-sharingpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-SiteMailboxProvisioningPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sitemailboxprovisioningpolicy",
+ "redirect_url": "/powershell/module/exchange/new-sitemailboxprovisioningpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/New-SyncMailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-syncmailpublicfolder",
+ "redirect_url": "/powershell/module/exchange/new-syncmailpublicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-AvailabilityAddressSpace.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityaddressspace",
+ "redirect_url": "/powershell/module/exchange/remove-availabilityaddressspace",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-AvailabilityConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityconfig",
+ "redirect_url": "/powershell/module/exchange/remove-availabilityconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-organizationrelationship",
+ "redirect_url": "/powershell/module/exchange/remove-organizationrelationship",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolder",
+ "redirect_url": "/powershell/module/exchange/remove-publicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolderAdministrativePermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderadministrativepermission",
+ "redirect_url": "/powershell/module/exchange/remove-publicfolderadministrativepermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolderClientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderclientpermission",
+ "redirect_url": "/powershell/module/exchange/remove-publicfolderclientpermission",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-PublicFolderDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderdatabase",
+ "redirect_url": "/powershell/module/exchange/remove-publicfolderdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-SharingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-sharingpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-sharingpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-SiteMailboxProvisioningPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-sitemailboxprovisioningpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-sitemailboxprovisioningpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Remove-SyncMailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-syncmailpublicfolder",
+ "redirect_url": "/powershell/module/exchange/remove-syncmailpublicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Resume-PublicFolderReplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-publicfolderreplication",
+ "redirect_url": "/powershell/module/exchange/resume-publicfolderreplication",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-AvailabilityConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-availabilityconfig",
+ "redirect_url": "/powershell/module/exchange/set-availabilityconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-MailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailpublicfolder",
+ "redirect_url": "/powershell/module/exchange/set-mailpublicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-organizationrelationship",
+ "redirect_url": "/powershell/module/exchange/set-organizationrelationship",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-publicfolder",
+ "redirect_url": "/powershell/module/exchange/set-publicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-PublicFolderDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-publicfolderdatabase",
+ "redirect_url": "/powershell/module/exchange/set-publicfolderdatabase",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-SharingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sharingpolicy",
+ "redirect_url": "/powershell/module/exchange/set-sharingpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sitemailbox",
+ "redirect_url": "/powershell/module/exchange/set-sitemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Set-SiteMailboxProvisioningPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sitemailboxprovisioningpolicy",
+ "redirect_url": "/powershell/module/exchange/set-sitemailboxprovisioningpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Suspend-PublicFolderReplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfolderreplication",
+ "redirect_url": "/powershell/module/exchange/suspend-publicfolderreplication",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Test-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-organizationrelationship",
+ "redirect_url": "/powershell/module/exchange/test-organizationrelationship",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Test-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-sitemailbox",
+ "redirect_url": "/powershell/module/exchange/test-sitemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-publicfolder",
+ "redirect_url": "/powershell/module/exchange/update-publicfolder",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-PublicFolderHierarchy.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-publicfolderhierarchy",
+ "redirect_url": "/powershell/module/exchange/update-publicfolderhierarchy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-PublicFolderMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-publicfoldermailbox",
+ "redirect_url": "/powershell/module/exchange/update-publicfoldermailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/sharing-and-collaboration/Update-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-sitemailbox",
+ "redirect_url": "/powershell/module/exchange/update-sitemailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umautoattendant",
+ "redirect_url": "/powershell/module/exchange/disable-umautoattendant",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umcallansweringrule",
+ "redirect_url": "/powershell/module/exchange/disable-umcallansweringrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umipgateway",
+ "redirect_url": "/powershell/module/exchange/disable-umipgateway",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-ummailbox",
+ "redirect_url": "/powershell/module/exchange/disable-ummailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umserver",
+ "redirect_url": "/powershell/module/exchange/disable-umserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Disable-UMService.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umservice",
+ "redirect_url": "/powershell/module/exchange/disable-umservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umautoattendant",
+ "redirect_url": "/powershell/module/exchange/enable-umautoattendant",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umcallansweringrule",
+ "redirect_url": "/powershell/module/exchange/enable-umcallansweringrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umipgateway",
+ "redirect_url": "/powershell/module/exchange/enable-umipgateway",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-ummailbox",
+ "redirect_url": "/powershell/module/exchange/enable-ummailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umserver",
+ "redirect_url": "/powershell/module/exchange/enable-umserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Enable-UMService.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umservice",
+ "redirect_url": "/powershell/module/exchange/enable-umservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Export-UMCallDataRecord.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-umcalldatarecord",
+ "redirect_url": "/powershell/module/exchange/export-umcalldatarecord",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Export-UMPrompt.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-umprompt",
+ "redirect_url": "/powershell/module/exchange/export-umprompt",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-OnlineMeetingConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-onlinemeetingconfiguration",
+ "redirect_url": "/powershell/module/exchange/get-onlinemeetingconfiguration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMActiveCalls.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umactivecalls",
+ "redirect_url": "/powershell/module/exchange/get-umactivecalls",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umautoattendant",
+ "redirect_url": "/powershell/module/exchange/get-umautoattendant",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umcallansweringrule",
+ "redirect_url": "/powershell/module/exchange/get-umcallansweringrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallDataRecord.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umcalldatarecord",
+ "redirect_url": "/powershell/module/exchange/get-umcalldatarecord",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallRouterSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umcallroutersettings",
+ "redirect_url": "/powershell/module/exchange/get-umcallroutersettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMCallSummaryReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umcallsummaryreport",
+ "redirect_url": "/powershell/module/exchange/get-umcallsummaryreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMDialPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umdialplan",
+ "redirect_url": "/powershell/module/exchange/get-umdialplan",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMHuntGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umhuntgroup",
+ "redirect_url": "/powershell/module/exchange/get-umhuntgroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umipgateway",
+ "redirect_url": "/powershell/module/exchange/get-umipgateway",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ummailbox",
+ "redirect_url": "/powershell/module/exchange/get-ummailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMMailboxPIN.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ummailboxpin",
+ "redirect_url": "/powershell/module/exchange/get-ummailboxpin",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ummailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/get-ummailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UmServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umserver",
+ "redirect_url": "/powershell/module/exchange/get-umserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Get-UMService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umservice",
+ "redirect_url": "/powershell/module/exchange/get-umservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Import-UMPrompt.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-umprompt",
+ "redirect_url": "/powershell/module/exchange/import-umprompt",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umautoattendant",
+ "redirect_url": "/powershell/module/exchange/new-umautoattendant",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umcallansweringrule",
+ "redirect_url": "/powershell/module/exchange/new-umcallansweringrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMDialPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umdialplan",
+ "redirect_url": "/powershell/module/exchange/new-umdialplan",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMHuntGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umhuntgroup",
+ "redirect_url": "/powershell/module/exchange/new-umhuntgroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umipgateway",
+ "redirect_url": "/powershell/module/exchange/new-umipgateway",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/New-UMMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-ummailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/new-ummailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umautoattendant",
+ "redirect_url": "/powershell/module/exchange/remove-umautoattendant",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umcallansweringrule",
+ "redirect_url": "/powershell/module/exchange/remove-umcallansweringrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMDialPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umdialplan",
+ "redirect_url": "/powershell/module/exchange/remove-umdialplan",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMHuntGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umhuntgroup",
+ "redirect_url": "/powershell/module/exchange/remove-umhuntgroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umipgateway",
+ "redirect_url": "/powershell/module/exchange/remove-umipgateway",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Remove-UMMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ummailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/remove-ummailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umautoattendant",
+ "redirect_url": "/powershell/module/exchange/set-umautoattendant",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umcallansweringrule",
+ "redirect_url": "/powershell/module/exchange/set-umcallansweringrule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMCallRouterSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umcallroutersettings",
+ "redirect_url": "/powershell/module/exchange/set-umcallroutersettings",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMDialPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umdialplan",
+ "redirect_url": "/powershell/module/exchange/set-umdialplan",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umipgateway",
+ "redirect_url": "/powershell/module/exchange/set-umipgateway",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ummailbox",
+ "redirect_url": "/powershell/module/exchange/set-ummailbox",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMMailboxPIN.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ummailboxpin",
+ "redirect_url": "/powershell/module/exchange/set-ummailboxpin",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ummailboxpolicy",
+ "redirect_url": "/powershell/module/exchange/set-ummailboxpolicy",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UmServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umserver",
+ "redirect_url": "/powershell/module/exchange/set-umserver",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Set-UMService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umservice",
+ "redirect_url": "/powershell/module/exchange/set-umservice",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/unified-messaging/Test-UMConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-umconnectivity",
+ "redirect_url": "/powershell/module/exchange/test-umconnectivity",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Add-DistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-distributiongroupmember",
+ "redirect_url": "/powershell/module/exchange/add-distributiongroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Add-UnifiedGroupLinks.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-unifiedgrouplinks",
+ "redirect_url": "/powershell/module/exchange/add-unifiedgrouplinks",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Disable-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/disable-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Disable-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailcontact",
+ "redirect_url": "/powershell/module/exchange/disable-mailcontact",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Disable-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailuser",
+ "redirect_url": "/powershell/module/exchange/disable-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Enable-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/enable-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Enable-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailcontact",
+ "redirect_url": "/powershell/module/exchange/enable-mailcontact",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Enable-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailuser",
+ "redirect_url": "/powershell/module/exchange/enable-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-Contact.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contact",
+ "redirect_url": "/powershell/module/exchange/get-contact",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/get-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-DistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-distributiongroupmember",
+ "redirect_url": "/powershell/module/exchange/get-distributiongroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-DynamicDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dynamicdistributiongroup",
+ "redirect_url": "/powershell/module/exchange/get-dynamicdistributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-EligibleDistributionGroupForMigration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-eligibledistributiongroupformigration",
+ "redirect_url": "/powershell/module/exchange/get-eligibledistributiongroupformigration",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-Group.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-group",
+ "redirect_url": "/powershell/module/exchange/get-group",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-LinkedUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-linkeduser",
+ "redirect_url": "/powershell/module/exchange/get-linkeduser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailcontact",
+ "redirect_url": "/powershell/module/exchange/get-mailcontact",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailuser",
+ "redirect_url": "/powershell/module/exchange/get-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-Recipient.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recipient",
+ "redirect_url": "/powershell/module/exchange/get-recipient",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-SecurityPrincipal.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-securityprincipal",
+ "redirect_url": "/powershell/module/exchange/get-securityprincipal",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-UnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-unifiedgroup",
+ "redirect_url": "/powershell/module/exchange/get-unifiedgroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-UnifiedGroupLinks.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-unifiedgrouplinks",
+ "redirect_url": "/powershell/module/exchange/get-unifiedgrouplinks",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Get-User.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-user",
+ "redirect_url": "/powershell/module/exchange/get-user",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/New-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/new-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/New-DynamicDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dynamicdistributiongroup",
+ "redirect_url": "/powershell/module/exchange/new-dynamicdistributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/New-EOPDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/new-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/New-EOPMailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailuser",
+ "redirect_url": "/powershell/module/exchange/new-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/New-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailcontact",
+ "redirect_url": "/powershell/module/exchange/new-mailcontact",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/New-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailuser",
+ "redirect_url": "/powershell/module/exchange/new-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/New-UnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-unifiedgroup",
+ "redirect_url": "/powershell/module/exchange/new-unifiedgroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/remove-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-DistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroupmember",
+ "redirect_url": "/powershell/module/exchange/remove-distributiongroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-DynamicDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dynamicdistributiongroup",
+ "redirect_url": "/powershell/module/exchange/remove-dynamicdistributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-EOPDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/remove-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-EOPMailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailuser",
+ "redirect_url": "/powershell/module/exchange/remove-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailcontact",
+ "redirect_url": "/powershell/module/exchange/remove-mailcontact",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailuser",
+ "redirect_url": "/powershell/module/exchange/remove-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-UnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedgroup",
+ "redirect_url": "/powershell/module/exchange/remove-unifiedgroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Remove-UnifiedGroupLinks.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedgrouplinks",
+ "redirect_url": "/powershell/module/exchange/remove-unifiedgrouplinks",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-Contact.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-contact",
+ "redirect_url": "/powershell/module/exchange/set-contact",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/set-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-DynamicDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dynamicdistributiongroup",
+ "redirect_url": "/powershell/module/exchange/set-dynamicdistributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/set-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-group",
+ "redirect_url": "/powershell/module/exchange/set-group",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPMailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailuser",
+ "redirect_url": "/powershell/module/exchange/set-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-EOPUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-user",
+ "redirect_url": "/powershell/module/exchange/set-user",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-Group.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-group",
+ "redirect_url": "/powershell/module/exchange/set-group",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-LinkedUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-linkeduser",
+ "redirect_url": "/powershell/module/exchange/set-linkeduser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailcontact",
+ "redirect_url": "/powershell/module/exchange/set-mailcontact",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailuser",
+ "redirect_url": "/powershell/module/exchange/set-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-UnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-unifiedgroup",
+ "redirect_url": "/powershell/module/exchange/set-unifiedgroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Set-User.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-user",
+ "redirect_url": "/powershell/module/exchange/set-user",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Undo-SoftDeletedUnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/undo-softdeletedunifiedgroup",
+ "redirect_url": "/powershell/module/exchange/undo-softdeletedunifiedgroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Update-DistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-distributiongroupmember",
+ "redirect_url": "/powershell/module/exchange/update-distributiongroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Update-EOPDistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-distributiongroupmember",
+ "redirect_url": "/powershell/module/exchange/update-distributiongroupmember",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/users-and-groups/Upgrade-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/upgrade-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/upgrade-distributiongroup",
"redirect_document_id": false
},
{
@@ -6622,47 +6622,47 @@
},
{
"source_path": "exchange/virtual-folder/exchange/Get-TenantAnalyticsConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig",
+ "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-TenantAnalyticsConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-myanalyticsfeatureconfig",
+ "redirect_url": "/powershell/module/exchange/set-myanalyticsfeatureconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-UserAnalyticsConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig",
+ "redirect_url": "/powershell/module/exchange/get-myanalyticsfeatureconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-UserAnalyticsConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-myanalyticsfeatureconfig",
+ "redirect_url": "/powershell/module/exchange/set-myanalyticsfeatureconfig",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-MailDetailMalwareReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailatpreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-MailDetailSpamReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailatpreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionTrafficReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailatpreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-UrlTrace.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safelinksaggregatereport",
+ "redirect_url": "/powershell/module/exchange/get-safelinksaggregatereport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-MailTrafficReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
+ "redirect_url": "/powershell/module/exchange/get-maildetailatpreport",
"redirect_document_id": false
},
{
@@ -6757,87 +6757,87 @@
},
{
"source_path": "exchange/virtual-folder/exchange/Get-RMSTrustedPublishingDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates",
+ "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Import-RMSTrustedPublishingDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates",
+ "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-RMSTrustedPublishingDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates",
+ "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-RMSTrustedPublishingDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/#encryption-and-certificates",
+ "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-CustomNudge.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-CustomNudgeAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-CustomNudgeSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/New-CustomNudge.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/New-CustomNudgeAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-CustomNudge.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-CustomNudgeAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-CustomNudge.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-CustomNudgeAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-CustomNudgeSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/",
+ "redirect_url": "/powershell/module/exchange/",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-MailTrafficTopReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficsummaryreport",
+ "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-PhishFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-tenantallowblocklistspoofitems",
+ "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistspoofitems",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-PhishFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-tenantallowblocklistspoofitems",
+ "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistspoofitems",
"redirect_document_id": false
},
{
@@ -6862,47 +6862,47 @@
},
{
"source_path": "exchange/virtual-folder/exchange/New-EOPDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/new-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/New-EOPMailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailuser",
+ "redirect_url": "/powershell/module/exchange/new-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-EOPDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/remove-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-EOPMailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailuser",
+ "redirect_url": "/powershell/module/exchange/remove-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-EOPDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-distributiongroup",
+ "redirect_url": "/powershell/module/exchange/set-distributiongroup",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-EOPGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-group",
+ "redirect_url": "/powershell/module/exchange/set-group",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-EOPMailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailuser",
+ "redirect_url": "/powershell/module/exchange/set-mailuser",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-EOPUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-user",
+ "redirect_url": "/powershell/module/exchange/set-user",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Update-EOPDistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-distributiongroupmember",
+ "redirect_url": "/powershell/module/exchange/update-distributiongroupmember",
"redirect_document_id": false
},
{
@@ -6922,42 +6922,42 @@
},
{
"source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionDocumentDetail.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contentmalwaremdodetailreport",
+ "redirect_url": "/powershell/module/exchange/get-contentmalwaremdodetailreport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-AdvancedThreatProtectionDocumentReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contentmalwaremdoaggregatereport",
+ "redirect_url": "/powershell/module/exchange/get-contentmalwaremdoaggregatereport",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/New-SecOpsOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-exosecopsoverriderule",
+ "redirect_url": "/powershell/module/exchange/new-exosecopsoverriderule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-SecOpsOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-exosecopsoverriderule",
+ "redirect_url": "/powershell/module/exchange/remove-exosecopsoverriderule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-SecOpsOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exosecopsoverriderule",
+ "redirect_url": "/powershell/module/exchange/set-exosecopsoverriderule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/New-PhishSimOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-exophishsimoverriderule",
+ "redirect_url": "/powershell/module/exchange/new-exophishsimoverriderule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-PhishSimOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-exophishsimoverriderule",
+ "redirect_url": "/powershell/module/exchange/remove-exophishsimoverriderule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-PhishSimOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exophishsimoverriderule",
+ "redirect_url": "/powershell/module/exchange/set-exophishsimoverriderule",
"redirect_document_id": false
},
{
@@ -7122,12 +7122,12 @@
},
{
"source_path": "exchange/virtual-folder/exchange/Get-PhishSimOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exophishsimoverriderule",
+ "redirect_url": "/powershell/module/exchange/get-exophishsimoverriderule",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-SecOpsOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exosecopsoverriderule",
+ "redirect_url": "/powershell/module/exchange/get-exosecopsoverriderule",
"redirect_document_id": false
},
{
@@ -7137,7103 +7137,68 @@
},
{
"source_path": "exchange/virtual-folder/exchange/Get-AuditConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert",
+ "redirect_url": "/powershell/module/exchange/get-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/New-AuditConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert",
+ "redirect_url": "/powershell/module/exchange/new-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-AuditConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert",
+ "redirect_url": "/powershell/module/exchange/remove-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-AuditConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert",
+ "redirect_url": "/powershell/module/exchange/get-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/New-AuditConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert",
+ "redirect_url": "/powershell/module/exchange/new-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-AuditConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert",
+ "redirect_url": "/powershell/module/exchange/remove-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-AuditConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-protectionalert",
+ "redirect_url": "/powershell/module/exchange/set-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Get-ActivityAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert",
+ "redirect_url": "/powershell/module/exchange/get-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/New-ActivityAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert",
+ "redirect_url": "/powershell/module/exchange/new-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-ActivityAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert",
+ "redirect_url": "/powershell/module/exchange/remove-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Set-ActivityAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-protectionalert",
+ "redirect_url": "/powershell/module/exchange/set-protectionalert",
"redirect_document_id": false
},
{
"source_path": "exchange/virtual-folder/exchange/Remove-RecordLabel.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-label",
+ "redirect_url": "/powershell/module/exchange/remove-label",
"redirect_document_id": false
},
{
"source_path": "exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md",
"redirect_url": "/powershell/exchange/connect-to-exchange-online-powershell",
"redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-ADPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-adpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-attachmentfilterentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-availabilityaddressspace",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-ComplianceCaseMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-compliancecasemember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-contentfilterphrase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-databaseavailabilitygroupserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-DistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-distributiongroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-FederatedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-federateddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-globalmonitoringoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-IPAllowListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ipallowlistentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ipallowlistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-IPBlockListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ipblocklistentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ipblocklistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-mailboxdatabasecopy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-mailboxfolderpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-MailboxPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-mailboxpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-managementroleentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-publicfolderadministrativepermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-publicfolderclientpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-RecipientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-recipientpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-ResubmitRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-resubmitrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-RoleGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-rolegroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-servermonitoringoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-unifiedgrouplinks",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-vivamodulefeaturepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-vivaorginsightsdelegatedrole",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md",
- "redirect_url": "/powershell/module/exchangepowershell/add-ediscoverycaseadmin",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Check-PurviewConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/check-purviewconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Clean-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/clean-mailboxdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/clear-activesyncdevice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Clear-MobileDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/clear-mobiledevice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md",
- "redirect_url": "/powershell/module/exchangepowershell/clear-textmessagingaccount",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md",
- "redirect_url": "/powershell/module/exchangepowershell/compare-textmessagingverificationcode",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Complete-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/complete-migrationbatch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Connect-ExchangeOnline.md",
- "redirect_url": "/powershell/module/exchangepowershell/connect-exchangeonline",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Connect-IPPSSession.md",
- "redirect_url": "/powershell/module/exchangepowershell/connect-ippssession",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Connect-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/connect-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Delete-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/delete-quarantinemessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-atpprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-AddressListPaging.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-addresslistpaging",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-antiphishrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-app",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-cmdletextensionagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-distributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-dnssecforverifieddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-eopprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-hostedcontentfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-hostedoutboundspamfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-ipv6foraccepteddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-inboxrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-JournalArchiving.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-journalarchiving",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-journalrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailcontact",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-MailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailpublicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-mailboxquarantine",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-malwarefilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-metacachedatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-outlookanywhere",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-outlookprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-pushnotificationproxy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-remotemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-reportsubmissionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-safeattachmentrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-safelinksrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-serviceemailchannel",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-smtpdaneinbound",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-sweeprule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-transportagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-transportrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umcallansweringrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umipgateway",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-UMMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-ummailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-UMServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disable-UMService.md",
- "redirect_url": "/powershell/module/exchangepowershell/disable-umservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md",
- "redirect_url": "/powershell/module/exchangepowershell/disconnect-exchangeonline",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Dismount-Database.md",
- "redirect_url": "/powershell/module/exchangepowershell/dismount-database",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Dump-ProvisioningCache.md",
- "redirect_url": "/powershell/module/exchangepowershell/dump-provisioningcache",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-atpprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-AddressListPaging.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-addresslistpaging",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-antiphishrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-AntispamUpdates.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-antispamupdates",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-app",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-cmdletextensionagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-compliancetagstorage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-distributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-dnssecforverifieddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-eopprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-exchangecertificate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-hostedcontentfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-hostedoutboundspamfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-ipv6foraccepteddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-inboxrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-journalrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailcontact",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-MailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailpublicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-mailboxquarantine",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-malwarefilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-metacachedatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-organizationcustomization",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-outlookanywhere",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-outlookprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-pushnotificationproxy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-remotemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-reportsubmissionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-safeattachmentrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-safelinksrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-serviceemailchannel",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-smtpdaneinbound",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-sweeprule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-transportagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-transportrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umcallansweringrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umipgateway",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-UMMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-ummailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-UMServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Enable-UMService.md",
- "redirect_url": "/powershell/module/exchangepowershell/enable-umservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/exchange.md",
- "redirect_url": "/powershell/module/exchangepowershell/exchangepowershell",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md",
- "redirect_url": "/powershell/module/exchangepowershell/execute-azureadlabelsync",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Expedite-Delicensing.md",
- "redirect_url": "/powershell/module/exchangepowershell/expedite-delicensing",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-ActiveSyncLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-activesynclog",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-ActivityExplorerData.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-activityexplorerdata",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-autodiscoverconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-ContentExplorerData.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-contentexplorerdata",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-dlppolicycollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-exchangecertificate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-FilePlanProperty.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-fileplanproperty",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-JournalRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-journalrulecollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-mailboxdiagnosticlogs",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-message",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-MigrationReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-migrationreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-quarantinemessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-RecipientDataProperty.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-recipientdataproperty",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-TransportRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-transportrulecollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-UMCallDataRecord.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-umcalldatarecord",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Export-UMPrompt.md",
- "redirect_url": "/powershell/module/exchangepowershell/export-umprompt",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ADPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ADServerSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adserversettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ADSite.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adsite",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-atpbuiltinprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-atpprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-atptotaltrafficreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-accepteddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-accesstocustomerdatarequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdevice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceautoblockthreshold",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdeviceclass",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncdevicestatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncmailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncorganizationsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-activesyncvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AdSiteLink.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adsitelink",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AdaptiveScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adaptivescope",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AddressBookPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-addressbookpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-addresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-addressrewriteentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-adminauditlogconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AdministrativeUnit.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-administrativeunit",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AgentLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-agentlog",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AggregateZapReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-aggregatezapreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-antiphishpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-antiphishrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-app",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-appretentioncompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-appretentioncompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-applicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ArcConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-arcconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-atppolicyforo365",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-attachmentfilterentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-attachmentfilterlistconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AuditConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-auditconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AuditLogSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-auditlogsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AuthConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-authconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AuthRedirect.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-authredirect",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AuthServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-authserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-authenticationpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-autosensitivitylabelpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-autosensitivitylabelrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-autodiscovervirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-availabilityaddressspace",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AvailabilityConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-availabilityconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-availabilityreportoutage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-BlockedConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-blockedconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-blockedsenderaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CASMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-casmailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CASMailboxPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-casmailboxplan",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CalendarDiagnosticAnalysis.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticanalysis",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticlog",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendardiagnosticobjects",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CalendarNotification.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendarnotification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CalendarProcessing.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-calendarprocessing",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-caseholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CaseHoldRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-caseholdrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-classificationrulecollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ClientAccessArray.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessarray",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ClientAccessServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ClientAccessService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clientaccessservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Clutter.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-clutter",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-cmdletextensionagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceCase.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancecase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancecasemember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-complianceretentionevent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-complianceretentioneventtype",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancesearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancesearchaction",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancesecurityfilter",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancetag",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compliancetagstorage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compromiseduseraggregatereport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-compromiseduserdetailreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-configanalyzerpolicyrecommendation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ConnectionInformation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-connectioninformation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Contact.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contact",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ContentFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contentfilterconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contentfilterphrase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contentmalwaremdoaggregatereport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-contentmalwaremdodetailreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dataclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DataClassificationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dataclassificationconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dataencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DataRetentionReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dataretentionreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-databaseavailabilitygroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-databaseavailabilitygroupnetwork",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-defaulttenantbriefingconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-defaulttenantmyanalyticsfeatureconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deliveryagentconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DetailZapReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-detailzapreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DetailsTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-detailstemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deviceconditionalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deviceconditionalaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deviceconfigurationpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-deviceconfigurationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DevicePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-devicepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-devicetenantpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DeviceTenantRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-devicetenantrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-distributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-distributiongroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DkimSigningConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dkimsigningconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpcompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpcompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpDetailReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpdetailreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpdetectionsreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpEdmSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpedmschema",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpincidentdetailreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpkeyworddictionary",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlppolicytemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpsensitiveinformationtyperulepackage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dlpsidetectionsreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dnssecstatusforverifieddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DomainController.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-domaincontroller",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dynamicdistributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-DynamicDistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-dynamicdistributiongroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-eopprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXOCasMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exocasmailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXOMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxfolderpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxfolderstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomailboxstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exomobiledevicestatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXORecipient.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exorecipient",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EXORecipientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exorecipientpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ecpvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EdgeSubscription.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-edgesubscription",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-edgesyncserviceconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-eligibledistributiongroupformigration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-emailaddresspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EmailTenantSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-emailtenantsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EtrLimits.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-etrlimits",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EventLogLevel.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-eventloglevel",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-eventsfromemailconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangeassistanceconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangecertificate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangediagnosticinfo",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExchangeFeature.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangefeature",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExchangeServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserveraccesslicense",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangeserveraccesslicenseuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExchangeSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exchangesettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exoinformationbarrierpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exoinformationbarrierrelationship",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exoinformationbarriersegment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exophishsimoverriderule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-exosecopsoverriderule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ExternalInOutlook.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-externalinoutlook",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-failedcontentindexdocuments",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FeatureConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-featureconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FederatedDomainProof.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-federateddomainproof",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-federatedorganizationidentifier",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FederationInformation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-federationinformation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-federationtrust",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-fileplanpropertyauthority",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-fileplanpropertycategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-fileplanpropertycitation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-fileplanpropertydepartment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-fileplanpropertyreferenceid",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-fileplanpropertystructure",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-fileplanpropertysubcategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FocusedInbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-focusedinbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ForeignConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-foreignconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-FrontendTransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-frontendtransportservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-globaladdresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-globalmonitoringoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Group.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-group",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HealthReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-healthreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HistoricalSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-historicalsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-holdcompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HoldComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-holdcompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedconnectionfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedcontentfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedcontentfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedoutboundspamfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hostedoutboundspamfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hybridconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-hybridmailflowdatacenterips",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPAllowListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPAllowListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipallowlistprovidersconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPBlockListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPBlockListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipblocklistprovidersconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ipv6statusforaccepteddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IRMConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-irmconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ImapSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-imapsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-InboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-inboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-inboxrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierpoliciesapplicationstatus",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-informationbarrierrecipientstatus",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-intraorganizationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-intraorganizationconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-journalrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Label.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-label",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-LabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-labelpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-LinkedUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-linkeduser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-LogonStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-logonstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-m365dataatrestencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-m365dataatrestencryptionpolicyassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailcontact",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailDetailATPReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailatpreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetaildlppolicyreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailencryptionreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-maildetailtransportrulereport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailFilterListReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailfilterlistreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailpublicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficatpreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficencryptionreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficpolicyreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailtrafficsummaryreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxauditbypassassociation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxautoreplyconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxcalendarconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxcalendarfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxdatabasecopystatus",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxexportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxexportrequeststatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolderpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxfolderstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxirmaccess",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboximportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboximportrequeststatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxjunkemailconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxLocation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxlocation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxmessageconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxplan",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxregionalconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrepairrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrestorerequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxrestorerequeststatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxsentitemsconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxspellingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxTransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxtransportservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailboxuserconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MailflowStatusReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mailflowstatusreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-malwarefilteringserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ManagedContentSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managedcontentsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ManagedFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managedfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managedfoldermailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ManagementRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managementrole",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managementroleassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ManagementRoleEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managementroleentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ManagementScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-managementscope",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mapivirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-message",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MessageCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagecategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MessageClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messageclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MessageTrace.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetrace",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MessageTraceDetail.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetracedetail",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetracedetailv2",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MessageTraceV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetracev2",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MessageTrackingLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetrackinglog",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MessageTrackingReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-messagetrackingreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationbatch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MigrationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MigrationEndpoint.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationendpoint",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MigrationStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-migrationuserstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MobileDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevicemailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mobiledevicestatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-monitoringitemhelp",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-monitoringitemidentity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-moverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-moverequeststatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MxRecordReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-mxrecordreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-networkconnectioninfo",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Notification.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-notification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OMEConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-omeconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OMEMessageStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-omemessagestatus",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-oabvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-offlineaddressbook",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-onpremisesorganization",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OnlineMeetingConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-onlinemeetingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OrganizationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-organizationconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-organizationrelationship",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OrganizationSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-organizationsegment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OrganizationalUnit.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-organizationalunit",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outboundconnectorreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OutlookAnywhere.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outlookanywhere",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outlookprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OutlookProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-outlookprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-owamailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-owavirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PartnerApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-partnerapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-pendingdelicenseuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-pendingfederateddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PerimeterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-perimeterconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-phishsimoverridepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Place.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-place",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PolicyConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-policyconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PolicyTipConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-policytipconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PopSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-popsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-powershellvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ProtectionAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-protectionalert",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderadministrativepermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderclientpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderitemstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxdiagnostics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxmigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermailboxmigrationrequeststatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermigrationrequeststatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermoverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfoldermoverequeststatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-publicfolderstatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-quarantinemessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-QuarantineMessageHeader.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-quarantinemessageheader",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-QuarantinePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-quarantinepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Queue.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-queue",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-QueueDigest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-queuedigest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RMSTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-rmstemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ReceiveConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-receiveconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Recipient.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recipient",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recipientfilterconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RecipientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recipientpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recipientstatisticsreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recordreviewnotificationtemplateconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RecoverableItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-recoverableitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-regulatorycomplianceui",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RemoteDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-remotedomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-remotemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-reportexecutioninstance",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-reportsubmissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-reportsubmissionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ResourceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-resourceconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ResubmitRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-resubmitrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentioncompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RetentionEvent.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentionevent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-retentionpolicytag",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ReviewItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-reviewitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-roleassignmentpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RoleGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-rolegroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RoleGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-rolegroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-routinggroupconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-RpcClientAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-rpcclientaccess",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SCInsights.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-scinsights",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safeattachmentpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safeattachmentrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safelinksaggregatereport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safelinksdetailreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safelinkspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-safelinksrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-searchdocumentformat",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-secopsoverridepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SecurityPrincipal.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-securityprincipal",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SendConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sendconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SenderFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-senderfilterconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SenderIdConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-senderidconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SenderReputationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-senderreputationconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ServerComponentState.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-servercomponentstate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ServerHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-serverhealth",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-servermonitoringoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-servicedeliveryreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ServicePrincipal.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-serviceprincipal",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SettingOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-settingoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SharingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sharingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sitemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sitemailboxdiagnostics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sitemailboxprovisioningpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SmimeConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-smimeconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-smtpdaneinboundstatus",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-spoofintelligenceinsight",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SpoofMailReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-spoofmailreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-storeusagestatistics",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewactivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewoverallprogressreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewpolicyreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewpolicyv2",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-supervisoryreviewtopcasesreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-sweeprule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-SystemMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-systemmessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-teamsprotectionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-teamsprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-tenantallowblocklistitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-tenantallowblocklistspoofitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TextMessagingAccount.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-textmessagingaccount",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-throttlingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-throttlingpolicyassociation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TransportConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TransportPipeline.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportpipeline",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TransportRuleAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportruleaction",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TransportRulePredicate.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportrulepredicate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TransportServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-TransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-transportservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-Trust.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-trust",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMActiveCalls.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umactivecalls",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umcallansweringrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMCallDataRecord.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umcalldatarecord",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umcallroutersettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umcallsummaryreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMDialPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMHuntGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umhuntgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umipgateway",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ummailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMMailboxPIN.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ummailboxpin",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ummailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UMService.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UmServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-umserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-unifiedauditlogretentionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-unifiedgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-unifiedgrouplinks",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-User.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-user",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UserBriefingConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-userbriefingconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UserPhoto.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-userphoto",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-userprincipalnamessuffix",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-vivainsightssettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-VivaModuleFeature.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-vivamodulefeature",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-vivamodulefeatureenablement",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-vivamodulefeaturepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-vivaorginsightsdelegatedrole",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-webservicesvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-x400authoritativedomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md",
- "redirect_url": "/powershell/module/exchangepowershell/get-ediscoverycaseadmin",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-dlppolicycollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-dlppolicytemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Import-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-exchangecertificate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Import-FilePlanProperty.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-fileplanproperty",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Import-JournalRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-journalrulecollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Import-RecipientDataProperty.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-recipientdataproperty",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Import-TransportRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-transportrulecollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Import-UMPrompt.md",
- "redirect_url": "/powershell/module/exchangepowershell/import-umprompt",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Install-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/install-transportagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md",
- "redirect_url": "/powershell/module/exchangepowershell/install-unifiedcomplianceprerequisite",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md",
- "redirect_url": "/powershell/module/exchangepowershell/invoke-compliancesearchactionstep",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/invoke-compliancesecurityfilteraction",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/invoke-holdremovalaction",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md",
- "redirect_url": "/powershell/module/exchangepowershell/invoke-monitoringprobe",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Mount-Database.md",
- "redirect_url": "/powershell/module/exchangepowershell/mount-database",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/move-activemailboxdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Move-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/move-addresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Move-DatabasePath.md",
- "redirect_url": "/powershell/module/exchangepowershell/move-databasepath",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Move-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/move-offlineaddressbook",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-atpbuiltinprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-atpprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-accepteddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-activesyncdeviceaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-activesyncmailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-activesyncvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AdaptiveScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-adaptivescope",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AddressBookPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-addressbookpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-addresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AddressRewriteEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-addressrewriteentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-adminauditlogsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AntiPhishPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-antiphishpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-antiphishrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-app",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-appretentioncompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-appretentioncompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-applicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AuthRedirect.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-authredirect",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AuthServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-authserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AuthenticationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-authenticationpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-autosensitivitylabelpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-autosensitivitylabelrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-autodiscovervirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AvailabilityConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-availabilityconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-availabilityreportoutage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-CaseHoldPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-caseholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-CaseHoldRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-caseholdrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-classificationrulecollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ClientAccessArray.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-clientaccessarray",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-clientaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ComplianceCase.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancecase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-complianceretentionevent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-complianceretentioneventtype",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancesearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ComplianceSearchAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancesearchaction",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancesecurityfilter",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ComplianceTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-compliancetag",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dataclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dataencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-databaseavailabilitygroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-databaseavailabilitygroupnetwork",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deliveryagentconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deviceconditionalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deviceconditionalaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deviceconfigurationpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-deviceconfigurationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-devicetenantpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DeviceTenantRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-devicetenantrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-distributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DkimSigningConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dkimsigningconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpcompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DlpComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpcompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DlpEdmSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpedmschema",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DlpFingerprint.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpfingerprint",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpkeyworddictionary",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DlpPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dlpsensitiveinformationtyperulepackage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-dynamicdistributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-eopprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-ecpvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-EdgeSubscription.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-edgesubscription",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-edgesyncserviceconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-emailaddresspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-exchangecertificate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ExchangeSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-exchangesettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-exophishsimoverriderule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-exosecopsoverriderule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-FeatureConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-featureconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-federationtrust",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-fileplanpropertyauthority",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-fileplanpropertycategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-fileplanpropertycitation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-fileplanpropertydepartment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-fileplanpropertyreferenceid",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-fileplanpropertysubcategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-Fingerprint.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-fingerprint",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ForeignConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-foreignconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-globaladdresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-holdcompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-HoldComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-holdcompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hostedcontentfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hostedcontentfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hostedoutboundspamfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hostedoutboundspamfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-hybridconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-InboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-inboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-inboxrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-informationbarrierpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-intraorganizationconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-journalrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-Label.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-label",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-LabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-labelpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-M365DataAtRestEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-m365dataatrestencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailcontact",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailmessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailboxAuditLogSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxauditlogsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxexportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailboxFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboximportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailboxRepairRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxrepairrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxrestorerequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mailboxsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-malwarefilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-malwarefilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ManagedContentSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managedcontentsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ManagedFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managedfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ManagedFolderMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managedfoldermailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ManagementRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managementrole",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ManagementRoleAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managementroleassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ManagementScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-managementscope",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mapivirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MessageClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-messageclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-migrationbatch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MigrationEndpoint.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-migrationendpoint",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MobileDeviceMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-mobiledevicemailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-moverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OMEConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-omeconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OabVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-oabvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-offlineaddressbook",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OnPremisesOrganization.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-onpremisesorganization",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-organizationrelationship",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OrganizationSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-organizationsegment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-outboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-outlookprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OutlookProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-outlookprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OwaMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-owamailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-OwaVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-owavirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PartnerApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-partnerapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PhishSimOverridePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-phishsimoverridepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PolicyTipConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-policytipconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PowerShellVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-powershellvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ProtectionAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-protectionalert",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PublicFolderDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfolderdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PublicFolderDatabaseRepairRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfolderdatabaserepairrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfoldermigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-publicfoldermoverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-QuarantinePermissions.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-quarantinepermissions",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-QuarantinePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-quarantinepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ReceiveConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-receiveconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RemoteDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-remotedomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-remotemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ReportSubmissionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-reportsubmissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ReportSubmissionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-reportsubmissionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentioncompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RetentionPolicyTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-retentionpolicytag",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RoleAssignmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-roleassignmentpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RoleGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-rolegroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RoutingGroupConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-routinggroupconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-RpcClientAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-rpcclientaccess",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SafeAttachmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-safeattachmentpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-safeattachmentrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SafeLinksPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-safelinkspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-safelinksrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SearchDocumentFormat.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-searchdocumentformat",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SecOpsOverridePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-secopsoverridepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SendConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sendconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ServicePrincipal.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-serviceprincipal",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SettingOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-settingoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SharingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sharingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sitemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SiteMailboxProvisioningPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sitemailboxprovisioningpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SupervisoryReviewPolicyV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-supervisoryreviewpolicyv2",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SupervisoryReviewRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-supervisoryreviewrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-sweeprule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SyncMailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-syncmailpublicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-SystemMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-systemmessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-TeamsProtectionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-teamsprotectionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-TeamsProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-teamsprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-TenantAllowBlockListItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-tenantallowblocklistitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-TenantAllowBlockListSpoofItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-tenantallowblocklistspoofitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-ThrottlingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-throttlingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-transportrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umcallansweringrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-UMDialPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-UMHuntGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umhuntgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-umipgateway",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-UMMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-ummailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-UnifiedAuditLogRetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-unifiedauditlogretentionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-UnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-unifiedgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-WebServicesVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-webservicesvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/New-X400AuthoritativeDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/new-x400authoritativedomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Preview-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/preview-quarantinemessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Redirect-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/redirect-message",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Release-QuarantineMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/release-quarantinemessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ADPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-adpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ATPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-atpprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-accepteddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ActiveSyncDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdevice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdeviceaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ActiveSyncDeviceClass.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncdeviceclass",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ActiveSyncMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncmailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ActiveSyncVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-activesyncvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AdaptiveScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-adaptivescope",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AddressBookPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-addressbookpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-addresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AddressRewriteEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-addressrewriteentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AntiPhishPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-antiphishpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-antiphishrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-app",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AppRetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-appretentioncompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AppRetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-appretentioncompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-applicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AttachmentFilterEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-attachmentfilterentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AuthRedirect.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-authredirect",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AuthServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-authserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-authenticationpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-autosensitivitylabelpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AutoSensitivityLabelRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-autosensitivitylabelrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AutodiscoverVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-autodiscovervirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AvailabilityAddressSpace.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityaddressspace",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AvailabilityConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-AvailabilityReportOutage.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-availabilityreportoutage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-BlockedConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-blockedconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-BlockedSenderAddress.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-blockedsenderaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-CalendarEvents.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-calendarevents",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-CaseHoldPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-caseholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-CaseHoldRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-caseholdrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ClassificationRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-classificationrulecollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ClientAccessArray.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-clientaccessarray",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-clientaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ComplianceCase.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancecase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ComplianceCaseMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancecasemember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ComplianceRetentionEventType.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-complianceretentioneventtype",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ComplianceSearchAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesearchaction",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ComplianceSecurityFilter.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancesecurityfilter",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ComplianceTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-compliancetag",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ContentFilterPhrase.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-contentfilterphrase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dataclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupNetwork.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroupnetwork",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DatabaseAvailabilityGroupServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-databaseavailabilitygroupserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DeliveryAgentConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deliveryagentconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconditionalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DeviceConditionalAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconditionalaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DeviceConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconfigurationpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DeviceConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-deviceconfigurationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DeviceTenantPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-devicetenantpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DeviceTenantRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-devicetenantrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-distributiongroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DlpCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpcompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DlpComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpcompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DlpEdmSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpedmschema",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DlpKeywordDictionary.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpkeyworddictionary",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DlpPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DlpPolicyTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlppolicytemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationType.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtype",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DlpSensitiveInformationTypeRulePackage.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtyperulepackage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-DynamicDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-dynamicdistributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-EOPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-eopprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-EcpVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ecpvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-EdgeSubscription.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-edgesubscription",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-emailaddresspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ExchangeCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-exchangecertificate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ExoPhishSimOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-exophishsimoverriderule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ExoSecOpsOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-exosecopsoverriderule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FeatureConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-featureconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FederatedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-federateddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-federationtrust",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FilePlanPropertyAuthority.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-fileplanpropertyauthority",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FilePlanPropertyCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-fileplanpropertycategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FilePlanPropertyCitation.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-fileplanpropertycitation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FilePlanPropertyDepartment.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-fileplanpropertydepartment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FilePlanPropertyReferenceId.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-fileplanpropertyreferenceid",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-FilePlanPropertySubCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-fileplanpropertysubcategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ForeignConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-foreignconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-globaladdresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-GlobalMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-globalmonitoringoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-HoldCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-holdcompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-HoldComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-holdcompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-HostedContentFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hostedcontentfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hostedcontentfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hostedoutboundspamfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hostedoutboundspamfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-hybridconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-IPAllowListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ipallowlistentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ipallowlistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-IPBlockListEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ipblocklistentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ipblocklistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-InboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-inboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-inboxrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-InformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-informationbarrierpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-IntraOrganizationConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-intraorganizationconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-journalrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-Label.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-label",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-LabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-labelpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailcontact",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxdatabasecopy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxexportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxfolderpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxIRMAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxirmaccess",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboximportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxRepairRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxrepairrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxrestorerequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MailboxUserConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mailboxuserconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MalwareFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-malwarefilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-malwarefilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ManagedContentSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managedcontentsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ManagedFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managedfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ManagedFolderMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managedfoldermailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ManagementRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managementrole",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ManagementRoleAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managementroleassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ManagementRoleEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managementroleentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ManagementScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-managementscope",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MapiVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mapivirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-message",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MessageClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-messageclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-migrationbatch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MigrationEndpoint.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-migrationendpoint",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-migrationuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MobileDevice.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mobiledevice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MobileDeviceMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-mobiledevicemailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-moverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OMEConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-omeconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OabVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-oabvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-offlineaddressbook",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OnPremisesOrganization.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-onpremisesorganization",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-organizationrelationship",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OrganizationSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-organizationsegment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-outboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-outlookprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OutlookProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-outlookprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OwaMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-owamailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-OwaVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-owavirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PartnerApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-partnerapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PhishSimOverridePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-phishsimoverridepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PolicyTipConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-policytipconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PowerShellVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-powershellvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ProtectionAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-protectionalert",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PublicFolderAdministrativePermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderadministrativepermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PublicFolderClientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderclientpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PublicFolderDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfolderdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PublicFolderMailboxMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermailboxmigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-publicfoldermoverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-QuarantinePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-quarantinepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ReceiveConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-receiveconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RecipientPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-recipientpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RemoteDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-remotedomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-remotemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ReportSubmissionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-reportsubmissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ReportSubmissionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-reportsubmissionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ResubmitRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-resubmitrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentioncompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RetentionPolicyTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-retentionpolicytag",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RoleAssignmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-roleassignmentpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RoleGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-rolegroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RoleGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-rolegroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RoutingGroupConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-routinggroupconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-RpcClientAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-rpcclientaccess",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SafeAttachmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-safeattachmentpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-safeattachmentrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SafeLinksPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-safelinkspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-safelinksrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SearchDocumentFormat.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-searchdocumentformat",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SecOpsOverridePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-secopsoverridepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SendConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-sendconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ServerMonitoringOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-servermonitoringoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ServicePrincipal.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-serviceprincipal",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SettingOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-settingoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SharingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-sharingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SiteMailboxProvisioningPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-sitemailboxprovisioningpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-StoreMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-storemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SupervisoryReviewPolicyV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-supervisoryreviewpolicyv2",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-sweeprule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SyncMailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-syncmailpublicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-SystemMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-systemmessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-TenantAllowBlockListItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-tenantallowblocklistitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-tenantallowblocklistspoofitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-ThrottlingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-throttlingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-transportrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umcallansweringrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UMDialPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UMHuntGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umhuntgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-umipgateway",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UMMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ummailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UnifiedAuditLogRetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedauditlogretentionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UnifiedGroupLinks.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-unifiedgrouplinks",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-UserPhoto.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-userphoto",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-VivaModuleFeaturePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-vivamodulefeaturepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-VivaOrgInsightsDelegatedRole.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-vivaorginsightsdelegatedrole",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-WebServicesVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-webservicesvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-X400AuthoritativeDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-x400authoritativedomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Remove-eDiscoveryCaseAdmin.md",
- "redirect_url": "/powershell/module/exchangepowershell/remove-ediscoverycaseadmin",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Reset-ProvisioningCache.md",
- "redirect_url": "/powershell/module/exchangepowershell/reset-provisioningcache",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Restore-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/restore-databaseavailabilitygroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Restore-DetailsTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/restore-detailstemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Restore-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/restore-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Restore-RecoverableItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/restore-recoverableitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxdatabasecopy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxexportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-mailboximportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-mailboxrestorerequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-message",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-moverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-publicfoldermigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-publicfoldermoverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-PublicFolderReplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-publicfolderreplication",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Resume-Queue.md",
- "redirect_url": "/powershell/module/exchangepowershell/resume-queue",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Retry-Queue.md",
- "redirect_url": "/powershell/module/exchangepowershell/retry-queue",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Rotate-DkimSigningConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/rotate-dkimsigningconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Search-AdminAuditLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-adminauditlog",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Search-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Search-MailboxAuditLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-mailboxauditlog",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Search-MessageTrackingReport.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-messagetrackingreport",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/search-unifiedauditlog",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Send-TextMessagingVerificationCode.md",
- "redirect_url": "/powershell/module/exchangepowershell/send-textmessagingverificationcode",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ADServerSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adserversettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ADSite.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adsite",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ATPBuiltInProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-atpbuiltinprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ATPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-atpprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AcceptedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-accepteddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AccessToCustomerDataRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-accesstocustomerdatarequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncdeviceaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ActiveSyncDeviceAutoblockThreshold.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncdeviceautoblockthreshold",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ActiveSyncMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncmailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ActiveSyncOrganizationSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncorganizationsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ActiveSyncVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-activesyncvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AdSiteLink.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adsitelink",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AdaptiveScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adaptivescope",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AddressBookPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-addressbookpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-addresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AddressRewriteEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-addressrewriteentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AdminAuditLogConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-adminauditlogconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AntiPhishPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-antiphishpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AntiPhishRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-antiphishrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-App.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-app",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-appretentioncompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AppRetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-appretentioncompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-applicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ArcConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-arcconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-atppolicyforo365",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AttachmentFilterListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-attachmentfilterlistconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AuditConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-auditconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AuthConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-authconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AuthRedirect.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-authredirect",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AuthServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-authserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-authenticationpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-autosensitivitylabelpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-autosensitivitylabelrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AutodiscoverVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-autodiscovervirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AvailabilityConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-availabilityconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-AvailabilityReportOutage.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-availabilityreportoutage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-CASMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-casmailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-CASMailboxPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-casmailboxplan",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-CalendarNotification.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-calendarnotification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-CalendarProcessing.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-calendarprocessing",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-CaseHoldPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-caseholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-CaseHoldRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-caseholdrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ClassificationRuleCollection.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-classificationrulecollection",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ClientAccessArray.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessarray",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ClientAccessServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ClientAccessService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clientaccessservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-Clutter.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-clutter",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-CmdletExtensionAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-cmdletextensionagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ComplianceCase.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancecase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ComplianceRetentionEventType.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-complianceretentioneventtype",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancesearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ComplianceSearchAction.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancesearchaction",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ComplianceSecurityFilter.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancesecurityfilter",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ComplianceTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-compliancetag",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-Contact.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-contact",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ContentFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-contentfilterconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dataclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DataEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dataencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-databaseavailabilitygroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DatabaseAvailabilityGroupNetwork.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-databaseavailabilitygroupnetwork",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DefaultTenantBriefingConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-defaulttenantbriefingconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-defaulttenantmyanalyticsfeatureconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DeliveryAgentConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deliveryagentconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DetailsTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-detailstemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DeviceConditionalAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deviceconditionalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DeviceConditionalAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deviceconditionalaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DeviceConfigurationPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deviceconfigurationpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DeviceConfigurationRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-deviceconfigurationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DeviceTenantPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-devicetenantpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DeviceTenantRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-devicetenantrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-distributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DkimSigningConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dkimsigningconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpcompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DlpComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpcompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DlpEdmSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpedmschema",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DlpKeywordDictionary.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpkeyworddictionary",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DlpPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DlpSensitiveInformationType.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpsensitiveinformationtype",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DlpSensitiveInformationTypeRulePackage.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dlpsensitiveinformationtyperulepackage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-dynamicdistributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-EOPProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-eopprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-EcpVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ecpvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-EdgeSyncServiceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-edgesyncserviceconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-emailaddresspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-EmailTenantSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-emailtenantsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-EventLogLevel.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-eventloglevel",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-EventsFromEmailConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-eventsfromemailconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ExchangeAssistanceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exchangeassistanceconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ExchangeFeature.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exchangefeature",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ExchangeServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exchangeserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ExchangeSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exchangesettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ExoPhishSimOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exophishsimoverriderule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ExoSecOpsOverrideRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-exosecopsoverriderule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ExternalInOutlook.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-externalinoutlook",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FeatureConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-featureconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-federatedorganizationidentifier",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-federationtrust",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FilePlanPropertyAuthority.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-fileplanpropertyauthority",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FilePlanPropertyCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-fileplanpropertycategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FilePlanPropertyCitation.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-fileplanpropertycitation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FilePlanPropertyDepartment.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-fileplanpropertydepartment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FilePlanPropertyReferenceId.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-fileplanpropertyreferenceid",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FilePlanPropertySubCategory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-fileplanpropertysubcategory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FocusedInbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-focusedinbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ForeignConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-foreignconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-FrontendTransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-frontendtransportservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-globaladdresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-Group.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-group",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-HoldCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-holdcompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-HoldComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-holdcompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-HostedConnectionFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedconnectionfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-HostedContentFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedcontentfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-HostedContentFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedcontentfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedoutboundspamfilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hostedoutboundspamfilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-hybridconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-IPAllowListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-IPAllowListProvidersConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipallowlistprovidersconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-IPBlockListConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-IPBlockListProvidersConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ipblocklistprovidersconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-IRMConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-irmconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ImapSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-imapsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-InboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-inboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-InboxRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-inboxrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-InformationBarrierPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-informationbarrierpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-IntraOrganizationConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-intraorganizationconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-JournalRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-journalrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-Label.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-label",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-LabelPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-labelpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-LinkedUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-linkeduser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-m365dataatrestencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-M365DataAtRestEncryptionPolicyAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-m365dataatrestencryptionpolicyassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailContact.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailcontact",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailPublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailpublicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-Mailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxAuditBypassAssociation.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxauditbypassassociation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxAutoReplyConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxautoreplyconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxCalendarConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxcalendarconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxCalendarFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxcalendarfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxdatabasecopy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxexportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxFolderPermission.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxfolderpermission",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxIRMAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxirmaccess",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboximportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxJunkEmailConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxjunkemailconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxMessageConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxmessageconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxplan",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxRegionalConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxregionalconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxrestorerequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxSentItemsConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxsentitemsconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxSpellingConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxspellingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MailboxTransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mailboxtransportservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilterpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MalwareFilterRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilterrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MalwareFilteringServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-malwarefilteringserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ManagedContentSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managedcontentsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ManagedFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managedfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ManagedFolderMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managedfoldermailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ManagementRoleAssignment.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managementroleassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ManagementRoleEntry.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managementroleentry",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ManagementScope.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-managementscope",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MapiVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mapivirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MessageClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-messageclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-migrationbatch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MigrationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-migrationconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MigrationEndpoint.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-migrationendpoint",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-migrationuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MobileDeviceMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-mobiledevicemailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-moverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-MyAnalyticsFeatureConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-myanalyticsfeatureconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-Notification.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-notification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OMEConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-omeconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OMEMessageRevocation.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-omemessagerevocation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OabVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-oabvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-offlineaddressbook",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OnPremisesOrganization.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-onpremisesorganization",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OrganizationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-organizationconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-organizationrelationship",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OrganizationSegment.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-organizationsegment",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-outboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OutlookAnywhere.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-outlookanywhere",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OutlookProtectionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-outlookprotectionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OutlookProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-outlookprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-owamailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-OwaVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-owavirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PartnerApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-partnerapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PendingFederatedDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-pendingfederateddomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PerimeterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-perimeterconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PhishSimOverridePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-phishsimoverridepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-Place.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-place",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PolicyConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-policyconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PolicyTipConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-policytipconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PopSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-popsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PowerShellVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-powershellvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ProtectionAlert.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-protectionalert",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-publicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PublicFolderDatabase.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-publicfolderdatabase",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-publicfoldermigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-publicfoldermoverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-QuarantinePermissions.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-quarantinepermissions",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-QuarantinePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-quarantinepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RMSTemplate.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-rmstemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ReceiveConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-receiveconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RecipientFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-recipientfilterconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RecordReviewNotificationTemplateConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-recordreviewnotificationtemplateconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RegulatoryComplianceUI.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-regulatorycomplianceui",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RemoteDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-remotedomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RemoteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-remotemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ReportSubmissionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-reportsubmissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ReportSubmissionRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-reportsubmissionrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ResourceConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-resourceconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ResubmitRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-resubmitrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentioncompliancerule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RetentionPolicyTag.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-retentionpolicytag",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RoleAssignmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-roleassignmentpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RoleGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-rolegroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RoutingGroupConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-routinggroupconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-RpcClientAccess.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-rpcclientaccess",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-safeattachmentpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SafeAttachmentRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-safeattachmentrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SafeLinksPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-safelinkspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SafeLinksRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-safelinksrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SearchDocumentFormat.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-searchdocumentformat",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SecOpsOverridePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-secopsoverridepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SendConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sendconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SenderFilterConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-senderfilterconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SenderIdConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-senderidconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SenderReputationConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-senderreputationconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ServerComponentState.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-servercomponentstate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ServerMonitor.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-servermonitor",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ServicePrincipal.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-serviceprincipal",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SettingOverride.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-settingoverride",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SharingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sharingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sitemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SiteMailboxProvisioningPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sitemailboxprovisioningpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SmimeConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-smimeconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SupervisoryReviewPolicyV2.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-supervisoryreviewpolicyv2",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SupervisoryReviewRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-supervisoryreviewrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SweepRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-sweeprule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-SystemMessage.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-systemmessage",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TeamsProtectionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-teamsprotectionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TeamsProtectionPolicyRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-teamsprotectionpolicyrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TenantAllowBlockListItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-tenantallowblocklistitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TenantAllowBlockListSpoofItems.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-tenantallowblocklistspoofitems",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TextMessagingAccount.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-textmessagingaccount",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ThrottlingPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-throttlingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-ThrottlingPolicyAssociation.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-throttlingpolicyassociation",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TransportConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TransportRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TransportServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-TransportService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-transportservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMAutoAttendant.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMCallAnsweringRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umcallansweringrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMCallRouterSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umcallroutersettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMDialPlan.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMIPGateway.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umipgateway",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ummailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMMailboxPIN.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ummailboxpin",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMMailboxPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-ummailboxpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UMService.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UmServer.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-umserver",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UnifiedAuditLogRetentionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-unifiedauditlogretentionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-unifiedgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-User.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-user",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UserBriefingConfig.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-userbriefingconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-UserPhoto.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-userphoto",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-VivaInsightsSettings.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-vivainsightssettings",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-WebServicesVirtualDirectory.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-webservicesvirtualdirectory",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Set-X400AuthoritativeDomain.md",
- "redirect_url": "/powershell/module/exchangepowershell/set-x400authoritativedomain",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-compliancesearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-databaseavailabilitygroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-EdgeSynchronization.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-edgesynchronization",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-HistoricalSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-historicalsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-InformationBarrierPoliciesApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-informationbarrierpoliciesapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-MailboxAssistant.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-mailboxassistant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-mailboxsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-ManagedFolderAssistant.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-managedfolderassistant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-migrationbatch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-migrationuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Start-RetentionAutoTagLearning.md",
- "redirect_url": "/powershell/module/exchangepowershell/start-retentionautotaglearning",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Stop-ComplianceSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-compliancesearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Stop-DatabaseAvailabilityGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-databaseavailabilitygroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Stop-HistoricalSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-historicalsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Stop-InformationBarrierPoliciesApplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-informationbarrierpoliciesapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Stop-MailboxSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-mailboxsearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Stop-ManagedFolderAssistant.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-managedfolderassistant",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Stop-MigrationBatch.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-migrationbatch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Stop-MigrationUser.md",
- "redirect_url": "/powershell/module/exchangepowershell/stop-migrationuser",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxdatabasecopy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-MailboxExportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxexportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-MailboxImportRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboximportrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-MailboxRestoreRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-mailboxrestorerequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-message",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-MoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-moverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-PublicFolderMailboxMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermailboxmigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-PublicFolderMigrationRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermigrationrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-PublicFolderMoveRequest.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfoldermoverequest",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-PublicFolderReplication.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-publicfolderreplication",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Suspend-Queue.md",
- "redirect_url": "/powershell/module/exchangepowershell/suspend-queue",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ActiveSyncConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-activesyncconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-applicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ArchiveConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-archiveconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-AssistantHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-assistanthealth",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-CalendarConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-calendarconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ClientAccessRule.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-clientaccessrule",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-DataClassification.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-dataclassification",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-EcpConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-ecpconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-EdgeSynchronization.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-edgesynchronization",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ExchangeSearch.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-exchangesearch",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-FederationTrust.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-federationtrust",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-FederationTrustCertificate.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-federationtrustcertificate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-IPAllowListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-ipallowlistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-IPBlockListProvider.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-ipblocklistprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-IRMConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-irmconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ImapConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-imapconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-M365DataAtRestEncryptionPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-m365dataatrestencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-MAPIConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-mapiconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-MRSHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-mrshealth",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-Mailflow.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-mailflow",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-Message.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-message",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-MigrationServerAvailability.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-migrationserveravailability",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-OAuthConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-oauthconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-OrganizationRelationship.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-organizationrelationship",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-OutlookConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-outlookconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-OutlookWebServices.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-outlookwebservices",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-OwaConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-owaconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-PopConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-popconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-PowerShellConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-powershellconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ReplicationHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-replicationhealth",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-SenderId.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-senderid",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ServiceHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-servicehealth",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-ServicePrincipalAuthorization.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-serviceprincipalauthorization",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-sitemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-SmtpConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-smtpconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-SystemHealth.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-systemhealth",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-TextExtraction.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-textextraction",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-UMConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-umconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Test-WebServicesConnectivity.md",
- "redirect_url": "/powershell/module/exchangepowershell/test-webservicesconnectivity",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Undo-SoftDeletedMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/undo-softdeletedmailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Undo-SoftDeletedUnifiedGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/undo-softdeletedunifiedgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Uninstall-TransportAgent.md",
- "redirect_url": "/powershell/module/exchangepowershell/uninstall-transportagent",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-AddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-addresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-ComplianceCaseMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-compliancecasemember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-DatabaseSchema.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-databaseschema",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-DistributionGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-distributiongroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-EmailAddressPolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-emailaddresspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-ExchangeHelp.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-exchangehelp",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-FileDistributionService.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-filedistributionservice",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-GlobalAddressList.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-globaladdresslist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-HybridConfiguration.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-hybridconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-MailboxDatabaseCopy.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-mailboxdatabasecopy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-OfflineAddressBook.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-offlineaddressbook",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-PublicFolder.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-publicfolder",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-PublicFolderHierarchy.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-publicfolderhierarchy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-PublicFolderMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-publicfoldermailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-Recipient.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-recipient",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-RoleGroupMember.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-rolegroupmember",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-SafeList.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-safelist",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-SiteMailbox.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-sitemailbox",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-StoreMailboxState.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-storemailboxstate",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-vivamodulefeaturepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Update-eDiscoveryCaseAdmin.md",
- "redirect_url": "/powershell/module/exchangepowershell/update-ediscoverycaseadmin",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Upgrade-DistributionGroup.md",
- "redirect_url": "/powershell/module/exchangepowershell/upgrade-distributiongroup",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Validate-OutboundConnector.md",
- "redirect_url": "/powershell/module/exchangepowershell/validate-outboundconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Validate-RetentionRuleQuery.md",
- "redirect_url": "/powershell/module/exchangepowershell/validate-retentionrulequery",
- "redirect_document_id": false
- },
- {
- "source_path": "exchange/exchange-ps/exchange/Write-AdminAuditLog.md",
- "redirect_url": "/powershell/module/exchangepowershell/write-adminauditlog",
- "redirect_document_id": false
}
]
-}
+}
\ No newline at end of file
diff --git a/.openpublishing.redirection.skype.json b/.openpublishing.redirection.skype.json
index b36ea96b4e..c034ac18a3 100644
--- a/.openpublishing.redirection.skype.json
+++ b/.openpublishing.redirection.skype.json
@@ -2,1817 +2,1817 @@
"redirections": [
{
"source_path": "skype/virtual-folder/skype/Disable-CsOnlineSipDomain.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Disable-CsOnlineSipDomain",
+ "redirect_url": "/powershell/module/teams/Disable-CsOnlineSipDomain",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Enable-CsOnlineSipDomain.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Enable-CsOnlineSipDomain",
+ "redirect_url": "/powershell/module/teams/Enable-CsOnlineSipDomain",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Export-CsAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Export-CsAutoAttendantHolidays",
+ "redirect_url": "/powershell/module/teams/Export-CsAutoAttendantHolidays",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/export-csonlineaudiofile.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/export-csonlineaudiofile",
+ "redirect_url": "/powershell/module/teams/export-csonlineaudiofile",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Find-CsGroup.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Find-CsGroup",
+ "redirect_url": "/powershell/module/teams/Find-CsGroup",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Find-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Find-CsOnlineApplicationInstance",
+ "redirect_url": "/powershell/module/teams/Find-CsOnlineApplicationInstance",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsApplicationAccessPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsApplicationAccessPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsApplicationMeetingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsApplicationMeetingConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsApplicationMeetingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsAutoAttendant",
+ "redirect_url": "/powershell/module/teams/Get-CsAutoAttendant",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsAutoAttendantHolidays",
+ "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantHolidays",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantStatus.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsAutoAttendantStatus",
+ "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantStatus",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantSupportedLanguage.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsAutoAttendantSupportedLanguage",
+ "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantSupportedLanguage",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantSupportedTimeZone.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsAutoAttendantSupportedTimeZone",
+ "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantSupportedTimeZone",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsAutoAttendantTenantInformation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsAutoAttendantTenantInformation",
+ "redirect_url": "/powershell/module/teams/Get-CsAutoAttendantTenantInformation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsCallingLineIdentity",
+ "redirect_url": "/powershell/module/teams/Get-CsCallingLineIdentity",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsCallQueue.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsCallQueue",
+ "redirect_url": "/powershell/module/teams/Get-CsCallQueue",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsEffectiveTenantDialPlan.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsEffectiveTenantDialPlan",
+ "redirect_url": "/powershell/module/teams/Get-CsEffectiveTenantDialPlan",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsInboundBlockedNumberPattern",
+ "redirect_url": "/powershell/module/teams/Get-CsInboundBlockedNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsInboundExemptNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsInboundExemptNumberPattern",
+ "redirect_url": "/powershell/module/teams/Get-CsInboundExemptNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsMeetingMigrationStatus.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsMeetingMigrationStatus",
+ "redirect_url": "/powershell/module/teams/Get-CsMeetingMigrationStatus",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineApplicationInstance",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineApplicationInstance",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineApplicationInstanceAssociation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineApplicationInstanceAssociation",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineApplicationInstanceAssociation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineApplicationInstanceAssociationStatus.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineApplicationInstanceAssociationStatus",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineApplicationInstanceAssociationStatus",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineAudioFile.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineAudioFile",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineAudioFile",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingBridge.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDialInConferencingBridge",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingBridge",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingLanguagesSupported.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDialInConferencingLanguagesSupported",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingLanguagesSupported",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialinConferencingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDialinConferencingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDialinConferencingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingServiceNumber.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDialInConferencingServiceNumber",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingServiceNumber",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialinConferencingTenantConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDialinConferencingTenantConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDialinConferencingTenantConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingTenantSettings.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDialInConferencingTenantSettings",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingTenantSettings",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingUser.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDialInConferencingUser",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDialInConferencingUser",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialOutPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDialOutPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDialOutPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDirectoryTenant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineDirectoryTenant",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineDirectoryTenant",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineEnhancedEmergencyServiceDisclaimer",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineEnhancedEmergencyServiceDisclaimer",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineLisCivicAddress",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineLisCivicAddress",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineLisLocation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineLisLocation",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineLisLocation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineLisPort.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineLisPort",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineLisPort",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineLisSubnet.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineLisSubnet",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineLisSubnet",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineLisSwitch.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineLisSwitch",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineLisSwitch",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineLisWirelessAccessPoint.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineLisWirelessAccessPoint",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineLisWirelessAccessPoint",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlinePSTNGateway.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlinePSTNGateway",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlinePSTNGateway",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlinePstnUsage.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlinePstnUsage",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlinePstnUsage",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineSchedule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineSchedule",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineSchedule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineSipDomain.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineSipDomain",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineSipDomain",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumber.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineTelephoneNumber",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineTelephoneNumber",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineUser.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineUser",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineUser",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineVoicemailPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineVoicemailPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineVoicemailUserSettings.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineVoicemailUserSettings",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineVoicemailUserSettings",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineVoiceRoute.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineVoiceRoute",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineVoiceRoute",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineVoiceRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineVoiceRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineVoiceUser.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsOnlineVoiceUser",
+ "redirect_url": "/powershell/module/teams/Get-CsOnlineVoiceUser",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsAppPermissionPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsAppPermissionPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsAppSetupPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsAppSetupPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsAudioConferencingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsAudioConferencingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsCallHoldPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsCallHoldPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsCallingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsCallParkPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsCallParkPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsChannelsPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsChannelsPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsClientConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsClientConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsClientConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsComplianceRecordingApplication.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsComplianceRecordingApplication",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsComplianceRecordingApplication",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsComplianceRecordingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsComplianceRecordingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsCortanaPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsCortanaPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsEducationAssignmentsAppPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsEducationAssignmentsAppPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsEducationAssignmentsAppPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsEmergencyCallingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsEmergencyCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsEmergencyCallRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsEmergencyCallRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsFeedbackPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsFeedbackPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsGuestCallingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsGuestCallingConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsGuestCallingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsGuestMeetingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsGuestMeetingConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsGuestMeetingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsGuestMessagingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsGuestMessagingConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsGuestMessagingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsIPPhonePolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsIPPhonePolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsMeetingBrandingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingBrandingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingBroadcastConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsMeetingBroadcastConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingBroadcastConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsMeetingBroadcastPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingBroadcastPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsMeetingConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsMeetingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsMeetingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsMessagingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsMessagingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsMobilityPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsMobilityPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsNetworkRoamingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsNetworkRoamingPolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsNetworkRoamingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsTranslationRule",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsTranslationRule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsVideoInteropServicePolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTeamsVideoInteropServicePolicy",
+ "redirect_url": "/powershell/module/teams/Get-CsTeamsVideoInteropServicePolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenant",
+ "redirect_url": "/powershell/module/teams/Get-CsTenant",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantBlockedCallingNumbers.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantBlockedCallingNumbers",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantBlockedCallingNumbers",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantDialPlan",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantDialPlan",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantFederationConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantFederationConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantFederationConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantLicensingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantLicensingConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantLicensingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantMigrationConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantMigrationConfiguration",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantMigrationConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantNetworkRegion.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantNetworkRegion",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantNetworkRegion",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantNetworkSite.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantNetworkSite",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantNetworkSite",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantNetworkSubnet.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantNetworkSubnet",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantNetworkSubnet",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantTrustedIPAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsTenantTrustedIPAddress",
+ "redirect_url": "/powershell/module/teams/Get-CsTenantTrustedIPAddress",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsVideoInteropServiceProvider.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Get-CsVideoInteropServiceProvider",
+ "redirect_url": "/powershell/module/teams/Get-CsVideoInteropServiceProvider",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsApplicationAccessPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsApplicationAccessPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsCallingLineIdentity",
+ "redirect_url": "/powershell/module/teams/Grant-CsCallingLineIdentity",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsCloudMeetingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsCloudMeetingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsCloudMeetingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsDialoutPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsDialoutPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsDialoutPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsExternalUserCommunicationPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsExternalUserCommunicationPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsExternalUserCommunicationPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsOnlineVoicemailPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsOnlineVoicemailPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsOnlineVoiceRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsOnlineVoiceRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsAppPermissionPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsAppPermissionPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsAppSetupPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsAppSetupPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsAudioConferencingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsAudioConferencingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsCallHoldPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsCallHoldPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsCallingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsCallParkPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsCallParkPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsChannelsPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsChannelsPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsComplianceRecordingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsComplianceRecordingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsCortanaPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsCortanaPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsEmergencyCallingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsEmergencyCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsEmergencyCallRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsEmergencyCallRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsFeedbackPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsFeedbackPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsIPPhonePolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsIPPhonePolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsMeetingBrandingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsMeetingBrandingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsMeetingBroadcastPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsMeetingBroadcastPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsMeetingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsMeetingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsMessagingPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsMessagingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsMobilityPolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsMobilityPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTeamsVideoInteropServicePolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTeamsVideoInteropServicePolicy",
+ "redirect_url": "/powershell/module/teams/Grant-CsTeamsVideoInteropServicePolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Grant-CsTenantDialPlan",
+ "redirect_url": "/powershell/module/teams/Grant-CsTenantDialPlan",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Import-CsAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Import-CsAutoAttendantHolidays",
+ "redirect_url": "/powershell/module/teams/Import-CsAutoAttendantHolidays",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Import-CsOnlineAudioFile.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Import-CsOnlineAudioFile",
+ "redirect_url": "/powershell/module/teams/Import-CsOnlineAudioFile",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsApplicationAccessPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsApplicationAccessPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsAutoAttendant",
+ "redirect_url": "/powershell/module/teams/New-CsAutoAttendant",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsAutoAttendantCallableEntity.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsAutoAttendantCallableEntity",
+ "redirect_url": "/powershell/module/teams/New-CsAutoAttendantCallableEntity",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsAutoAttendantCallFlow.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsAutoAttendantCallFlow",
+ "redirect_url": "/powershell/module/teams/New-CsAutoAttendantCallFlow",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsAutoAttendantCallHandlingAssociation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsAutoAttendantCallHandlingAssociation",
+ "redirect_url": "/powershell/module/teams/New-CsAutoAttendantCallHandlingAssociation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsAutoAttendantDialScope.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsAutoAttendantDialScope",
+ "redirect_url": "/powershell/module/teams/New-CsAutoAttendantDialScope",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsAutoAttendantMenu.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsAutoAttendantMenu",
+ "redirect_url": "/powershell/module/teams/New-CsAutoAttendantMenu",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsAutoAttendantMenuOption.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsAutoAttendantMenuOption",
+ "redirect_url": "/powershell/module/teams/New-CsAutoAttendantMenuOption",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsAutoAttendantPrompt.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsAutoAttendantPrompt",
+ "redirect_url": "/powershell/module/teams/New-CsAutoAttendantPrompt",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsCallingLineIdentity",
+ "redirect_url": "/powershell/module/teams/New-CsCallingLineIdentity",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsCallQueue.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsCallQueue",
+ "redirect_url": "/powershell/module/teams/New-CsCallQueue",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsEdgeAllowAllKnownDomains.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsEdgeAllowAllKnownDomains",
+ "redirect_url": "/powershell/module/teams/New-CsEdgeAllowAllKnownDomains",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsEdgeAllowList.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsEdgeAllowList",
+ "redirect_url": "/powershell/module/teams/New-CsEdgeAllowList",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsEdgeDomainPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsEdgeDomainPattern",
+ "redirect_url": "/powershell/module/teams/New-CsEdgeDomainPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsInboundBlockedNumberPattern",
+ "redirect_url": "/powershell/module/teams/New-CsInboundBlockedNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsInboundExemptNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsInboundExemptNumberPattern",
+ "redirect_url": "/powershell/module/teams/New-CsInboundExemptNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineApplicationInstance",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineApplicationInstance",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineApplicationInstanceAssociation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineApplicationInstanceAssociation",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineApplicationInstanceAssociation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineDateTimeRange.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineDateTimeRange",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineDateTimeRange",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineLisCivicAddress",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineLisCivicAddress",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineLisLocation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineLisLocation",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineLisLocation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlinePSTNGateway.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlinePSTNGateway",
+ "redirect_url": "/powershell/module/teams/New-CsOnlinePSTNGateway",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineSchedule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineSchedule",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineSchedule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineTimeRange.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineTimeRange",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineTimeRange",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineVoicemailPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineVoicemailPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineVoiceRoute.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineVoiceRoute",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineVoiceRoute",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsOnlineVoiceRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsOnlineVoiceRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsAppPermissionPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsAppPermissionPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsAppSetupPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsAppSetupPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsAudioConferencingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsAudioConferencingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsCallHoldPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsCallHoldPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsCallingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsCallParkPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsCallParkPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsChannelsPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsChannelsPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsComplianceRecordingApplication.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsComplianceRecordingApplication",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsComplianceRecordingApplication",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsComplianceRecordingPairedApplication.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsComplianceRecordingPairedApplication",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsComplianceRecordingPairedApplication",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsComplianceRecordingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsComplianceRecordingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsCortanaPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsCortanaPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsEmergencyCallingExtendedNotification.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsEmergencyCallingExtendedNotification",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsEmergencyCallingExtendedNotification",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsEmergencyCallingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsEmergencyCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsEmergencyCallRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsEmergencyCallRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsEmergencyNumber.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsEmergencyNumber",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsEmergencyNumber",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsFeedbackPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsFeedbackPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsIPPhonePolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsIPPhonePolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsMeetingBrandingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsMeetingBrandingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsMeetingBroadcastPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsMeetingBroadcastPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsMeetingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsMeetingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsMessagingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsMessagingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsMobilityPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsMobilityPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsNetworkRoamingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsNetworkRoamingPolicy",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsNetworkRoamingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsPinnedApp.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsPinnedApp",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsPinnedApp",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTeamsTranslationRule",
+ "redirect_url": "/powershell/module/teams/New-CsTeamsTranslationRule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTenantDialPlan",
+ "redirect_url": "/powershell/module/teams/New-CsTenantDialPlan",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTenantNetworkRegion.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTenantNetworkRegion",
+ "redirect_url": "/powershell/module/teams/New-CsTenantNetworkRegion",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTenantNetworkSite.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTenantNetworkSite",
+ "redirect_url": "/powershell/module/teams/New-CsTenantNetworkSite",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTenantNetworkSubnet.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTenantNetworkSubnet",
+ "redirect_url": "/powershell/module/teams/New-CsTenantNetworkSubnet",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsTenantTrustedIPAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsTenantTrustedIPAddress",
+ "redirect_url": "/powershell/module/teams/New-CsTenantTrustedIPAddress",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsVideoInteropServiceProvider.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/New-CsVideoInteropServiceProvider",
+ "redirect_url": "/powershell/module/teams/New-CsVideoInteropServiceProvider",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Register-CsOnlineDialInConferencingServiceNumber.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Register-CsOnlineDialInConferencingServiceNumber",
+ "redirect_url": "/powershell/module/teams/Register-CsOnlineDialInConferencingServiceNumber",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsApplicationAccessPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsApplicationAccessPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsAutoAttendant",
+ "redirect_url": "/powershell/module/teams/Remove-CsAutoAttendant",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsCallingLineIdentity",
+ "redirect_url": "/powershell/module/teams/Remove-CsCallingLineIdentity",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsCallQueue.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsCallQueue",
+ "redirect_url": "/powershell/module/teams/Remove-CsCallQueue",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsInboundBlockedNumberPattern",
+ "redirect_url": "/powershell/module/teams/Remove-CsInboundBlockedNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsInboundExemptNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsInboundExemptNumberPattern",
+ "redirect_url": "/powershell/module/teams/Remove-CsInboundExemptNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineApplicationInstanceAssociation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineApplicationInstanceAssociation",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineApplicationInstanceAssociation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineAudioFile.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineAudioFile",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineAudioFile",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineDialInConferencingTenantSettings.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineDialInConferencingTenantSettings",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineDialInConferencingTenantSettings",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineLisCivicAddress",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisCivicAddress",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisLocation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineLisLocation",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisLocation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisPort.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineLisPort",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisPort",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisSubnet.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineLisSubnet",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisSubnet",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisSwitch.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineLisSwitch",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisSwitch",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineLisWirelessAccessPoint.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineLisWirelessAccessPoint",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineLisWirelessAccessPoint",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlinePSTNGateway.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlinePSTNGateway",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlinePSTNGateway",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineSchedule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineSchedule",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineSchedule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineTelephoneNumber.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineTelephoneNumber",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineTelephoneNumber",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineVoicemailPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineVoicemailPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineVoiceRoute.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineVoiceRoute",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineVoiceRoute",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsOnlineVoiceRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsOnlineVoiceRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsAppPermissionPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsAppPermissionPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsAppSetupPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsAppSetupPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsAudioConferencingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsAudioConferencingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsCallHoldPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsCallHoldPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsCallingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsCallParkPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsCallParkPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsChannelsPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsChannelsPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsComplianceRecordingApplication.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsComplianceRecordingApplication",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsComplianceRecordingApplication",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsComplianceRecordingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsComplianceRecordingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsCortanaPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsCortanaPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsEmergencyCallingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsEmergencyCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsEmergencyCallRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsEmergencyCallRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsFeedbackPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsFeedbackPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsIPPhonePolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsIPPhonePolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsMeetingBrandingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsMeetingBrandingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsMeetingBroadcastPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsMeetingBroadcastPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsMeetingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsMeetingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsMessagingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsMessagingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsMobilityPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsMobilityPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsNetworkRoamingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsNetworkRoamingPolicy",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsNetworkRoamingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsPinnedApp.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsPinnedApp",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsPinnedApp",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTeamsTranslationRule",
+ "redirect_url": "/powershell/module/teams/Remove-CsTeamsTranslationRule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTenantDialPlan",
+ "redirect_url": "/powershell/module/teams/Remove-CsTenantDialPlan",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTenantNetworkRegion.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTenantNetworkRegion",
+ "redirect_url": "/powershell/module/teams/Remove-CsTenantNetworkRegion",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTenantNetworkSite.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTenantNetworkSite",
+ "redirect_url": "/powershell/module/teams/Remove-CsTenantNetworkSite",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTenantNetworkSubnet.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTenantNetworkSubnet",
+ "redirect_url": "/powershell/module/teams/Remove-CsTenantNetworkSubnet",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsTenantTrustedIPAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsTenantTrustedIPAddress",
+ "redirect_url": "/powershell/module/teams/Remove-CsTenantTrustedIPAddress",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsVideoInteropServiceProvider.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Remove-CsVideoInteropServiceProvider",
+ "redirect_url": "/powershell/module/teams/Remove-CsVideoInteropServiceProvider",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsApplicationAccessPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsApplicationAccessPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsApplicationMeetingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsApplicationMeetingConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsApplicationMeetingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsAutoAttendant",
+ "redirect_url": "/powershell/module/teams/Set-CsAutoAttendant",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsCallingLineIdentity",
+ "redirect_url": "/powershell/module/teams/Set-CsCallingLineIdentity",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsCallQueue.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsCallQueue",
+ "redirect_url": "/powershell/module/teams/Set-CsCallQueue",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsInboundBlockedNumberPattern",
+ "redirect_url": "/powershell/module/teams/Set-CsInboundBlockedNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsInboundExemptNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsInboundExemptNumberPattern",
+ "redirect_url": "/powershell/module/teams/Set-CsInboundExemptNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineApplicationInstance",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineApplicationInstance",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingBridge.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineDialInConferencingBridge",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingBridge",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingServiceNumber.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineDialInConferencingServiceNumber",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingServiceNumber",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingTenantSettings.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineDialInConferencingTenantSettings",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingTenantSettings",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingUser.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineDialInConferencingUser",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingUser",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineDialInConferencingUserDefaultNumber.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineDialInConferencingUserDefaultNumber",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineDialInConferencingUserDefaultNumber",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineEnhancedEmergencyServiceDisclaimer",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineEnhancedEmergencyServiceDisclaimer",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineLisCivicAddress",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineLisCivicAddress",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineLisLocation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineLisLocation",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineLisLocation",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineLisPort.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineLisPort",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineLisPort",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineLisSubnet.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineLisSubnet",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineLisSubnet",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineLisSwitch.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineLisSwitch",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineLisSwitch",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineLisWirelessAccessPoint.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineLisWirelessAccessPoint",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineLisWirelessAccessPoint",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlinePSTNGateway.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlinePSTNGateway",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlinePSTNGateway",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlinePstnUsage.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlinePstnUsage",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlinePstnUsage",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineSchedule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineSchedule",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineSchedule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceApplicationInstance.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineVoiceApplicationInstance",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineVoiceApplicationInstance",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineVoicemailPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineVoicemailPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineVoicemailUserSettings.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineVoicemailUserSettings",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineVoicemailUserSettings",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceRoute.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineVoiceRoute",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineVoiceRoute",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineVoiceRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineVoiceRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceUser.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsOnlineVoiceUser",
+ "redirect_url": "/powershell/module/teams/Set-CsOnlineVoiceUser",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsAppPermissionPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsAppPermissionPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsAppSetupPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsAppSetupPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsAudioConferencingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsAudioConferencingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsCallHoldPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsCallHoldPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsCallingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsCallParkPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsCallParkPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsChannelsPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsChannelsPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsClientConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsClientConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsClientConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsComplianceRecordingApplication.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsComplianceRecordingApplication",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsComplianceRecordingApplication",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsComplianceRecordingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsComplianceRecordingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsCortanaPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsCortanaPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsEducationAssignmentsAppPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsEducationAssignmentsAppPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsEducationAssignmentsAppPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsEmergencyCallingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsEmergencyCallingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsEmergencyCallRoutingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsEmergencyCallRoutingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsFeedbackPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsFeedbackPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsGuestCallingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsGuestCallingConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsGuestCallingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsGuestMeetingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsGuestMeetingConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsGuestMeetingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsGuestMessagingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsGuestMessagingConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsGuestMessagingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsIPPhonePolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsIPPhonePolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsMeetingBrandingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingBrandingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingBroadcastConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsMeetingBroadcastConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingBroadcastConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsMeetingBroadcastPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingBroadcastPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsMeetingConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsMeetingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsMeetingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsMessagingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsMessagingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsMobilityPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsMobilityPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsNetworkRoamingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsNetworkRoamingPolicy",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsNetworkRoamingPolicy",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsPinnedApp.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsPinnedApp",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsPinnedApp",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTeamsTranslationRule",
+ "redirect_url": "/powershell/module/teams/Set-CsTeamsTranslationRule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantBlockedCallingNumbers.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTenantBlockedCallingNumbers",
+ "redirect_url": "/powershell/module/teams/Set-CsTenantBlockedCallingNumbers",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTenantDialPlan",
+ "redirect_url": "/powershell/module/teams/Set-CsTenantDialPlan",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantFederationConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTenantFederationConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsTenantFederationConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantMigrationConfiguration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTenantMigrationConfiguration",
+ "redirect_url": "/powershell/module/teams/Set-CsTenantMigrationConfiguration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantNetworkRegion.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTenantNetworkRegion",
+ "redirect_url": "/powershell/module/teams/Set-CsTenantNetworkRegion",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantNetworkSite.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTenantNetworkSite",
+ "redirect_url": "/powershell/module/teams/Set-CsTenantNetworkSite",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantNetworkSubnet.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTenantNetworkSubnet",
+ "redirect_url": "/powershell/module/teams/Set-CsTenantNetworkSubnet",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantTrustedIPAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsTenantTrustedIPAddress",
+ "redirect_url": "/powershell/module/teams/Set-CsTenantTrustedIPAddress",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsVideoInteropServiceProvider.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Set-CsVideoInteropServiceProvider",
+ "redirect_url": "/powershell/module/teams/Set-CsVideoInteropServiceProvider",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Start-CsExMeetingMigration.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Start-CsExMeetingMigration",
+ "redirect_url": "/powershell/module/teams/Start-CsExMeetingMigration",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Sync-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Sync-CsOnlineApplicationInstance",
+ "redirect_url": "/powershell/module/teams/Sync-CsOnlineApplicationInstance",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Test-CsEffectiveTenantDialPlan.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Test-CsEffectiveTenantDialPlan",
+ "redirect_url": "/powershell/module/teams/Test-CsEffectiveTenantDialPlan",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Test-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Test-CsInboundBlockedNumberPattern",
+ "redirect_url": "/powershell/module/teams/Test-CsInboundBlockedNumberPattern",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Test-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Test-CsTeamsTranslationRule",
+ "redirect_url": "/powershell/module/teams/Test-CsTeamsTranslationRule",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Unregister-CsOnlineDialInConferencingServiceNumber.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Unregister-CsOnlineDialInConferencingServiceNumber",
+ "redirect_url": "/powershell/module/teams/Unregister-CsOnlineDialInConferencingServiceNumber",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Update-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/Update-CsAutoAttendant",
+ "redirect_url": "/powershell/module/teams/Update-CsAutoAttendant",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Clear-CsOnlineTelephoneNumberReservation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Disable-CsOnlineDialInConferencingUser.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Enable-CsOnlineDialInConferencingUser.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Export-CsOrganizationalAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsHuntGroup.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsHuntGroupTenantInformation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineApplicationEndpoint.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingUserInfo.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDialInConferencingUserState.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineDirectoryTenantNumberCities.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineNumberPortInOrder.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineNumberPortOutOrderPin.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberAvailableCount.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryAreas.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryCities.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryCountries.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryRegions.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberInventoryTypes.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOnlineTelephoneNumberReservationsInformation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantStatus.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantSupportedLanguage.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantSupportedTimeZone.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsOrganizationalAutoAttendantTenantInformation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTeamsUpgradeStatus.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Get-CsTenantPublicProvider.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Grant-CsBroadcastMeetingPolicy.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Import-CsOrganizationalAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsHuntGroup.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineApplicationEndpoint.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineAudioFile.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineBulkAssignmentInput.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineNumberPortInOrder.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOnlineSession.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantCallableEntity.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantCallFlow.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantCallHandlingAssociation.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantDialScope.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantMenu.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantMenuOption.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/New-CsOrganizationalAutoAttendantPrompt.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsHuntGroup.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineApplicationEndpoint.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOnlineNumberPortInOrder.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Remove-CsOrganizationalAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Search-CsOnlineTelephoneNumberInventory.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Select-CsOnlineTelephoneNumberInventory.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsHuntGroup.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineApplicationEndpoint.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineDirectoryUser.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineNumberPortInOrder.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineNumberPortOutOrderPin.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOnlineVoiceUserBulk.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsOrganizationalAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Set-CsTenantPublicProvider.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Test-CsOnlineCarrierPortabilityIn.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Test-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Test-CsOnlinePortabilityIn.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
"source_path": "skype/virtual-folder/skype/Update-CsOrganizationalAutoAttendant.md",
- "redirect_url": "/powershell/module/MicrosoftTeams/",
+ "redirect_url": "/powershell/module/teams/",
"redirect_document_id": false
},
{
diff --git a/.openpublishing.redirection.teams.json b/.openpublishing.redirection.teams.json
index 7076d5b588..ca0a088c34 100644
--- a/.openpublishing.redirection.teams.json
+++ b/.openpublishing.redirection.teams.json
@@ -2,3007 +2,7 @@
"redirections": [
{
"source_path": "teams/docs-conceptual/intro.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Add-TeamChannelUser.md",
- "redirect_url": "/powershell/module/microsoftteams/add-teamchanneluser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Add-TeamUser.md",
- "redirect_url": "/powershell/module/microsoftteams/add-teamuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Clear-CsOnlineTelephoneNumberOrder.md",
- "redirect_url": "/powershell/module/microsoftteams/clear-csonlinetelephonenumberorder",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Clear-TeamsEnvironmentConfig.md",
- "redirect_url": "/powershell/module/microsoftteams/clear-teamsenvironmentconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Complete-CsOnlineTelephoneNumberOrder.md",
- "redirect_url": "/powershell/module/microsoftteams/complete-csonlinetelephonenumberorder",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Connect-MicrosoftTeams.md",
- "redirect_url": "/powershell/module/microsoftteams/connect-microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Disable-CsOnlineSipDomain.md",
- "redirect_url": "/powershell/module/microsoftteams/disable-csonlinesipdomain",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Disconnect-MicrosoftTeams.md",
- "redirect_url": "/powershell/module/microsoftteams/disconnect-microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Enable-CsOnlineSipDomain.md",
- "redirect_url": "/powershell/module/microsoftteams/enable-csonlinesipdomain",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Export-CsAcquiredPhoneNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/export-csacquiredphonenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Export-CsAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/microsoftteams/export-csautoattendantholidays",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Find-CsGroup.md",
- "redirect_url": "/powershell/module/microsoftteams/find-csgroup",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Find-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/find-csonlineapplicationinstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-ALLM365TeamsApps.md",
- "redirect_url": "/powershell/module/microsoftteams/get-allm365teamsapps",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-AssociatedTeam.md",
- "redirect_url": "/powershell/module/microsoftteams/get-associatedteam",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csapplicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsApplicationMeetingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csapplicationmeetingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csautoattendantholidays",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsAutoAttendantStatus.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csautoattendantstatus",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsAutoAttendantSupportedLanguage.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csautoattendantsupportedlanguage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsAutoAttendantSupportedTimeZone.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csautoattendantsupportedtimezone",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsAutoAttendantTenantInformation.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csautoattendanttenantinformation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csbatchpolicyassignmentoperation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsBatchTeamsDeploymentStatus.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csbatchteamsdeploymentstatus",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsCallQueue.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cscallqueue",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cscallinglineidentity",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsCloudCallDataConnection.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cscloudcalldataconnection",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsComplianceRecordingForCallQueueTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cscompliancerecordingforcallqueuetemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsEffectiveTenantDialPlan.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cseffectivetenantdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsExportAcquiredPhoneNumberStatus.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csexportacquiredphonenumberstatus",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsExternalAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csexternalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsGroupPolicyAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csgrouppolicyassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsHybridTelephoneNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cshybridtelephonenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csinboundblockednumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsInboundExemptNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csinboundexemptnumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsMeetingMigrationStatus.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csmeetingmigrationstatus",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineapplicationinstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineApplicationInstanceAssociation.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineapplicationinstanceassociation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineApplicationInstanceAssociationStatus.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineapplicationinstanceassociationstatus",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineAudioConferencingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineaudioconferencingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineAudioFile.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineaudiofile",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDialInConferencingBridge.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedialinconferencingbridge",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDialInConferencingLanguagesSupported.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedialinconferencinglanguagessupported",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDialInConferencingServiceNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedialinconferencingservicenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDialInConferencingTenantSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedialinconferencingtenantsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDialInConferencingUser.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedialinconferencinguser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDialOutPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedialoutpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDialinConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedialinconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDialinConferencingTenantConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedialinconferencingtenantconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineDirectoryTenant.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinedirectorytenant",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineEnhancedEmergencyServiceDisclaimer.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineenhancedemergencyservicedisclaimer",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineliscivicaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineLisLocation.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinelislocation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineLisPort.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinelisport",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineLisSubnet.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinelissubnet",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineLisSwitch.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinelisswitch",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineLisWirelessAccessPoint.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineliswirelessaccesspoint",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlinePSTNGateway.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinepstngateway",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlinePstnUsage.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinepstnusage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineSchedule.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineschedule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineSipDomain.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinesipdomain",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineTelephoneNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinetelephonenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineTelephoneNumberCountry.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinetelephonenumbercountry",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineTelephoneNumberOrder.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinetelephonenumberorder",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineTelephoneNumberType.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinetelephonenumbertype",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineUser.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlineuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineVoiceRoute.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinevoiceroute",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinevoiceroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineVoiceUser.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinevoiceuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinevoicemailpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsOnlineVoicemailUserSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csonlinevoicemailusersettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsPhoneNumberAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csphonenumberassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsPhoneNumberTag.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csphonenumbertag",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsPolicyPackage.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cspolicypackage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsSdgBulkSignInRequestStatus.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cssdgbulksigninrequeststatus",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsSdgBulkSignInRequestsSummary.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cssdgbulksigninrequestssummary",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsSharedCallQueueHistoryTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cssharedcallqueuehistorytemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamtemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamTemplateList.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamtemplatelist",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsAIPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsaipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsAcsFederationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsacsfederationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsapppermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsappsetuppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsaudioconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamscallholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamscallparkpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamscallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamschannelspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsClientConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsclientconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsComplianceRecordingApplication.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamscompliancerecordingapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamscompliancerecordingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamscortanapolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsCustomBannerText.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamscustombannertext",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsEducationAssignmentsAppPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamseducationassignmentsapppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsEducationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamseducationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsemergencycallroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsemergencycallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsEnhancedEncryptionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsenhancedencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsEventsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamseventspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsExternalAccessConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsexternalaccessconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsfeedbackpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsFilesPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsfilespolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsFirstPartyMeetingTemplateConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsfirstpartymeetingtemplateconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsGuestCallingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsguestcallingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsGuestMeetingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsguestmeetingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsGuestMessagingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsguestmessagingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsipphonepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMediaConnectivityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmediaconnectivitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMediaLoggingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmedialoggingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmeetingbrandingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMeetingBroadcastConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmeetingbroadcastconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmeetingbroadcastpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMeetingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmeetingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmeetingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMeetingTemplateConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmeetingtemplateconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMeetingTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmeetingtemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmessagingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmobilitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsMultiTenantOrganizationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmultitenantorganizationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsNetworkRoamingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsnetworkroamingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsNotificationAndFeedsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsnotificationandfeedspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsRecordingRollOutPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsrecordingrolloutpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsRoomVideoTeleConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsroomvideoteleconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsSettingsCustomApp.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamssettingscustomapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsSharedCallingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamssharedcallingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsAppPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsapppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnection.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnection",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnectionConnector.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnectionconnector",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnectionErrorReport.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnectionerrorreport",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnectionInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnectioninstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnectionOperation.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnectionoperation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnectionSyncResult.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnectionsyncresult",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnectionTeamMap.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnectionteammap",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmTeam.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnectionwfmteam",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsConnectionWfmUser.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftsconnectionwfmuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsShiftsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsshiftspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsSipDevicesConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamssipdevicesconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsSurvivableBranchAppliance.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamssurvivablebranchappliance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsSurvivableBranchAppliancePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamssurvivablebranchappliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsTargetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamstargetingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamstemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamstranslationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsUnassignedNumberTreatment.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsunassignednumbertreatment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsUpdateManagementPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsupdatemanagementpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsUpgradeConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsupgradeconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsUpgradePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsupgradepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsVdiPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsvdipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsVideoInteropServicePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsvideointeropservicepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsVirtualAppointmentsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsvirtualappointmentspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsVoiceApplicationsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsvoiceapplicationspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsWorkLoadPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsworkloadpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTeamsWorkLocationDetectionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsworklocationdetectionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenant.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenant",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantBlockedCallingNumbers.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantblockedcallingnumbers",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantFederationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantfederationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantLicensingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantlicensingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantMigrationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantmigrationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantNetworkConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantnetworkconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantNetworkRegion.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantnetworkregion",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantNetworkSite.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantnetworksite",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantNetworkSubnet.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenantnetworksubnet",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsTenantTrustedIPAddress.md",
- "redirect_url": "/powershell/module/microsoftteams/get-cstenanttrustedipaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsUserCallingSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csusercallingsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsUserPolicyAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csuserpolicyassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsUserPolicyPackage.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csuserpolicypackage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsUserPolicyPackageRecommendation.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csuserpolicypackagerecommendation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsVideoInteropServiceProvider.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csvideointeropserviceprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-M365TeamsApp.md",
- "redirect_url": "/powershell/module/microsoftteams/get-m365teamsapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-M365UnifiedCustomPendingApps.md",
- "redirect_url": "/powershell/module/microsoftteams/get-m365unifiedcustompendingapps",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-M365UnifiedTenantSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/get-m365unifiedtenantsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-SharedWithTeam.md",
- "redirect_url": "/powershell/module/microsoftteams/get-sharedwithteam",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-SharedWithTeamUser.md",
- "redirect_url": "/powershell/module/microsoftteams/get-sharedwithteamuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-Team.md",
- "redirect_url": "/powershell/module/microsoftteams/get-team",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamAllChannel.md",
- "redirect_url": "/powershell/module/microsoftteams/get-teamallchannel",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamChannel.md",
- "redirect_url": "/powershell/module/microsoftteams/get-teamchannel",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamChannelUser.md",
- "redirect_url": "/powershell/module/microsoftteams/get-teamchanneluser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamIncomingChannel.md",
- "redirect_url": "/powershell/module/microsoftteams/get-teamincomingchannel",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamTargetingHierarchyStatus.md",
- "redirect_url": "/powershell/module/microsoftteams/get-teamtargetinghierarchystatus",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamUser.md",
- "redirect_url": "/powershell/module/microsoftteams/get-teamuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamsApp.md",
- "redirect_url": "/powershell/module/microsoftteams/get-teamsapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csapplicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-cscallinglineidentity",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsDialoutPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csdialoutpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsExternalAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csexternalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsGroupPolicyPackageAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csgrouppolicypackageassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsOnlineAudioConferencingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csonlineaudioconferencingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csonlinevoiceroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csonlinevoicemailpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsAIPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsaipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsapppermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsappsetuppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsaudioconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamscallholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamscallparkpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamscallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamschannelspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamscompliancerecordingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamscortanapolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsemergencycallroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsemergencycallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsEnhancedEncryptionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsenhancedencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsEventsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamseventspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsfeedbackpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsFilesPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsfilespolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsipphonepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsMediaConnectivityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsmediaconnectivitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsMediaLoggingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsmedialoggingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsmeetingbrandingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsmeetingbroadcastpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsmeetingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsMeetingTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsmeetingtemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsmessagingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsmobilitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsRecordingRollOutPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsrecordingrolloutpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsRoomVideoTeleConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsroomvideoteleconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsSharedCallingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamssharedcallingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsShiftsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsshiftspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsSurvivableBranchAppliancePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamssurvivablebranchappliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsUpdateManagementPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsupdatemanagementpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsUpgradePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsupgradepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsVdiPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsvdipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsVideoInteropServicePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsvideointeropservicepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsVirtualAppointmentsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsvirtualappointmentspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsVoiceApplicationsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsvoiceapplicationspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsWorkLoadPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsworkloadpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTeamsWorkLocationDetectionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csteamsworklocationdetectionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-cstenantdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsUserPolicyPackage.md",
- "redirect_url": "/powershell/module/microsoftteams/grant-csuserpolicypackage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Import-CsAutoAttendantHolidays.md",
- "redirect_url": "/powershell/module/microsoftteams/import-csautoattendantholidays",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Import-CsOnlineAudioFile.md",
- "redirect_url": "/powershell/module/microsoftteams/import-csonlineaudiofile",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csapplicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsAutoAttendantCallFlow.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csautoattendantcallflow",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsAutoAttendantCallHandlingAssociation.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csautoattendantcallhandlingassociation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsAutoAttendantCallableEntity.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csautoattendantcallableentity",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsAutoAttendantDialScope.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csautoattendantdialscope",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsAutoAttendantMenu.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csautoattendantmenu",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsAutoAttendantMenuOption.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csautoattendantmenuoption",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsAutoAttendantPrompt.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csautoattendantprompt",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csbatchpolicyassignmentoperation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsBatchPolicyPackageAssignmentOperation.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csbatchpolicypackageassignmentoperation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsBatchTeamsDeployment.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csbatchteamsdeployment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsCallQueue.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cscallqueue",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cscallinglineidentity",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsCloudCallDataConnection.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cscloudcalldataconnection",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsComplianceRecordingForCallQueueTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cscompliancerecordingforcallqueuetemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsCustomPolicyPackage.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cscustompolicypackage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsEdgeAllowAllKnownDomains.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csedgeallowallknowndomains",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsEdgeAllowList.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csedgeallowlist",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsEdgeDomainPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csedgedomainpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsExternalAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csexternalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsGroupPolicyAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csgrouppolicyassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsHybridTelephoneNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cshybridtelephonenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csinboundblockednumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsInboundExemptNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csinboundexemptnumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlineapplicationinstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineApplicationInstanceAssociation.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlineapplicationinstanceassociation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineAudioConferencingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlineaudioconferencingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineDateTimeRange.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinedatetimerange",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineDirectRoutingTelephoneNumberUploadOrder.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinedirectroutingtelephonenumberuploadorder",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlineliscivicaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineLisLocation.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinelislocation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlinePSTNGateway.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinepstngateway",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineSchedule.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlineschedule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineTelephoneNumberOrder.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinetelephonenumberorder",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineTelephoneNumberReleaseOrder.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinetelephonenumberreleaseorder",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineTimeRange.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinetimerange",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineVoiceRoute.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinevoiceroute",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinevoiceroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csonlinevoicemailpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsSdgBulkSignInRequest.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cssdgbulksigninrequest",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsSharedCallQueueHistoryTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cssharedcallqueuehistorytemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamtemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsAIPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsaipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsapppermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsappsetuppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsaudioconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamscallholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamscallparkpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamscallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamschannelspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsComplianceRecordingApplication.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamscompliancerecordingapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsComplianceRecordingPairedApplication.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamscompliancerecordingpairedapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamscompliancerecordingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamscortanapolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsCustomBannerText.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamscustombannertext",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsemergencycallroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsEmergencyCallingExtendedNotification.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsemergencycallingextendednotification",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsemergencycallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsEmergencyNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsemergencynumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsEnhancedEncryptionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsenhancedencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsEventsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamseventspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsfeedbackpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsFilesPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsfilespolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsHiddenMeetingTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamshiddenmeetingtemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsHiddenTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamshiddentemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsipphonepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsMediaConnectivityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsmediaconnectivitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsmeetingbrandingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsmeetingbroadcastpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsmeetingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsMeetingTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsmeetingtemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsmessagingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsmobilitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsNetworkRoamingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsnetworkroamingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsRecordingRollOutPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsrecordingrolloutpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsRoomVideoTeleConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsroomvideoteleconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsSharedCallingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamssharedcallingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsShiftsConnection.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsshiftsconnection",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsShiftsConnectionBatchTeamMap.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsshiftsconnectionbatchteammap",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsShiftsConnectionInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsshiftsconnectioninstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsShiftsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsshiftspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsSurvivableBranchAppliance.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamssurvivablebranchappliance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsSurvivableBranchAppliancePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamssurvivablebranchappliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamstemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamstranslationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsUnassignedNumberTreatment.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsunassignednumbertreatment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsUpdateManagementPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsupdatemanagementpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsVdiPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsvdipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsVirtualAppointmentsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsvirtualappointmentspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsVoiceApplicationsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsvoiceapplicationspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsWorkLoadPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsworkloadpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsWorkLocationDetectionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csteamsworklocationdetectionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cstenantdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTenantNetworkRegion.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cstenantnetworkregion",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTenantNetworkSite.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cstenantnetworksite",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTenantNetworkSubnet.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cstenantnetworksubnet",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTenantTrustedIPAddress.md",
- "redirect_url": "/powershell/module/microsoftteams/new-cstenanttrustedipaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsUserCallingDelegate.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csusercallingdelegate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsVideoInteropServiceProvider.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csvideointeropserviceprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsVoiceNormalizationRule.md",
- "redirect_url": "/powershell/module/microsoftteams/new-csvoicenormalizationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-Team.md",
- "redirect_url": "/powershell/module/microsoftteams/new-team",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-TeamChannel.md",
- "redirect_url": "/powershell/module/microsoftteams/new-teamchannel",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-TeamsApp.md",
- "redirect_url": "/powershell/module/microsoftteams/new-teamsapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Register-CsOnlineDialInConferencingServiceNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/register-csonlinedialinconferencingservicenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csapplicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsCallQueue.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cscallqueue",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cscallinglineidentity",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsComplianceRecordingForCallQueueTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cscompliancerecordingforcallqueuetemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsCustomPolicyPackage.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cscustompolicypackage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsExternalAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csexternalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsGroupPolicyAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csgrouppolicyassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsHybridTelephoneNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cshybridtelephonenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csinboundblockednumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsInboundExemptNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csinboundexemptnumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineApplicationInstanceAssociation.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlineapplicationinstanceassociation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineAudioConferencingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlineaudioconferencingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineAudioFile.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlineaudiofile",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineDialInConferencingTenantSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinedialinconferencingtenantsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlineliscivicaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineLisLocation.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinelislocation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineLisPort.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinelisport",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineLisSubnet.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinelissubnet",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineLisSwitch.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinelisswitch",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineLisWirelessAccessPoint.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlineliswirelessaccesspoint",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlinePSTNGateway.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinepstngateway",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineSchedule.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlineschedule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineTelephoneNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinetelephonenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineVoiceRoute.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinevoiceroute",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinevoiceroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csonlinevoicemailpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsPhoneNumberAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csphonenumberassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsPhoneNumberTag.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csphonenumbertag",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsSharedCallQueueHistoryTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cssharedcallqueuehistorytemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamtemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsAIPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsaipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsapppermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsappsetuppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsaudioconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamscallholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamscallparkpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamscallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamschannelspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsComplianceRecordingApplication.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamscompliancerecordingapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamscompliancerecordingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamscortanapolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsCustomBannerText.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamscustombannertext",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsemergencycallroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsemergencycallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsEnhancedEncryptionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsenhancedencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsEventsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamseventspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsfeedbackpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsFilesPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsfilespolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsipphonepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsMediaConnectivityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsmediaconnectivitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsmeetingbrandingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsmeetingbroadcastpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsmeetingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsMeetingTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsmeetingtemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsmessagingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsmobilitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsNetworkRoamingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsnetworkroamingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsNotificationAndFeedsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsnotificationandfeedspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsRecordingRollOutPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsrecordingrolloutpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsRoomVideoTeleConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsroomvideoteleconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsSharedCallingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamssharedcallingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsShiftsConnection.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsshiftsconnection",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsshiftsconnectioninstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsShiftsConnectionTeamMap.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsshiftsconnectionteammap",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsShiftsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsshiftspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsShiftsScheduleRecord.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsshiftsschedulerecord",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsSurvivableBranchAppliance.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamssurvivablebranchappliance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsSurvivableBranchAppliancePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamssurvivablebranchappliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsTargetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamstargetingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamstemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamstranslationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsUnassignedNumberTreatment.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsunassignednumbertreatment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsUpdateManagementPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsupdatemanagementpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsVdiPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsvdipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsVirtualAppointmentsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsvirtualappointmentspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsVoiceApplicationsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsvoiceapplicationspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsWorkLoadPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsworkloadpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsWorkLocationDetectionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csteamsworklocationdetectionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cstenantdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTenantNetworkRegion.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cstenantnetworkregion",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTenantNetworkSite.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cstenantnetworksite",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTenantNetworkSubnet.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cstenantnetworksubnet",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTenantTrustedIPAddress.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-cstenanttrustedipaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsUserCallingDelegate.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csusercallingdelegate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsUserLicenseGracePeriod.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csuserlicensegraceperiod",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsVideoInteropServiceProvider.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-csvideointeropserviceprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-SharedWithTeam.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-sharedwithteam",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-Team.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-team",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-TeamChannel.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-teamchannel",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-TeamChannelUser.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-teamchanneluser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-TeamTargetingHierarchy.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-teamtargetinghierarchy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-TeamUser.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-teamuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-TeamsApp.md",
- "redirect_url": "/powershell/module/microsoftteams/remove-teamsapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsApplicationAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csapplicationaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsApplicationMeetingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csapplicationmeetingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsCallQueue.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cscallqueue",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsCallingLineIdentity.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cscallinglineidentity",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsComplianceRecordingForCallQueueTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cscompliancerecordingforcallqueuetemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsExternalAccessPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csexternalaccesspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csinboundblockednumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsInboundExemptNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csinboundexemptnumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlineapplicationinstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineAudioConferencingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlineaudioconferencingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineDialInConferencingBridge.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinedialinconferencingbridge",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineDialInConferencingServiceNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinedialinconferencingservicenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineDialInConferencingTenantSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinedialinconferencingtenantsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineDialInConferencingUser.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinedialinconferencinguser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineEnhancedEmergencyServiceDisclaimer.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlineenhancedemergencyservicedisclaimer",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineLisCivicAddress.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlineliscivicaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineLisLocation.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinelislocation",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineLisPort.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinelisport",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineLisSubnet.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinelissubnet",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineLisSwitch.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinelisswitch",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineLisWirelessAccessPoint.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlineliswirelessaccesspoint",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlinePSTNGateway.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinepstngateway",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlinePstnUsage.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinepstnusage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineSchedule.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlineschedule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineVoiceApplicationInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinevoiceapplicationinstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineVoiceRoute.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinevoiceroute",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineVoiceRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinevoiceroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineVoiceUser.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinevoiceuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineVoicemailPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinevoicemailpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineVoicemailUserSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csonlinevoicemailusersettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsPhoneNumberAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csphonenumberassignment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsPhoneNumberTag.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csphonenumbertag",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsSharedCallQueueHistoryTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cssharedcallqueuehistorytemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsAIPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsaipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsAcsFederationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsacsfederationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsAppPermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsapppermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsAppSetupPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsappsetuppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsAudioConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsaudioconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsCallHoldPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamscallholdpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsCallParkPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamscallparkpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamscallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsChannelsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamschannelspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsClientConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsclientconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsComplianceRecordingApplication.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamscompliancerecordingapplication",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsComplianceRecordingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamscompliancerecordingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsCortanaPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamscortanapolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsCustomBannerText.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamscustombannertext",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsEducationAssignmentsAppPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamseducationassignmentsapppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsEducationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamseducationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsEmergencyCallRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsemergencycallroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsEmergencyCallingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsemergencycallingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsEnhancedEncryptionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsenhancedencryptionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsEventsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamseventspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsExternalAccessConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsexternalaccessconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsFeedbackPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsfeedbackpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsFilesPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsfilespolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsGuestCallingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsguestcallingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsGuestMeetingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsguestmeetingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsGuestMessagingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsguestmessagingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsIPPhonePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsipphonepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMediaConnectivityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmediaconnectivitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMeetingBrandingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmeetingbrandingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMeetingBroadcastConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmeetingbroadcastconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMeetingBroadcastPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmeetingbroadcastpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMeetingConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmeetingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMeetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmeetingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMeetingTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmeetingtemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMessagingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmessagingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMobilityPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmobilitypolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsMultiTenantOrganizationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmultitenantorganizationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsNetworkRoamingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsnetworkroamingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsNotificationAndFeedsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsnotificationandfeedspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsRecordingRollOutPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsrecordingrolloutpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsRoomVideoTeleConferencingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsroomvideoteleconferencingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsSettingsCustomApp.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamssettingscustomapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsSharedCallingRoutingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamssharedcallingroutingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsShiftsAppPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsshiftsapppolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsShiftsConnection.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsshiftsconnection",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsShiftsConnectionInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsshiftsconnectioninstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsShiftsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsshiftspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsSipDevicesConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamssipdevicesconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsSurvivableBranchAppliance.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamssurvivablebranchappliance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsSurvivableBranchAppliancePolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamssurvivablebranchappliancepolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsTargetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamstargetingpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsTemplatePermissionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamstemplatepermissionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamstranslationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsUnassignedNumberTreatment.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsunassignednumbertreatment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsUpdateManagementPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsupdatemanagementpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsUpgradeConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsupgradeconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsVdiPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsvdipolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsVirtualAppointmentsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsvirtualappointmentspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsVoiceApplicationsPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsvoiceapplicationspolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsWorkLoadPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsworkloadpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsWorkLocationDetectionPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsworklocationdetectionpolicy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTenantBlockedCallingNumbers.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cstenantblockedcallingnumbers",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTenantDialPlan.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cstenantdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTenantFederationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cstenantfederationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTenantMigrationConfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cstenantmigrationconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTenantNetworkRegion.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cstenantnetworkregion",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTenantNetworkSite.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cstenantnetworksite",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTenantNetworkSubnet.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cstenantnetworksubnet",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTenantTrustedIPAddress.md",
- "redirect_url": "/powershell/module/microsoftteams/set-cstenanttrustedipaddress",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsUser.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csuser",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsUserCallingDelegate.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csusercallingdelegate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsUserCallingSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csusercallingsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsVideoInteropServiceProvider.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csvideointeropserviceprovider",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-Team.md",
- "redirect_url": "/powershell/module/microsoftteams/set-team",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamArchivedState.md",
- "redirect_url": "/powershell/module/microsoftteams/set-teamarchivedstate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamChannel.md",
- "redirect_url": "/powershell/module/microsoftteams/set-teamchannel",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamPicture.md",
- "redirect_url": "/powershell/module/microsoftteams/set-teampicture",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamTargetingHierarchy.md",
- "redirect_url": "/powershell/module/microsoftteams/set-teamtargetinghierarchy",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamsApp.md",
- "redirect_url": "/powershell/module/microsoftteams/set-teamsapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamsEnvironmentConfig.md",
- "redirect_url": "/powershell/module/microsoftteams/set-teamsenvironmentconfig",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Start-CsExMeetingMigration.md",
- "redirect_url": "/powershell/module/microsoftteams/start-csexmeetingmigration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Sync-CsOnlineApplicationInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/sync-csonlineapplicationinstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Test-CsEffectiveTenantDialPlan.md",
- "redirect_url": "/powershell/module/microsoftteams/test-cseffectivetenantdialplan",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Test-CsInboundBlockedNumberPattern.md",
- "redirect_url": "/powershell/module/microsoftteams/test-csinboundblockednumberpattern",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Test-CsTeamsShiftsConnectionValidate.md",
- "redirect_url": "/powershell/module/microsoftteams/test-csteamsshiftsconnectionvalidate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Test-CsTeamsTranslationRule.md",
- "redirect_url": "/powershell/module/microsoftteams/test-csteamstranslationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Test-CsTeamsUnassignedNumberTreatment.md",
- "redirect_url": "/powershell/module/microsoftteams/test-csteamsunassignednumbertreatment",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Test-CsVoiceNormalizationRule.md",
- "redirect_url": "/powershell/module/microsoftteams/test-csvoicenormalizationrule",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Unregister-CsOnlineDialInConferencingServiceNumber.md",
- "redirect_url": "/powershell/module/microsoftteams/unregister-csonlinedialinconferencingservicenumber",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-CsAutoAttendant.md",
- "redirect_url": "/powershell/module/microsoftteams/update-csautoattendant",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-CsCustomPolicyPackage.md",
- "redirect_url": "/powershell/module/microsoftteams/update-cscustompolicypackage",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-CsPhoneNumberTag.md",
- "redirect_url": "/powershell/module/microsoftteams/update-csphonenumbertag",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-CsTeamTemplate.md",
- "redirect_url": "/powershell/module/microsoftteams/update-csteamtemplate",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-CsTeamsShiftsConnection.md",
- "redirect_url": "/powershell/module/microsoftteams/update-csteamsshiftsconnection",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-CsTeamsShiftsConnectionInstance.md",
- "redirect_url": "/powershell/module/microsoftteams/update-csteamsshiftsconnectioninstance",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-M365TeamsApp.md",
- "redirect_url": "/powershell/module/microsoftteams/update-m365teamsapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-M365UnifiedCustomPendingApp.md",
- "redirect_url": "/powershell/module/microsoftteams/update-m365unifiedcustompendingapp",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-M365UnifiedTenantSettings.md",
- "redirect_url": "/powershell/module/microsoftteams/update-m365unifiedtenantsettings",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/export-csonlineaudiofile.md",
- "redirect_url": "/powershell/module/microsoftteams/export-csonlineaudiofile",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/get-csteamsmessagingconfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/get-csteamsmessagingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/set-csteamsmessagingconfiguration.md",
- "redirect_url": "/powershell/module/microsoftteams/set-csteamsmessagingconfiguration",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Add-TeamsAppInstallation.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsDialPlan.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsMainlineAttendantAppointmentBookingFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsMainlineAttendantFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-CsMainlineAttendantQuestionAnswerFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-LicenseReportForChangeNotificationSubscription.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamFunSettings.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamGuestSettings.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamMemberSettings.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamMessagingSettings.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Get-TeamsAppInstallation.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsCloudMeetingPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Grant-CsExternalUserCommunicationPolicy.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsMainlineAttendantAppointmentBookingFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsMainlineAttendantQuestionAnswerFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/New-CsTeamsPinnedApp.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsMainlineAttendantAppointmentBookingFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsMainlineAttendantQuestionAnswerFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-CsTeamsPinnedApp.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Remove-TeamsAppInstallation.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsGroupPolicyAssignment.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsMainlineAttendantAppointmentBookingFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsMainlineAttendantQuestionAnswerFlow.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsOnlineDialInConferencingUserDefaultNumber.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-CsTeamsPinnedApp.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamFunSettings.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamGuestSettings.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamMemberSettings.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Set-TeamMessagingSettings.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/Update-TeamsAppInstallation.md",
- "redirect_url": "/powershell/module/microsoftteams",
- "redirect_document_id": false
- },
- {
- "source_path": "teams/teams-ps/teams/teams.md",
- "redirect_url": "/powershell/module/microsoftteams",
+ "redirect_url": "/powershell/teams",
"redirect_document_id": false
}
]
diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index bb1f6d26ca..6c58de1513 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -3,7 +3,7 @@ title: About the Exchange Online PowerShell V3 module
ms.author: chrisda
author: chrisda
manager: deniseb
-ms.date: 07/31/2025
+ms.date: 07/11/2025
ms.audience: Admin
audience: Admin
ms.topic: article
@@ -200,15 +200,9 @@ The procedures in this section explain how to install, update, and uninstall the
### Supported operating systems for the Exchange Online PowerShell module
-The module is officially supported in PowerShell 7 on Windows, Linux, and Apple macOS:
+Versions of the module since 2021 are officially supported in PowerShell 7 on Windows, Linux, and Apple macOS (PowerShell 7.0.3 or later).
-- Module versions 3.5.1 (July 2024) or later require PowerShell 7 version 7.4.0 (November 2023) or later. Earlier versions of PowerShell 7 might encounter compatibility issues due to missing .NET 8.0 assemblies (v3.5.1 is built on .NET 8.0).
-- Module versions 2.0.4 (February 2021) to 3.5.0 (May 2024) are supported in PowerShell 7 version 7.0.3 (July 2020) or later.
-
-For more information about PowerShell 7, see [What is PowerShell?](/powershell/scripting/overview).
-
-> [!TIP]
-> All versions of the module are supported and compatible in Windows PowerShell 5.1.
+For more information about PowerShell 7, see [Announcing PowerShell 7.0](https://devblogs.microsoft.com/powershell/announcing-PowerShell-7-0/).
#### Apple macOS
@@ -267,30 +261,23 @@ Now you can do the [regular PowerShell prerequisites](#prerequisites-for-the-exc
#### Windows
-- **Windows PowerShell 5.1**:
- - All versions of the module are supported.
- - Version 2.0.5 (May 2021) or later versions of the module require the Microsoft .NET Framework 4.7.2 or later to connect. Otherwise, you get a `System.Runtime.InteropServices.OSPlatform` error. For more information about versions of Windows that support the .NET Framework 4.7.2, see [this article](/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-472).
+All versions of the module are supported in Windows PowerShell 5.1.
- > [!TIP]
- > Current versions of Windows include the required versions of .NET and/or the .NET Framework, so you don't need to install .NET or the .NET Framework to use the module in Windows PowerShell 5.1.
+PowerShell 7 on Windows requires version 2.0.4 or later.
-- **PowerShell 7**:
- - Module versions 3.5.1 (July 2024) or later require PowerShell 7 version 7.4.0 (November 2023) or later. Earlier versions of PowerShell 7 might encounter compatibility issues due to missing .NET 8.0 assemblies (v3.5.1 is built on .NET 8.0).
- - Module versions 2.0.4 (February 2021) to 3.5.0 (May 2024) are supported in PowerShell 7 version 7.0.3 (July 2020) or later.
+Version 2.0.5 or later of the module requires the Microsoft .NET Framework 4.7.2 or later to connect. Otherwise, you get a `System.Runtime.InteropServices.OSPlatform` error. This requirement shouldn't be an issue in current versions of Windows. For more information about versions of Windows that support the .NET Framework 4.7.2, see [this article](/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-472).
Windows PowerShell requirements and module support **in older versions of Windows** are described in the following list:
-- Windows 10¹
-- Windows 8.1² ³
-- Windows Server 2012 or Windows Server 2012 R2² ³
-- Windows 7 Service Pack 1 (SP1)² ⁴ ⁵
-- Windows Server 2008 R2 SP1² ⁴ ⁵
-
-¹ Windows 10 Anniversary Update (version 1607 from August 2016) is the earliest version of Windows 10 that's reliably compatible with the .NET Framework 4.7.2 (v2.0.5 or later versions of the module in Windows PowerShell 5.1).
-² Support for this version of Windows is over. This version of Windows is supported only in Azure virtual machines.
-³ PowerShell 7 on this version of Windows requires a compatible version of .NET Core or .NET runtime and the [Windows 10 Universal C Runtime (CRT)](https://support.microsoft.com/topic/c0514201-7fe6-95a3-b0a5-287930f3560c). The last officially supported version of PowerShell 7 on this version of Windows is 7.2 (7.2.19 from August 2024), which means the last supported version of the module in PowerShell 7 is v3.5.0 (May 2024).
-⁴ The latest version of the module supported on this version of Windows is v2.0.3 (September 2020).
-⁵ Windows PowerShell 5.1 on this version of Windows requires the .NET Framework 4.5 or later and the Windows Management Framework 5.1. For more information, see [Windows Management Framework 5.1](https://aka.ms/wmf5download).
+- Windows 8.1¹
+- Windows Server 2012 or Windows Server 2012 R2¹
+- Windows 7 Service Pack 1 (SP1)² ³ ⁴
+- Windows Server 2008 R2 SP1² ³ ⁴
+
+- ¹ PowerShell 7 on this version of Windows requires the [Windows 10 Universal C Runtime (CRT)](https://www.microsoft.com/download/details.aspx?id=50410).
+- ² Support for this version of Windows is over. This version of Windows is supported only in Azure virtual machines.
+- ³ This version of Windows supports only v2.0.3 or earlier versions of the module.
+- ⁴ Windows PowerShell 5.1 on this version of Windows requires the .NET Framework 4.5 or later and the Windows Management Framework 5.1. For more information, see [Windows Management Framework 5.1](https://aka.ms/wmf5download).
### Prerequisites for the Exchange Online PowerShell module
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md b/exchange/exchange-ps/exchange/Add-ADPermission.md
similarity index 85%
rename from exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
rename to exchange/exchange-ps/exchange/Add-ADPermission.md
index 0f883fb2c0..c1daf4b98b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
+++ b/exchange/exchange-ps/exchange/Add-ADPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-adpermission
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-ADPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-adpermission
-schema: 2.0.0
-title: Add-ADPermission
+ms.reviewer:
---
# Add-ADPermission
@@ -89,15 +88,13 @@ This example assumes that another security mechanism is used to ensure the Recei
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the object that's getting permissions added. You can specify either the distinguished name (DN) of the object or the object's name if it's unique. If the DN or name contains spaces, enclose the name in quotation marks (").
```yaml
Type: ADRawEntryIdParameter
-Parameter Sets: AccessRights, Owner, Instance
+Parameter Sets: AccessRights, Owner
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -106,16 +103,27 @@ Accept pipeline input: True
Accept wildcard characters: False
```
-### -Instance
+```yaml
+Type: ADRawEntryIdParameter
+Parameter Sets: Instance
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: True
+Accept wildcard characters: False
+```
+### -Instance
The Instance parameter enables you to pass an entire object to the command to be processed. It's mainly used in scripts where an entire object must be passed to the command.
```yaml
Type: ADAcePresentationObject
Parameter Sets: Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -125,9 +133,6 @@ Accept wildcard characters: False
```
### -Owner
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Owner parameter specifies the owner of the Active Directory object. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -153,6 +158,7 @@ You can't use this parameter with the AccessRights or User parameters.
Type: SecurityPrincipalIdParameter
Parameter Sets: Owner
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -162,9 +168,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The User parameter specifies who gets the permissions on the Active Directory object. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -193,8 +196,9 @@ You can't use this parameter with the Owner parameter.
```yaml
Type: SecurityPrincipalIdParameter
-Parameter Sets: AccessRights, Instance
+Parameter Sets: AccessRights
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -203,10 +207,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -AccessRights
+```yaml
+Type: SecurityPrincipalIdParameter
+Parameter Sets: Instance
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -AccessRights
The AccessRights parameter specifies the rights that you want to add for the user on the Active Directory object. Valid values include:
- AccessSystemSecurity
@@ -237,6 +251,7 @@ You can't use this parameter with the Owner parameter.
Type: ActiveDirectoryRights[]
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -246,9 +261,6 @@ Accept wildcard characters: False
```
### -ChildObjectTypes
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ChildObjectTypes parameter specifies what type of object the permission should be applied to.
The ChildObjectTypes parameter can only be used if the AccessRights parameter is set to CreateChild or DeleteChild.
@@ -257,6 +269,7 @@ The ChildObjectTypes parameter can only be used if the AccessRights parameter is
Type: ADSchemaObjectIdParameter[]
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -266,9 +279,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -278,6 +288,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -287,15 +298,13 @@ Accept wildcard characters: False
```
### -Deny
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Deny switch specifies that the permissions you're adding are Deny permissions. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -305,9 +314,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -316,6 +322,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -325,15 +332,13 @@ Accept wildcard characters: False
```
### -ExtendedRights
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedRights parameter specifies the extended rights needed to perform the operation.
```yaml
Type: ExtendedRightIdParameter[]
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -343,9 +348,6 @@ Accept wildcard characters: False
```
### -InheritanceType
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The InheritanceType parameter specifies how permissions are inherited. Valid values are:
- None
@@ -358,6 +360,7 @@ The InheritanceType parameter specifies how permissions are inherited. Valid val
Type: ActiveDirectorySecurityInheritance
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -367,15 +370,13 @@ Accept wildcard characters: False
```
### -InheritedObjectType
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The InheritedObjectType parameter specifies what kind of object inherits this access control entry (ACE).
```yaml
Type: ADSchemaObjectIdParameter
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -385,9 +386,6 @@ Accept wildcard characters: False
```
### -Properties
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Properties parameter specifies what properties the object contains.
The Properties parameter can only be used if the AccessRights parameter is set to ReadProperty, WriteProperty or Self.
@@ -396,6 +394,7 @@ The Properties parameter can only be used if the AccessRights parameter is set t
Type: ADSchemaObjectIdParameter[]
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -405,15 +404,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md b/exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md
rename to exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md
index 89c8a158a9..000fae4281 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md
+++ b/exchange/exchange-ps/exchange/Add-AttachmentFilterEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-attachmentfilterentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-AttachmentFilterEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-attachmentfilterentry
-schema: 2.0.0
-title: Add-AttachmentFilterEntry
+ms.reviewer:
---
# Add-AttachmentFilterEntry
@@ -30,7 +29,7 @@ Add-AttachmentFilterEntry -Name -Type
```
## DESCRIPTION
-On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://learn.microsoft.com/powershell/module/exchangepowershell/set-attachmentfilterlistconfig).
+On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://learn.microsoft.com/powershell/module/exchange/set-attachmentfilterlistconfig).
On Edge Transport servers, you need to be a member of the local Administrators group to run this cmdlet.
@@ -53,9 +52,6 @@ This example adds an attachment filter entry based on the MIME content type imag
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies the files that you want to block. Valid values are:
- A exact file name (for example, BadFile.exe) or file name extension (for example, \*.exe). You need to use the value Filename for the Type parameter.
@@ -65,6 +61,7 @@ The Name parameter specifies the files that you want to block. Valid values are:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Type parameter specifies what type of attachment the attachment filter entry blocks. Valid values are:
- ContentType: This value matches the attachment filter entry against the MIME content type that's specified in the Name parameter.
@@ -86,6 +80,7 @@ The Type parameter specifies what type of attachment the attachment filter entry
Type: AttachmentType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -107,6 +99,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -127,6 +117,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -136,15 +127,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
rename to exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md
index dae8361398..aedd7aee1a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/exchange/Add-AvailabilityAddressSpace.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-availabilityaddressspace
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Add-AvailabilityAddressSpace
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-availabilityaddressspace
-schema: 2.0.0
-title: Add-AvailabilityAddressSpace
+ms.reviewer:
---
# Add-AvailabilityAddressSpace
@@ -75,9 +74,6 @@ In Exchange Online, this example sets up the sharing of free/busy information wi
## PARAMETERS
### -AccessMethod
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The AccessMethod parameter specifies how the free/busy data is accessed. Valid values are:
- PerUserFB: Per-user free/busy information can be requested. The free/busy data is accessed in the defined per-user free/busy proxy account or group, or in the All Exchange Servers group. This value requires a trust between the two forests, and requires you to use either the UseServiceAccount parameter or Credentials parameter.
@@ -90,6 +86,7 @@ The AccessMethod parameter specifies how the free/busy data is accessed. Valid v
Type: AvailabilityAccessMethod
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -99,15 +96,13 @@ Accept wildcard characters: False
```
### -ForestName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ForestName parameter specifies the SMTP domain name of the target forest that contains the users you're trying to read free/busy information from. If users are distributed among multiple SMTP domains in the target forest, run the Add-AvailabilityAddressSpace command once for each SMTP domain.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -117,9 +112,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -129,6 +121,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -138,9 +131,6 @@ Accept wildcard characters: False
```
### -Credentials
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Credentials parameter specifies the username and password that's used to access the Availability services in the target forest.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -149,6 +139,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -158,9 +149,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -169,6 +157,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -178,19 +167,17 @@ Accept wildcard characters: False
```
### -ProxyUrl
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ProxyUrl parameter was used to specify the URL that directed an Exchange 2007 Client Access server to proxy free/busy requests through an Exchange 2010 or Exchange 2013 Client Access server when requesting federated free/busy data for a user in another organization. When you used this parameter, you needed to set the AccessMethod parameter value to InternalProxy.
-This parameter required that you created the proper trust relationships and sharing relationships between the Exchange organizations. For more information, see [New-FederationTrust](https://learn.microsoft.com/powershell/module/exchangepowershell/new-federationtrust).
+This parameter required that you created the proper trust relationships and sharing relationships between the Exchange organizations. For more information, see [New-FederationTrust](https://learn.microsoft.com/powershell/module/exchange/new-federationtrust).
```yaml
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -200,15 +187,13 @@ Accept wildcard characters: False
```
### -TargetAutodiscoverEpr
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The TargetAutodiscoverEpr parameter specifies the Autodiscover URL of Exchange Web Services for the external organization that you're trying to read free/busy information from. For example, `https://contoso.com/autodiscover/autodiscover.xml`. Exchange uses Autodiscover to automatically detect the correct server endpoint for external requests.
```yaml
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -218,9 +203,6 @@ Accept wildcard characters: False
```
### -TargetServiceEpr
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The TargetServiceEpr parameter specifies the Exchange Online Calendar Service URL of the external Microsoft 365 organization that you're trying to read free/busy information from. Valid values are:
@@ -233,6 +215,7 @@ The TargetServiceEpr parameter specifies the Exchange Online Calendar Service UR
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -242,9 +225,6 @@ Accept wildcard characters: False
```
### -TargetTenantId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The TargetTenantID parameter specifies the tenant ID of the external Microsoft 365 organization that you're trying to read free/busy information from.
@@ -253,6 +233,7 @@ The TargetTenantID parameter specifies the tenant ID of the external Microsoft 3
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -262,9 +243,6 @@ Accept wildcard characters: False
```
### -UseServiceAccount
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The UseServiceAccount parameter specifies whether to use the local Availability service account for authorization. Valid values
@@ -276,6 +254,7 @@ The UseServiceAccount parameter specifies whether to use the local Availability
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -285,15 +264,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/Add-ComplianceCaseMember.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Add-ComplianceCaseMember.md
rename to exchange/exchange-ps/exchange/Add-ComplianceCaseMember.md
index c486c651c8..ddec608aad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ComplianceCaseMember.md
+++ b/exchange/exchange-ps/exchange/Add-ComplianceCaseMember.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-compliancecasemember
applicable: Security & Compliance
+title: Add-ComplianceCaseMember
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-compliancecasemember
-schema: 2.0.0
-title: Add-ComplianceCaseMember
+ms.reviewer:
---
# Add-ComplianceCaseMember
@@ -51,9 +50,6 @@ This example adds John Evans to the eDiscovery case named Case 2112.
## PARAMETERS
### -Case
-
-> Applicable: Security & Compliance
-
The Case parameter specifies the name of the eDiscovery case that you want to modify. If the value contains spaces, enclose the value in quotation marks (").
To see the available eDiscovery cases, use the Get-ComplianceCase cmdlet.
@@ -62,6 +58,7 @@ To see the available eDiscovery cases, use the Get-ComplianceCase cmdlet.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -Member
-
-> Applicable: Security & Compliance
-
The Member parameter specifies the user that you want to add to the eDiscovery case. You can use any value that uniquely identifies the user. For example:
- Name
@@ -85,6 +79,7 @@ The Member parameter specifies the user that you want to add to the eDiscovery c
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -94,9 +89,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -106,6 +98,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -115,15 +108,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md b/exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
rename to exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md
index 6065a9815c..72bcef12ec 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/exchange/Add-ContentFilterPhrase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-contentfilterphrase
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-ContentFilterPhrase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-contentfilterphrase
-schema: 2.0.0
-title: Add-ContentFilterPhrase
+ms.reviewer:
---
# Add-ContentFilterPhrase
@@ -46,15 +45,13 @@ This example adds the phrase Free credit report to the Block phrase list. Any me
## PARAMETERS
### -Phrase
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Phrase parameter specifies a custom word or phrase for the Content Filter agent. When you pass an argument, you must enclose the Phrase parameter in quotation marks (") if the phrase contains spaces, for example: "This is a bad phrase". Custom phrases must be less than 257 characters in length.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -64,9 +61,6 @@ Accept wildcard characters: False
```
### -Influence
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Influence parameter specifies whether the phrase being added will cause the messages that contain the phrase to be allowed or blocked. Valid values are GoodWord and BadWord.
A message that contains a custom word or phrase that has an Influence value of GoodWord is automatically assigned a spam confidence level (SCL) rating of 0 and therefore bypasses downstream spam processing. A message that contains a custom word or phrase that has an Influence value of BadWord is automatically assigned an SCL rating of 9 and therefore is treated as spam.
@@ -75,6 +69,7 @@ A message that contains a custom word or phrase that has an Influence value of G
Type: Influence
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -84,9 +79,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -96,6 +88,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -105,9 +98,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -116,6 +106,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -125,15 +116,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
rename to exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md
index 897bf7a61f..d1e4a31542 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
+++ b/exchange/exchange-ps/exchange/Add-DatabaseAvailabilityGroupServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-databaseavailabilitygroupserver
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-DatabaseAvailabilityGroupServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-databaseavailabilitygroupserver
-schema: 2.0.0
-title: Add-DatabaseAvailabilityGroupServer
+ms.reviewer:
---
# Add-DatabaseAvailabilityGroupServer
@@ -51,15 +50,13 @@ This example adds the Mailbox server MBX1 to the DAG DAG1.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of the DAG to which the server is being added.
```yaml
Type: DatabaseAvailabilityGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -MailboxServer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MailboxServer parameter specifies the Mailbox server to add to the DAG. You can use any value that uniquely identifies the server. For example:
- Name
@@ -83,6 +77,7 @@ The MailboxServer parameter specifies the Mailbox server to add to the DAG. You
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 2
@@ -92,9 +87,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -104,6 +96,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,15 +106,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,15 +122,13 @@ Accept wildcard characters: False
```
### -SkipDagValidation
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SkipDagValidation switch specifies whether to bypass the validation of the DAG's quorum model and the health check on the DAG's witness when adding members to the DAG. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -149,15 +138,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md b/exchange/exchange-ps/exchange/Add-DistributionGroupMember.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
rename to exchange/exchange-ps/exchange/Add-DistributionGroupMember.md
index b87a4f59b9..90029ad72b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
+++ b/exchange/exchange-ps/exchange/Add-DistributionGroupMember.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-distributiongroupmember
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Add-DistributionGroupMember
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-distributiongroupmember
-schema: 2.0.0
-title: Add-DistributionGroupMember
+ms.reviewer:
---
# Add-DistributionGroupMember
@@ -46,9 +45,6 @@ This example adds John Evans to the distribution group named Staff.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the group that you want to modify. You can use any value that uniquely identifies the group. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the group that you want to modify. You can use
Type: DistributionGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -BypassSecurityGroupManagerCheck
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
If you aren't defined in the ManagedBy property of the group, you need to use this switch in commands that modify or delete the group. To use this switch, your account requires specific permissions based on the group type:
@@ -85,6 +79,7 @@ If you aren't defined in the ManagedBy property of the group, you need to use th
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -94,9 +89,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -106,6 +98,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -126,6 +116,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -135,9 +126,6 @@ Accept wildcard characters: False
```
### -Member
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Member parameter specifies the recipient that you want to add to the group. A member can be any mail-enabled recipient in your organization. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -153,6 +141,7 @@ Although it isn't required, it's a good idea to add only security principals (fo
Type: RecipientWithAdUserGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -162,15 +151,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md b/exchange/exchange-ps/exchange/Add-FederatedDomain.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
rename to exchange/exchange-ps/exchange/Add-FederatedDomain.md
index 25568ab2fa..1a193dfead 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
+++ b/exchange/exchange-ps/exchange/Add-FederatedDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-federateddomain
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-FederatedDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-federateddomain
-schema: 2.0.0
-title: Add-FederatedDomain
+ms.reviewer:
---
# Add-FederatedDomain
@@ -50,15 +49,13 @@ This example adds the domain Contoso.co.uk to the existing federation trust.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -68,15 +65,13 @@ Accept wildcard characters: False
```
### -DomainName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainName parameter specifies the secondary domain to be configured.
```yaml
Type: SmtpDomain
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -86,9 +81,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -98,6 +90,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -107,15 +100,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -125,15 +116,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md b/exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
rename to exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md
index 7cdc6eb202..975a6bf632 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/exchange/Add-GlobalMonitoringOverride.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-globalmonitoringoverride
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-GlobalMonitoringOverride
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-globalmonitoringoverride
-schema: 2.0.0
-title: Add-GlobalMonitoringOverride
+ms.reviewer:
---
# Add-GlobalMonitoringOverride
@@ -65,15 +64,13 @@ This example adds a global monitoring override that disables the StorageLogicalD
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the probe, monitor, or responder. This parameter uses the syntax `HealthSetName\MonitoringItemName[\TargetResource]`. Note that the values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityServerReboot`, not `ad\activedirectoryconnectivityserverreboot`.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -83,9 +80,6 @@ Accept wildcard characters: False
```
### -ApplyVersion
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ApplyVersion parameter specifies the version of Exchange that gets the override. If an Exchange server is older or newer than the version you specify, the override isn't applied to the server. Typically, you increase the Exchange version by applying Cumulative Updates or Service Packs.
Valid input for this parameter is an Exchange version number in the format 15.0x.xxxx.xxx.
@@ -96,6 +90,7 @@ You can't use this parameter with the Duration parameter.
Type: Version
Parameter Sets: ApplyVersion
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -105,9 +100,6 @@ Accept wildcard characters: False
```
### -ItemType
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ItemType parameter specifies the item type for the property that you want to override. Valid values are:
- Probe
@@ -118,6 +110,7 @@ The ItemType parameter specifies the item type for the property that you want to
Type: MonitoringItemTypeEnum
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -127,15 +120,13 @@ Accept wildcard characters: False
```
### -PropertyName
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PropertyName parameter specifies the property that you want to override.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -145,15 +136,13 @@ Accept wildcard characters: False
```
### -PropertyValue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PropertyValue parameter specifies the new value for the property that you want to override.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -163,9 +152,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -175,6 +161,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -184,9 +171,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -195,6 +179,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -204,9 +189,6 @@ Accept wildcard characters: False
```
### -Duration
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Duration parameter specifies the length of time that the override is active.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -219,6 +201,7 @@ You can't use this parameter with the ApplyVersion parameter.
Type: EnhancedTimeSpan
Parameter Sets: Duration
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -228,15 +211,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -246,15 +227,13 @@ Accept wildcard characters: False
```
### -BuildRange
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: Duration
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -264,15 +243,13 @@ Accept wildcard characters: False
```
### -Roles
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md b/exchange/exchange-ps/exchange/Add-IPAllowListEntry.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md
rename to exchange/exchange-ps/exchange/Add-IPAllowListEntry.md
index 8aeb4bef69..d987ed4c56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md
+++ b/exchange/exchange-ps/exchange/Add-IPAllowListEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-ipallowlistentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-IPAllowListEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-ipallowlistentry
-schema: 2.0.0
-title: Add-IPAllowListEntry
+ms.reviewer:
---
# Add-IPAllowListEntry
@@ -66,15 +65,13 @@ This example adds the IP address range 192.168.0.1/24 to the list of allowed IP
## PARAMETERS
### -IPAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IPAddress parameter specifies a single IP address to add to the IP Allow list, for example, 192.168.0.1.
```yaml
Type: IPAddress
Parameter Sets: IPAddress
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -84,9 +81,6 @@ Accept wildcard characters: False
```
### -IPRange
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IPRange parameter specifies a range of IP addresses to add to the IP Allow list. Valid values are:
- IP address range: 192.168.0.1-192.168.0.254.
@@ -96,6 +90,7 @@ The IPRange parameter specifies a range of IP addresses to add to the IP Allow l
Type: IPRange
Parameter Sets: IPRange
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -105,15 +100,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -123,9 +116,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -135,6 +125,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -144,9 +135,6 @@ Accept wildcard characters: False
```
### -ExpirationTime
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExpirationTime parameter specifies a day and time when the IP Allow list entry that you're creating will expire. If you specify a time only and you don't specify a date, the current day is assumed.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -155,6 +143,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -164,9 +153,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -182,6 +168,7 @@ You can't use this parameter to configure other Edge Transport servers remotely.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -191,15 +178,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md b/exchange/exchange-ps/exchange/Add-IPAllowListProvider.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md
rename to exchange/exchange-ps/exchange/Add-IPAllowListProvider.md
index d9f0360b2b..9b528293bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md
+++ b/exchange/exchange-ps/exchange/Add-IPAllowListProvider.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-ipallowlistprovider
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-IPAllowListProvider
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-ipallowlistprovider
-schema: 2.0.0
-title: Add-IPAllowListProvider
+ms.reviewer:
---
# Add-IPAllowListProvider
@@ -56,15 +55,13 @@ This example adds an IP Allow list provider and configures a bitmask return valu
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies a descriptive name for the IP Allow list provider.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -74,15 +71,13 @@ Accept wildcard characters: False
```
### -LookupDomain
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LookupDomain parameter specifies the host name that's required to use the allow list provider. Connection filtering sends the IP address of the connecting SMTP server to the host name value that you specify. An example value is allowlist.spamservice.com. The actual value you need to use is provided by the allow list provider.
```yaml
Type: SmtpDomain
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -AnyMatch
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AnyMatch parameter specifies whether any response by the allow list provider is treated as a match. Valid input for this parameter is $true or $false. The default value is $false. When this parameter is set to $true, and connection filtering sends the IP address of the connecting SMTP server to the allow list provider, any response code returned by the allow list provider causes connection filtering to allow messages from that source.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -110,15 +103,13 @@ Accept wildcard characters: False
```
### -BitmaskMatch
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BitmaskMatch parameter specifies the bit mask status code that's returned by the allow list provider. Use this parameter if the allow list provider returns bitmask responses. Valid input for this parameter is a single IP address in the format 127.0.0.1.
```yaml
Type: IPAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -128,9 +119,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -140,6 +128,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -149,9 +138,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -160,6 +146,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -169,15 +156,13 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Enabled parameter specifies whether the connection filtering uses this IP Allow List provider. Valid input for this parameter is $true or $false. The default value is $true. By default, connection filtering uses new IP Allow List providers that you create.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -187,15 +172,13 @@ Accept wildcard characters: False
```
### -IPAddressesMatch
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IPAddressesMatch parameter specifies the IP address status codes that are returned by the allow list provider. Use this parameter if the allow list provider returns IP address or A record responses. Valid input for this parameter one or more IP addresses in the format 127.0.0.1. You can enter multiple IP addresses separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -205,9 +188,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Priority parameter specifies the order that the Connection Filtering agent queries the IP Allow list providers that you have configured. A lower priority integer value indicates a higher priority. By default, every time that you add a new IP Allow list provider, the entry is assigned a priority of N+1, where N is the number of IP Allow list providers that you have configured.
If you set the Priority parameter to a value that's the same as another IP Allow list provider, the priority of the IP Allow list provider that you add first is incremented by 1.
@@ -216,6 +196,7 @@ If you set the Priority parameter to a value that's the same as another IP Allow
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -225,15 +206,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md b/exchange/exchange-ps/exchange/Add-IPBlockListEntry.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md
rename to exchange/exchange-ps/exchange/Add-IPBlockListEntry.md
index c121c4bd15..35072b31fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md
+++ b/exchange/exchange-ps/exchange/Add-IPBlockListEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-ipblocklistentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-IPBlockListEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-ipblocklistentry
-schema: 2.0.0
-title: Add-IPBlockListEntry
+ms.reviewer:
---
# Add-IPBlockListEntry
@@ -65,15 +64,13 @@ This example adds the IP address range 192.168.0.1/24 to the list of blocked IP
## PARAMETERS
### -IPAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IPAddress parameter specifies a single IP address to add to the IP Block list, for example, 192.168.0.1.
```yaml
Type: IPAddress
Parameter Sets: IPAddress
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -83,9 +80,6 @@ Accept wildcard characters: False
```
### -IPRange
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IPRange parameter specifies a range of IP addresses to add to the IP Block list. Valid values are:
- IP address range: 192.168.0.1-192.168.0.254.
@@ -95,6 +89,7 @@ The IPRange parameter specifies a range of IP addresses to add to the IP Block l
Type: IPRange
Parameter Sets: IPRange
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -104,15 +99,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -122,9 +115,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -134,6 +124,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -143,9 +134,6 @@ Accept wildcard characters: False
```
### -ExpirationTime
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExpirationTime parameter specifies a day and time when the IP Block list entry that you're creating will expire. If you specify a time only and you don't specify a date, the current day is assumed.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -154,6 +142,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -163,9 +152,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -181,6 +167,7 @@ You can't use this parameter to configure other Edge Transport servers remotely.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -190,15 +177,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md b/exchange/exchange-ps/exchange/Add-IPBlockListProvider.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md
rename to exchange/exchange-ps/exchange/Add-IPBlockListProvider.md
index e87c1f2b8d..29ca57a584 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md
+++ b/exchange/exchange-ps/exchange/Add-IPBlockListProvider.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-ipblocklistprovider
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-IPBlockListProvider
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-ipblocklistprovider
-schema: 2.0.0
-title: Add-IPBlockListProvider
+ms.reviewer:
---
# Add-IPBlockListProvider
@@ -57,15 +56,13 @@ This example adds an IP Block list provider and configures a bitmask return valu
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies a descriptive name for the IP Block list provider.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -LookupDomain
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LookupDomain parameter specifies the host name that's required to use the block list provider. Connection filtering sends the IP address of the connecting SMTP server to the host name value that you specify. An example value is blocklist.spamservice.com. The actual value you need to use is provided by the block list provider.
```yaml
Type: SmtpDomain
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -93,15 +88,13 @@ Accept wildcard characters: False
```
### -AnyMatch
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AnyMatch parameter specifies whether any response by the block list provider is treated as a match. Valid input for this parameter is $true or $false. The default value is $false. When this parameter is set to $true, and connection filtering sends the IP address of the connecting SMTP server to the block list provider, any response code returned by the block list provider causes connection filtering to block messages from that source.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -111,15 +104,13 @@ Accept wildcard characters: False
```
### -BitmaskMatch
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BitmaskMatch parameter specifies the bit mask status code that's returned by the block list provider. Use this parameter if the block list provider returns bitmask responses. Valid input for this parameter is a single IP address in the format 127.0.0.1.
```yaml
Type: IPAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -129,9 +120,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -141,6 +129,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -150,9 +139,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -161,6 +147,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -170,15 +157,13 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Enabled parameter specifies whether the connection filtering uses this IP Block list provider. Valid input for this parameter is $true or $false. The default value is $true. By default, connection filtering uses new IP Block List providers that you create.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -188,15 +173,13 @@ Accept wildcard characters: False
```
### -IPAddressesMatch
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IPAddressesMatch parameter specifies the IP address status codes that are returned by the block list provider. Use this parameter if the block list provider returns IP address or A record responses. Valid input for this parameter one or more IP addresses in the format 127.0.0.1. You can enter multiple IP addresses separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -206,9 +189,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Priority parameter specifies the order that the Connection Filtering agent queries the IP Block list providers. A lower priority integer value indicates a higher priority. By default, every time that you add a new IP Block list provider, the entry is assigned a priority of N+1, where N is the number of IP Block list provider services that you have configured.
If you set the Priority parameter to a value that's the same as another IP Block list provider service, the priority of the IP Block list provider that you add first is incremented by 1.
@@ -217,6 +197,7 @@ If you set the Priority parameter to a value that's the same as another IP Block
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -226,9 +207,6 @@ Accept wildcard characters: False
```
### -RejectionResponse
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RejectionResponse parameter specifies the text that you want to include in the SMTP rejection response when messages are blocked by connection filtering. The argument can't exceed 240 characters. If the value contains spaces, enclose the value in quotation marks (").
You should always specify the block list provider in the response so that legitimate senders can contact the block list provider for removal instructions. For example, "Source IP address is listed at the Contoso.com block list provider".
@@ -237,6 +215,7 @@ You should always specify the block list provider in the response so that legiti
Type: AsciiString
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -246,15 +225,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md b/exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
rename to exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md
index e255aaa90a..df90710452 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/exchange/Add-MailboxDatabaseCopy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-mailboxdatabasecopy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-MailboxDatabaseCopy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-mailboxdatabasecopy
-schema: 2.0.0
-title: Add-MailboxDatabaseCopy
+ms.reviewer:
---
# Add-MailboxDatabaseCopy
@@ -73,9 +72,6 @@ This example adds a copy of mailbox database DB3 to the Mailbox server MBX4. Rep
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox database that's being copied. You can use any value that uniquely identifies the database. For example:
- Name
@@ -86,6 +82,7 @@ The Identity parameter specifies the mailbox database that's being copied. You c
Type: DatabaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -95,15 +92,13 @@ Accept wildcard characters: False
```
### -MailboxServer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MailboxServer parameter specifies the name of the server that will host the database copy. This server must be a member of the same DAG and must not already host a copy of the database.
```yaml
Type: MailboxServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 2
@@ -113,15 +108,13 @@ Accept wildcard characters: False
```
### -ActivationPreference
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ActivationPreference parameter value is used as part of Active Manager's best copy selection process and to redistribute active mailbox databases throughout the DAG when using the RedistributeActiveDatabases.ps1 script. The value for the activation preference is a number equal to or greater than 1, where 1 is at the top of the preference order. The preference number can't be larger than the number of copies of the mailbox database.
```yaml
Type: UInt32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,9 +124,6 @@ Accept wildcard characters: False
```
### -ConfigurationOnly
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ConfigurationOnly switch allows database copies to be added without invoking automatic seeding. You don't need to specify a value with this switch.
The source database does not need to be online or present when using this parameter. It will create a new database in Active Directory without contacting the target server. This parameter may be useful in situations where the target server is down for maintenance and the new database copy does not yet exist on the target server.
@@ -142,6 +132,7 @@ The source database does not need to be online or present when using this parame
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -151,9 +142,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -163,6 +151,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -172,15 +161,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -190,9 +177,6 @@ Accept wildcard characters: False
```
### -ReplayLagMaxDelay
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The ReplayLagMaxDelay parameter specifies the maximum delay for lagged database copy play down (also known as deferred lagged copy play down). If the disk read IO latency is greater than 25 ms, lagged copy play down is delayed up to the value of this parameter.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -205,6 +189,7 @@ Note that when the disk is running out of space, the value of this parameter is
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -214,9 +199,6 @@ Accept wildcard characters: False
```
### -ReplayLagTime
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReplayLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service waits before replaying log files that have been copied to the database copy.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
@@ -227,6 +209,7 @@ The default value is 00.00:00:00, which specifies that there's no truncation lag
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -236,15 +219,13 @@ Accept wildcard characters: False
```
### -SeedingPostponed
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SeedingPostponed switch specifies that the task doesn't seed the database copy, so you need to explicitly seed the database copy. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -254,9 +235,6 @@ Accept wildcard characters: False
```
### -TruncationLagTime
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service waits before truncating log files that have replayed into a copy of the database. The time period begins after the log has been successfully replayed into the copy of the database.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -267,6 +245,7 @@ The default value is 00.00:00:00, which specifies that there's no truncation lag
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -276,15 +255,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
rename to exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md
index 721fa3fe78..bda1bfce49 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-mailboxfolderpermission
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Add-MailboxFolderPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-mailboxfolderpermission
-schema: 2.0.0
-title: Add-MailboxFolderPermission
+ms.reviewer:
---
# Add-MailboxFolderPermission
@@ -62,9 +61,6 @@ In Exchange Online, this example adds Laura as a calendar delegate to Ayla's mai
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the target mailbox and folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example:
@@ -86,6 +82,7 @@ Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Inb
Type: MailboxFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -95,9 +92,6 @@ Accept wildcard characters: False
```
### -AccessRights
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AccessRights parameter specifies the permissions that you want to add for the user on the mailbox folder.
You can specify individual folder permissions or roles, which are combinations of permissions. You can specify multiple permissions and roles separated by commas.
@@ -138,6 +132,7 @@ When the Editor role is applied to calendar folders, delegates can accept or dec
Type: MailboxFolderAccessRight[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -147,9 +142,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The User parameter specifies who's granted permission to the mailbox folder. Valid values are mail-enabled security principals (mail-enabled accounts or groups that have security identifiers or SIDs that can have permissions assigned to them). For example:
- User mailboxes
@@ -174,6 +166,7 @@ Otherwise, you can use any value that uniquely identifies the user or group. For
Type: MailboxFolderUserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -183,9 +176,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -195,6 +185,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -204,9 +195,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -215,6 +203,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -224,9 +213,6 @@ Accept wildcard characters: False
```
### -SendNotificationToUser
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you add calendar permissions for them. The message will be a normal calendar sharing invitation that can be accepted by the recipient. Valid values are:
@@ -245,6 +231,7 @@ This parameter only applies to calendar folders and can only be used with the fo
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -254,9 +241,6 @@ Accept wildcard characters: False
```
### -SharingPermissionFlags
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The SharingPermissionFlags parameter assigns calendar delegate permissions. This parameter only applies to calendar folders and can only be used when the AccessRights parameter value is Editor. Valid values are:
@@ -273,6 +257,7 @@ You can specify multiple values separated by commas.
Type: MailboxFolderPermissionFlags
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -282,15 +267,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -316,10 +299,10 @@ To see the return types, which are also known as output types, that this cmdlet
## RELATED LINKS
-[Get-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxfolderpermission)
+[Get-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderpermission)
-[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxfolderpermission)
+[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission)
-[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/remove-mailboxfolderpermission)
+[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission)
-[Get-EXOMailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/get-exomailboxfolderpermission)
+[Get-EXOMailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderpermission)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md b/exchange/exchange-ps/exchange/Add-MailboxPermission.md
similarity index 84%
rename from exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
rename to exchange/exchange-ps/exchange/Add-MailboxPermission.md
index accc016d50..07ab0e946e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
+++ b/exchange/exchange-ps/exchange/Add-MailboxPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-mailboxpermission
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Add-MailboxPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-mailboxpermission
-schema: 2.0.0
-title: Add-MailboxPermission
+ms.reviewer:
---
# Add-MailboxPermission
@@ -102,9 +101,6 @@ In Exchange Online, this example assigns the administrator account admin@contoso
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox where you want to assign permissions to the user. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -120,8 +116,9 @@ The Identity parameter specifies the mailbox where you want to assign permission
```yaml
Type: MailboxIdParameter
-Parameter Sets: AccessRights, Owner, Instance
+Parameter Sets: AccessRights, Owner
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -130,10 +127,20 @@ Accept pipeline input: True
Accept wildcard characters: False
```
-### -AccessRights
+```yaml
+Type: MailboxIdParameter
+Parameter Sets: Instance
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: True
+Accept wildcard characters: False
+```
+### -AccessRights
The AccessRights parameter specifies the permission that you want to add for the user on the mailbox. Valid values are:
- ChangeOwner
@@ -149,8 +156,9 @@ You can't use this parameter with the Owner parameter.
```yaml
Type: MailboxRights[]
-Parameter Sets: AccessRights, Instance
+Parameter Sets: AccessRights
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -159,10 +167,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -Instance
+```yaml
+Type: MailboxRights[]
+Parameter Sets: Instance
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -Instance
This parameter is available only in on-premises Exchange.
This parameter has been deprecated and is no longer used.
@@ -171,6 +189,7 @@ This parameter has been deprecated and is no longer used.
Type: MailboxAcePresentationObject
Parameter Sets: Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -180,9 +199,6 @@ Accept wildcard characters: False
```
### -Owner
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Owner parameter specifies the owner of the mailbox object. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -210,6 +226,7 @@ You can't use this parameter with the AccessRights or User parameters.
Type: SecurityPrincipalIdParameter
Parameter Sets: Owner
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -219,9 +236,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The User parameter specifies who gets the permissions on the mailbox. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -252,8 +266,9 @@ You can't use this parameter with the Owner parameter.
```yaml
Type: SecurityPrincipalIdParameter
-Parameter Sets: AccessRights, Instance
+Parameter Sets: AccessRights
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -262,10 +277,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -AutoMapping
+```yaml
+Type: SecurityPrincipalIdParameter
+Parameter Sets: Instance
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -AutoMapping
The AutoMapping parameter includes or excludes the mailbox from the auto-mapping feature in Microsoft Outlook. Auto-mapping uses Autodiscover to automatically add mailboxes to a user's Outlook profile if the user has Full Access permission to the mailbox. However, Autodiscover won't enumerate security groups that are given Full Access permission to the mailbox. Valid values are:
- $true: The mailbox is automatically added to the user's Outlook profile if the user has Full Access permission. This is the default value.
@@ -277,6 +302,7 @@ The AutoMapping parameter includes or excludes the mailbox from the auto-mapping
Type: Boolean
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -286,9 +312,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -298,6 +321,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -307,15 +331,13 @@ Accept wildcard characters: False
```
### -Deny
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Deny switch specifies that the permissions you're adding are Deny permissions. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -325,9 +347,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -336,6 +355,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -345,9 +365,6 @@ Accept wildcard characters: False
```
### -GroupMailbox
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The GroupMailbox switch is required to add permissions to a Microsoft 365 Group mailbox. You don't need to specify a value with this switch.
@@ -356,6 +373,7 @@ The GroupMailbox switch is required to add permissions to a Microsoft 365 Group
Type: SwitchParameter
Parameter Sets: AccessRights, Owner, Instance
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -365,9 +383,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -379,6 +394,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -388,9 +404,6 @@ Accept wildcard characters: False
```
### -InheritanceType
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The InheritanceType parameter specifies how permissions are inherited by folders in the mailbox. Valid values are:
- None
@@ -403,6 +416,7 @@ The InheritanceType parameter specifies how permissions are inherited by folders
Type: ActiveDirectorySecurityInheritance
Parameter Sets: AccessRights, Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -412,15 +426,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md b/exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
rename to exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md
index c356ae0e7b..6b98323cb7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/exchange/Add-ManagementRoleEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-managementroleentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Add-ManagementRoleEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-managementroleentry
-schema: 2.0.0
-title: Add-ManagementRoleEntry
+ms.reviewer:
---
# Add-ManagementRoleEntry
@@ -89,9 +88,6 @@ In on-premises Exchange, this example adds the MailboxAudit script with the Depa
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the role entry that you want to add. This parameter uses the syntax: `Management role\role entry name` (for example, `CustomRole\Set-Mailbox`).
For more information about how management role entries work, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
@@ -102,6 +98,7 @@ The role entry you want to add must exist in the parent role. If the role entry
Type: RoleEntryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -111,15 +108,13 @@ Accept wildcard characters: False
```
### -ParentRoleEntry
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ParentRoleEntry parameter specifies the role entry in the parent role to add to the role specified with the Role parameter. This parameter generally isn't used directly, but exists to enable the piping of role entries from the Get-ManagementRoleEntry cmdlet. If you use the ParentRoleEntry parameter, you can't use the UnScopedTopLevel switch.
```yaml
Type: RoleEntryIdParameter
Parameter Sets: ParentRoleEntry
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -129,15 +124,13 @@ Accept wildcard characters: False
```
### -Role
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Role parameter specifies the role to which the new role entry, specified by the ParentRoleEntry parameter, is added.
```yaml
Type: RoleIdParameter
Parameter Sets: ParentRoleEntry
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -147,9 +140,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -159,6 +149,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -168,9 +159,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -179,6 +167,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -188,9 +177,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
@@ -201,6 +187,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -210,15 +197,13 @@ Accept wildcard characters: False
```
### -Overwrite
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Overwrite switch causes existing role entries to be overwritten by the role entries being added. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -228,15 +213,13 @@ Accept wildcard characters: False
```
### -Parameters
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Parameters parameter specifies the parameters to be included in the role being added. The parameters specified must exist on the cmdlet associated with the role entry. You can specify multiple parameters, separated with commas.
```yaml
Type: String[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -246,9 +229,6 @@ Accept wildcard characters: False
```
### -PSSnapinName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The PSSnapinName parameter specifies the Windows PowerShell snap-in that contains the cmdlet associated with the role being added. Use the Get-PSSnapin cmdlet to retrieve a list of available Windows PowerShell snap-ins.
@@ -257,6 +237,7 @@ The PSSnapinName parameter specifies the Windows PowerShell snap-in that contain
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -266,15 +247,13 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Type parameter specifies the type of role entry being added. The valid values are Cmdlet, Script and ApplicationPermission.
```yaml
Type: ManagementRoleEntryType
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -284,9 +263,6 @@ Accept wildcard characters: False
```
### -UnScopedTopLevel
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
By default, this parameter is available only in the UnScoped Role Management role, and that role isn't assigned to any role groups. To use this parameter, you need to add the UnScoped Role Management role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group).
@@ -301,6 +277,7 @@ You can't use this switch with the ParentRoleEntry parameter.
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -310,15 +287,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md
rename to exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md
index 7049b48a5c..153ba0c086 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md
+++ b/exchange/exchange-ps/exchange/Add-PublicFolderAdministrativePermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-publicfolderadministrativepermission
applicable: Exchange Server 2010
+title: Add-PublicFolderAdministrativePermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-publicfolderadministrativepermission
-schema: 2.0.0
-title: Add-PublicFolderAdministrativePermission
+ms.reviewer:
---
# Add-PublicFolderAdministrativePermission
@@ -79,17 +78,15 @@ This example denies the user Chris the ViewInformationStore permission.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\\PublicFolder.
You can omit the parameter label so that only the public folder name or GUID is supplied.
```yaml
Type: PublicFolderIdParameter
-Parameter Sets: Identity, Owner, Instance
+Parameter Sets: Identity, Owner
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: 1
@@ -98,10 +95,20 @@ Accept pipeline input: True
Accept wildcard characters: False
```
-### -AccessRights
+```yaml
+Type: PublicFolderIdParameter
+Parameter Sets: Instance
+Aliases:
+Applicable: Exchange Server 2010
-> Applicable: Exchange Server 2010
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: True
+Accept wildcard characters: False
+```
+### -AccessRights
The AccessRights parameter specifies the rights that you want to add for the administrator on the public folder. Valid values include:
- None The administrator has no rights to modify public folder attributes.
@@ -121,8 +128,9 @@ You can't use this parameter with the Owner parameter.
```yaml
Type: MultiValuedProperty
-Parameter Sets: Identity, Instance
+Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -131,16 +139,27 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -Instance
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: Instance
+Aliases:
+Applicable: Exchange Server 2010
-> Applicable: Exchange Server 2010
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -Instance
The Instance parameter specifies whether to pass an entire object to the command to be processed. It's mainly used in scripts where an entire object must be passed to the command.
```yaml
Type: PublicFolderAdministrativeAceObject
Parameter Sets: Instance
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -150,9 +169,6 @@ Accept wildcard characters: False
```
### -Owner
-
-> Applicable: Exchange Server 2010
-
The Owner parameter specifies the owner of the public folder object. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -178,6 +194,7 @@ You can't use this parameter with the AccessRights or User parameters.
Type: SecurityPrincipalIdParameter
Parameter Sets: Owner
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -187,9 +204,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010
-
The User parameter specifies who gets the admin permissions on the public folder. You can specify the following types of users or groups:
- Mailbox users
@@ -213,8 +227,9 @@ You can't use this parameter with the Owner parameter.
```yaml
Type: SecurityPrincipalIdParameter
-Parameter Sets: Identity, Instance
+Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -223,10 +238,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -Confirm
+```yaml
+Type: SecurityPrincipalIdParameter
+Parameter Sets: Instance
+Aliases:
+Applicable: Exchange Server 2010
-> Applicable: Exchange Server 2010
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -Confirm
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -236,6 +261,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -245,15 +271,13 @@ Accept wildcard characters: False
```
### -Deny
-
-> Applicable: Exchange Server 2010
-
The Deny switch specifies that the permissions you're adding are Deny permissions. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity, Instance
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -263,15 +287,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -281,9 +303,6 @@ Accept wildcard characters: False
```
### -InheritanceType
-
-> Applicable: Exchange Server 2010
-
The InheritanceType parameter specifies how permissions are inherited. Valid values are:
- None
@@ -296,6 +315,7 @@ The InheritanceType parameter specifies how permissions are inherited. Valid val
Type: ActiveDirectorySecurityInheritance
Parameter Sets: Identity, Instance
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -305,9 +325,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -321,6 +338,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -330,15 +348,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md b/exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
rename to exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md
index e65cd078af..059bc10445 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-publicfolderclientpermission
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Add-PublicFolderClientPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-publicfolderclientpermission
-schema: 2.0.0
-title: Add-PublicFolderClientPermission
+ms.reviewer:
---
# Add-PublicFolderClientPermission
@@ -52,9 +51,6 @@ This example adds permission for the user Chris to create items in the public fo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\\PublicFolder.
You can omit the parameter label so that only the public folder name or GUID is supplied.
@@ -63,6 +59,7 @@ You can omit the parameter label so that only the public folder name or GUID is
Type: PublicFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -AccessRights
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AccessRights parameter specifies the rights that you want to add for the user on the public folder.
You can specify individual folder permissions or roles, which are combinations of permissions. You can specify multiple permissions and roles separated by commas.
@@ -108,6 +102,7 @@ In addition to access rights, you can create rights based upon roles, which incl
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -117,9 +112,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The User parameter specifies the user for whom rights are being added.
For the best results, we recommend using the following values:
@@ -131,6 +123,7 @@ For the best results, we recommend using the following values:
Type: PublicFolderUserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -140,9 +133,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -152,6 +142,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -161,9 +152,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -172,6 +160,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -181,9 +170,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
@@ -199,6 +185,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -208,15 +195,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md b/exchange/exchange-ps/exchange/Add-RecipientPermission.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md
rename to exchange/exchange-ps/exchange/Add-RecipientPermission.md
index 2a629a5a0d..06dfc9280a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md
+++ b/exchange/exchange-ps/exchange/Add-RecipientPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-recipientpermission
applicable: Exchange Online
+title: Add-RecipientPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-recipientpermission
-schema: 2.0.0
-title: Add-RecipientPermission
+ms.reviewer:
---
# Add-RecipientPermission
@@ -45,9 +44,6 @@ This example gives the user Ayla Kol SendAs permission for the mailbox Help Desk
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the target recipient. The user or group specified by the Trustee parameter receives SendAs permission on this recipient.
You can specify any type of recipient, for example:
@@ -71,6 +67,7 @@ You can use any value that uniquely identifies the recipient. For example:
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -80,15 +77,13 @@ Accept wildcard characters: False
```
### -AccessRights
-
-> Applicable: Exchange Online
-
The AccessRights parameter specifies the permission that you want to add for the trustee on the target recipient. The only valid value for this parameter is SendAs.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -98,9 +93,6 @@ Accept wildcard characters: False
```
### -Trustee
-
-> Applicable: Exchange Online
-
The Trustee parameter specifies the user or group that receives SendAs permission on the recipient specified by the Identity parameter. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -124,6 +116,7 @@ You can use any value that uniquely identifies the user or group. For example:
Type: SecurityPrincipalIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -133,9 +126,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -147,6 +137,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -156,15 +147,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md b/exchange/exchange-ps/exchange/Add-ResubmitRequest.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
rename to exchange/exchange-ps/exchange/Add-ResubmitRequest.md
index 05205b5d59..d1801a114d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
+++ b/exchange/exchange-ps/exchange/Add-ResubmitRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-resubmitrequest
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-ResubmitRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-resubmitrequest
-schema: 2.0.0
-title: Add-ResubmitRequest
+ms.reviewer:
---
# Add-ResubmitRequest
@@ -65,9 +64,6 @@ This example replays the redundant copies of messages delivered from 6:00 PM Jun
## PARAMETERS
### -EndTime
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The EndTime parameter specifies the delivery time of the latest messages that need to be resubmitted from Safety Net.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -78,6 +74,7 @@ The date and time specified by the EndTime parameter must be later than the date
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -87,9 +84,6 @@ Accept wildcard characters: False
```
### -StartTime
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The StartTime parameter specifies the delivery time of the oldest messages that need to be resubmitted from Safety Net.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -100,6 +94,7 @@ The date and time specified by the StartTime parameter must be earlier than the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -109,9 +104,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -121,6 +113,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,15 +123,13 @@ Accept wildcard characters: False
```
### -CorrelationId
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -148,9 +139,6 @@ Accept wildcard characters: False
```
### -Destination
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Destination parameter specifies the GUID of the destination mailbox database. To find the GUID of the mailbox database, run the command: `Get-MailboxDatabase -Server | Format-List Name,GUID`.
You can't use this parameter with the Recipient, ResubmitTo, or Sender parameters.
@@ -159,6 +147,7 @@ You can't use this parameter with the Recipient, ResubmitTo, or Sender parameter
Type: Guid
Parameter Sets: MDBResubmit
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -168,15 +157,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: String
Parameter Sets: ConditionalResubmit
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -186,9 +173,6 @@ Accept wildcard characters: False
```
### -Recipient
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Recipient parameter filters the messages to resubmit from Safety Net by the specified recipient's email address.
You can't use this parameter with the Destination parameter.
@@ -197,6 +181,7 @@ You can't use this parameter with the Destination parameter.
Type: String
Parameter Sets: ConditionalResubmit
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -206,15 +191,13 @@ Accept wildcard characters: False
```
### -ResubmitTo
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The ResubmitTo parameter specifies the recipient's email address for resubmitted messages that are identified by using the Recipient or Sender parameters.
```yaml
Type: String
Parameter Sets: ConditionalResubmit
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -224,9 +207,6 @@ Accept wildcard characters: False
```
### -Sender
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Sender parameter filters the messages to resubmit from Safety Net by the specified sender's email address.
You can't use this parameter with the Destination parameter.
@@ -235,6 +215,7 @@ You can't use this parameter with the Destination parameter.
Type: String
Parameter Sets: ConditionalResubmit
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -244,9 +225,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -260,6 +238,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -269,15 +248,13 @@ Accept wildcard characters: False
```
### -TestOnly
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -287,15 +264,13 @@ Accept wildcard characters: False
```
### -UnresponsivePrimaryServers
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The UnresponsivePrimaryServers parameter identifies the primary servers that should resubmit the messages from Safety Net as being unavailable so other servers can resubmit the messages. If the primary servers are unavailable, you can designate other servers that hold redundant copies of the messages in Safety Net to resubmit their copies of the messages. However, you must identify the unresponsive primary servers to the other servers using this parameter.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -305,15 +280,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md b/exchange/exchange-ps/exchange/Add-RoleGroupMember.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
rename to exchange/exchange-ps/exchange/Add-RoleGroupMember.md
index 4b06eb4397..5f64ff5636 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
+++ b/exchange/exchange-ps/exchange/Add-RoleGroupMember.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-rolegroupmember
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Add-RoleGroupMember
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-rolegroupmember
-schema: 2.0.0
-title: Add-RoleGroupMember
+ms.reviewer:
---
# Add-RoleGroupMember
@@ -74,15 +73,13 @@ This example adds the Training Assistants USG to the Training Administrators rol
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the role group to add a member to. If the role group name contains spaces, enclose the name in quotation marks (").
```yaml
Type: RoleGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: 1
@@ -92,9 +89,6 @@ Accept wildcard characters: False
```
### -Member
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Member parameter specifies who you want to add to the role group. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -119,6 +113,7 @@ You can use any value that uniquely identifies the user or group. For example:
Type: SecurityPrincipalIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -128,9 +123,6 @@ Accept wildcard characters: False
```
### -BypassSecurityGroupManagerCheck
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
If you aren't defined in the ManagedBy property of the group, you need to use this switch in commands that modify or delete the group. To use this switch, your account requires specific permissions based on the group type:
@@ -142,6 +134,7 @@ If you aren't defined in the ManagedBy property of the group, you need to use th
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -151,9 +144,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -163,6 +153,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -172,9 +163,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -183,6 +171,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -192,9 +181,6 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
@@ -203,6 +189,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md b/exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
rename to exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md
index 09faae554b..97858e26e8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/exchange/Add-ServerMonitoringOverride.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-servermonitoringoverride
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Add-ServerMonitoringOverride
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-servermonitoringoverride
-schema: 2.0.0
-title: Add-ServerMonitoringOverride
+ms.reviewer:
---
# Add-ServerMonitoringOverride
@@ -53,9 +52,6 @@ This example adds a server monitoring override that disables the responder Activ
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the monitoring item that you want to override. This parameter uses the syntax `HealthSet\MonitoringItemName[\TargetResource]`. Note that the values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityConfigDCServerReboot`, not `ad\activedirectoryconnectivityconfigdcserverreboot`.
You can use Get-ServerHealth to find the correct object for the monitoring item you want to override.
@@ -64,6 +60,7 @@ You can use Get-ServerHealth to find the correct object for the monitoring item
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -ApplyVersion
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ApplyVersion parameter specifies the version of Exchange that gets the override. If you update Exchange to a newer version (for example, you apply a Cumulative Update or Service Pack), the override is no longer applied to the server.
Valid input for this parameter is an Exchange version number in the format 15.01.xxxx.xxx.
@@ -86,6 +80,7 @@ You can't use this parameter with the Duration parameter.
Type: Version
Parameter Sets: ApplyVersion
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -ItemType
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ItemType parameter specifies the server item type for the property that you want to override. Valid value are:
- Probe
@@ -108,6 +100,7 @@ The ItemType parameter specifies the server item type for the property that you
Type: MonitoringItemTypeEnum
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -117,15 +110,13 @@ Accept wildcard characters: False
```
### -PropertyName
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PropertyName parameter specifies the server property that you want to override.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -135,15 +126,13 @@ Accept wildcard characters: False
```
### -PropertyValue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PropertyValue parameter specifies the new value for the server property that you want to override.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -153,9 +142,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to add the monitoring override. You can use any value that uniquely identifies the server. For example:
- Name
@@ -169,6 +155,7 @@ You can't use this parameter to configure other Edge Transport servers remotely.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -178,9 +165,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -190,6 +174,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -199,9 +184,6 @@ Accept wildcard characters: False
```
### -Duration
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Duration parameter specifies the length of time that the override is active.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -214,6 +196,7 @@ You can't use this parameter with the ApplyVersion parameter.
Type: EnhancedTimeSpan
Parameter Sets: Duration
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -223,15 +206,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md b/exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md
rename to exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md
index a4786f7f64..e58e810aba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md
+++ b/exchange/exchange-ps/exchange/Add-UnifiedGroupLinks.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-unifiedgrouplinks
applicable: Exchange Online, Exchange Online Protection
+title: Add-UnifiedGroupLinks
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-unifiedgrouplinks
-schema: 2.0.0
-title: Add-UnifiedGroupLinks
+ms.reviewer:
---
# Add-UnifiedGroupLinks
@@ -61,9 +60,6 @@ This example shows how to add bulk members to a Microsoft 365 Group. Mailboxes w
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the Microsoft 365 Group that you want to modify. You can use any value that uniquely identifies the Microsoft 365 Group. For example:
- Name
@@ -77,6 +73,7 @@ The Identity parameter specifies the Microsoft 365 Group that you want to modify
Type: UnifiedGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -86,9 +83,6 @@ Accept wildcard characters: False
```
### -Links
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Links parameter specifies the recipients to add to the Microsoft 365 Group. You specify whether these recipients are members, owners, or subscribers by using the LinkType parameter.
You can use any value that uniquely identifies the recipient. For example:
@@ -110,6 +104,7 @@ You must use this parameter with the LinkType parameter, which means the specifi
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -119,9 +114,6 @@ Accept wildcard characters: False
```
### -LinkType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The LinkType parameter specifies the recipient's role in the Microsoft 365 Group that you want to add. Valid values are:
- Members: Participate in conversations, create Teams channels, collaborate on files, and edit the connected SharePoint site.
@@ -136,6 +128,7 @@ You must use this parameter with the Links parameter.
Type: LinkType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -145,9 +138,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -157,6 +147,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -166,15 +157,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Add-VivaModuleFeaturePolicy.md
rename to exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md
index c3ca0dd9e1..340921a576 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-VivaModuleFeaturePolicy.md
+++ b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/add-vivamodulefeaturepolicy
applicable: Exchange Online
+title: Add-VivaModuleFeaturePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-vivamodulefeaturepolicy
-schema: 2.0.0
-title: Add-VivaModuleFeaturePolicy
+ms.reviewer:
---
# Add-VivaModuleFeaturePolicy
@@ -19,7 +19,7 @@ Use the Add-VivaModuleFeaturePolicy cmdlet to add a new access policy for a spec
- You can assign up to 10 policies per feature. An additional one policy per feature can be assigned to the entire tenant.
- Policies assigned to a specific user or group take priority over the policy assigned to the entire tenant when determining whether a feature is enabled. If a user has multiple policies assigned for a feature (directly as a user or member of a group), the most restrictive policy applies.
-- Some features only support policies that apply to the entire tenant, not specific users or groups. You can refer to supported policy scopes for a feature using the [Get-VivaModuleFeature](https://learn.microsoft.com/powershell/module/exchangepowershell/get-vivamodulefeature) cmdlet.
+- Some features only support policies that apply to the entire tenant, not specific users or groups. You can refer to supported policy scopes for a feature using the [Get-VivaModuleFeature](https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeature) cmdlet.
Some features include the option for user controls (user opt out). Refer to the feature documentation to see if user controls are available for the feature that you intend to set a policy for.
@@ -95,9 +95,6 @@ This example adds a policy for the ShowAISkills feature in Viva Skills. The poli
## PARAMETERS
### -FeatureId
-
-> Applicable: Exchange Online
-
The FeatureId parameter specifies the feature in the Viva module that you want to add the policy for.
To view details about the features in a Viva module that support feature access controls, use the Get-VivaModuleFeature cmdlet. The FeatureId value is returned in the output of the cmdlet.
@@ -106,6 +103,7 @@ To view details about the features in a Viva module that support feature access
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -115,9 +113,6 @@ Accept wildcard characters: False
```
### -IsFeatureEnabled
-
-> Applicable: Exchange Online
-
The IsFeatureEnabled parameter specifies whether or not the feature is enabled by the policy. Valid values are:
- $true: The feature is enabled by the policy.
@@ -127,6 +122,7 @@ The IsFeatureEnabled parameter specifies whether or not the feature is enabled b
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -136,15 +132,13 @@ Accept wildcard characters: False
```
### -ModuleId
-
-> Applicable: Exchange Online
-
The ModuleId parameter specifies the Viva module that you want to add the feature policy for.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -154,9 +148,6 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Online
-
The Name parameter specifies the name of the policy. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
Valid characters are English letters, numbers, commas, periods, and spaces.
@@ -165,6 +156,7 @@ Valid characters are English letters, numbers, commas, periods, and spaces.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -174,9 +166,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -188,6 +177,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -197,9 +187,6 @@ Accept wildcard characters: False
```
### -Everyone
-
-> Applicable: Exchange Online
-
The Everyone switch specifies that the policy applies to all users in the organization. You don't need to specify a value with this switch.
Don't use this switch with the GroupIds or UserIds parameters.
@@ -208,6 +195,7 @@ Don't use this switch with the GroupIds or UserIds parameters.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -217,9 +205,6 @@ Accept wildcard characters: False
```
### -GroupIds
-
-> Applicable: Exchange Online
-
The GroupIds parameter specifies the email addresses or security group object IDs (GUIDs) of groups that the updated policy applies to. Both [Mail-enabled and non-mail-enabled Microsoft Entra groups](https://docs.microsoft.com/graph/api/resources/groups-overview#group-types-in-azure-ad-and-microsoft-graph) are supported. You can enter multiple values separated by commas.
You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.).
@@ -232,6 +217,7 @@ To have the policy apply to all users in the organization, use the Everyone swit
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -241,9 +227,6 @@ Accept wildcard characters: False
```
### -IsUserControlEnabled
-
-> Applicable: Exchange Online
-
This parameter is available in version 3.3.0 or later of the module.
The IsUserControlEnabled parameter specifies whether user control is enabled by the policy. Valid values are:
@@ -257,6 +240,7 @@ Only features that allow admins to enable and disable user controls by policy ca
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -266,9 +250,6 @@ Accept wildcard characters: False
```
### -IsUserOptedInByDefault
-
-> Applicable: Exchange Online
-
This parameter is available in version 3.8.0-Preview2 or later of the module.
The IsUserOptedInByDefault parameter specifies whether users are opted in by default by the policy. Valid values are:
@@ -284,6 +265,7 @@ This parameter can be set only when the IsUserControlEnabled parameter is set to
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -293,15 +275,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -311,9 +291,6 @@ Accept wildcard characters: False
```
### -UserIds
-
-> Applicable: Exchange Online
-
The UserIds parameter specifies the user principal names (UPNs) of the users that the policy applies to. You can enter multiple values separated by commas.
You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.).
@@ -324,6 +301,7 @@ To have the policy apply to all users in the organization, use the Everyone swit
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -333,15 +311,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-VivaOrgInsightsDelegatedRole.md b/exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Add-VivaOrgInsightsDelegatedRole.md
rename to exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md
index 3a6604d12d..0bd5527745 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-VivaOrgInsightsDelegatedRole.md
+++ b/exchange/exchange-ps/exchange/Add-VivaOrgInsightsDelegatedRole.md
@@ -1,12 +1,12 @@
---
-author: chrisda
external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-vivaorginsightsdelegatedrole
-schema: 2.0.0
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/add-vivaorginsightsdelegatedrole
title: Add-VivaOrgInsightsDelegatedRole
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
---
# Add-VivaOrgInsightsDelegatedRole
@@ -47,9 +47,6 @@ This example adds the organization insights viewing capability of the specified
## PARAMETERS
### -Delegate
-
-> Applicable: Exchange Online
-
The Delegate parameter specifies the account that can view organizational insights like the leader (the account specified by the Delegator account).
A valid value for this parameter is the Microsoft Entra ObjectId value of the delegate account. Use the [Get-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/get-mguser) cmdlet in Microsoft Graph PowerShell to find this value.
@@ -58,6 +55,7 @@ A valid value for this parameter is the Microsoft Entra ObjectId value of the de
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -67,9 +65,6 @@ Accept wildcard characters: False
```
### -Delegator
-
-> Applicable: Exchange Online
-
The Delegator parameter specifies the account of the leader that can view organizational insights. This capability is delegated to the account specified by the Delegate parameter.
A valid value for this parameter is the ObjectID value of the delegator account. Use the [Get-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/get-mguser) cmdlet in Microsoft Graph PowerShell to find this value.
@@ -78,6 +73,7 @@ A valid value for this parameter is the ObjectID value of the delegator account.
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -87,15 +83,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Add-eDiscoveryCaseAdmin.md
rename to exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md
index c0127b3b6e..ddb6eb30ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-eDiscoveryCaseAdmin.md
+++ b/exchange/exchange-ps/exchange/Add-eDiscoveryCaseAdmin.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/add-ediscoverycaseadmin
applicable: Security & Compliance
+title: Add-eDiscoveryCaseAdmin
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/add-ediscoverycaseadmin
-schema: 2.0.0
-title: Add-eDiscoveryCaseAdmin
+ms.reviewer:
---
# Add-eDiscoveryCaseAdmin
@@ -47,9 +46,6 @@ This example adds an eDiscovery Administrator.
## PARAMETERS
### -User
-
-> Applicable: Security & Compliance
-
The User parameter specifies the user that you want to add to the list of eDiscovery Administrators. You can use any value that uniquely identifies the user. For example:
- Name
@@ -61,6 +57,7 @@ The User parameter specifies the user that you want to add to the list of eDisco
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -70,9 +67,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -82,6 +76,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -91,15 +86,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Check-PurviewConfig.md b/exchange/exchange-ps/exchange/Check-PurviewConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Check-PurviewConfig.md
rename to exchange/exchange-ps/exchange/Check-PurviewConfig.md
index 27692105c9..831bdea8cb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Check-PurviewConfig.md
+++ b/exchange/exchange-ps/exchange/Check-PurviewConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/check-purviewconfig
applicable: Security & Compliance
+title: Check-PurviewConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/check-purviewconfig
-schema: 2.0.0
-title: Check-PurviewConfig
+ms.reviewer:
---
# Check-PurviewConfig
@@ -90,9 +89,6 @@ This example runs the specified test cases. A UserPrincipalName value is require
## PARAMETERS
### -Component
-
-> Applicable: Security & Compliance
-
The Component parameter specifies the component to analyze in the test case. Valid values are:
- DLP
@@ -104,6 +100,7 @@ The Component parameter specifies the component to analyze in the test case. Val
Type: PurviewConfigComponent
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -113,9 +110,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -125,6 +119,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -134,9 +129,6 @@ Accept wildcard characters: False
```
### -DateTimeUTC
-
-> Applicable: Security & Compliance
-
The DateTimeUTC specifies the date-time of the test case in Coordinated Universal Time (UTC). For example, "2025-06-05 14:30:00".
This parameter is required for the following TestCases values:
@@ -148,6 +140,7 @@ This parameter is required for the following TestCases values:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -157,15 +150,13 @@ Accept wildcard characters: False
```
### -File
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 2
@@ -175,9 +166,6 @@ Accept wildcard characters: False
```
### -IncidentId
-
-> Applicable: Security & Compliance
-
The IncidentId parameter specifies the incident to analyze in the test case.
You can find a value for this parameter in audit log searches filtered by the operation DLPRuleMatch in the IncidentId property.
@@ -188,6 +176,7 @@ This parameter is required for the TestCases value DlpAlerts_FindAlertForActivit
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 3
@@ -197,15 +186,13 @@ Accept wildcard characters: False
```
### -ItemId
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 4
@@ -215,15 +202,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 5
@@ -233,9 +218,6 @@ Accept wildcard characters: False
```
### -RecordId
-
-> Applicable: Security & Compliance
-
The RuleName parameter specifies the record to analyze in the test case.
You can find a value for this parameter in Activity Explorer filtered by the activity type DLPRuleMatch in the RecordId property.
@@ -246,6 +228,7 @@ This parameter is optional with the TestCases value DlpAlerts_FindAlertForActivi
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 6
@@ -255,9 +238,6 @@ Accept wildcard characters: False
```
### -RuleName
-
-> Applicable: Security & Compliance
-
The RuleName parameter specifies the DLP rule to analyze in the test case.
This parameter is optional with the TestCases value DlpAlerts_CheckAlertsCreated.
@@ -266,6 +246,7 @@ This parameter is optional with the TestCases value DlpAlerts_CheckAlertsCreated
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 7
@@ -275,9 +256,6 @@ Accept wildcard characters: False
```
### -TestCases
-
-> Applicable: Security & Compliance
-
The TestCases parameter specifies the name of the test case to analyze. The available test cases and their required parameters are described in the following list:
- **Encryption_EvaluationDetails**: Validates email encryption evaluation details. No other parameters are required.
@@ -294,6 +272,7 @@ You can specify multiple values separated by commas.
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 8
@@ -303,9 +282,6 @@ Accept wildcard characters: False
```
### -Theme
-
-> Applicable: Security & Compliance
-
The Theme parameter filters specifies the them to analyze in the test case. Valid values are:
- EnabledEntities
@@ -316,6 +292,7 @@ The Theme parameter filters specifies the them to analyze in the test case. Vali
Type: PurviewConfigTheme
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 9
@@ -325,9 +302,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Security & Compliance
-
The UserPrincipalName parameter specifies the user account to analyze in the test case (for example, `sathya@contoso.onmicrosoft.com`).
- Required for the TestCases value MipLabels_EnabledEntities_ScopedLabels.
@@ -337,6 +311,7 @@ The UserPrincipalName parameter specifies the user account to analyze in the tes
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 10
@@ -346,15 +321,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -364,9 +337,6 @@ Accept wildcard characters: False
```
### -Workload
-
-> Applicable: Security & Compliance
-
The Workload parameter specifies the service workload. Value values are:
- EndpointDevices
@@ -381,6 +351,7 @@ This parameter is required for the TestCases value DLP_ScopedEntities.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 11
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md b/exchange/exchange-ps/exchange/Clean-MailboxDatabase.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md
rename to exchange/exchange-ps/exchange/Clean-MailboxDatabase.md
index feca97fac4..9e3829eb4e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md
+++ b/exchange/exchange-ps/exchange/Clean-MailboxDatabase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/clean-mailboxdatabase
applicable: Exchange Server 2010
+title: Clean-MailboxDatabase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/clean-mailboxdatabase
-schema: 2.0.0
-title: Clean-MailboxDatabase
+ms.reviewer:
---
# Clean-MailboxDatabase
@@ -50,9 +49,6 @@ This example cleans the mailbox database MBD01.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the mailbox database that you want to update. You can use any value that uniquely identifies the database. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the mailbox database that you want to update. Y
Type: DatabaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -84,6 +78,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -93,9 +88,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -104,6 +96,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -113,15 +106,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md b/exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
rename to exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md
index bf8643a66b..f729195ad5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/exchange/Clear-ActiveSyncDevice.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/clear-activesyncdevice
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Clear-ActiveSyncDevice
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/clear-activesyncdevice
-schema: 2.0.0
-title: Clear-ActiveSyncDevice
+ms.reviewer:
---
# Clear-ActiveSyncDevice
@@ -66,15 +65,13 @@ This example cancels a previously sent Clear-ActiveSyncDevice command request fo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the device that you want to reset.
```yaml
Type: ActiveSyncDeviceIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -84,15 +81,13 @@ Accept wildcard characters: False
```
### -Cancel
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Cancel switch specifies whether to issue a cancellation request for a pending remote device wipe. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -102,9 +97,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -116,6 +108,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -125,9 +118,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -136,6 +126,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -145,15 +136,13 @@ Accept wildcard characters: False
```
### -NotificationEmailAddresses
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The NotificationEmailAddresses parameter specifies the notification email address for the remote device wipe confirmation. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -163,15 +152,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md b/exchange/exchange-ps/exchange/Clear-MobileDevice.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
rename to exchange/exchange-ps/exchange/Clear-MobileDevice.md
index 0c9f6522b3..9a5eda7425 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
+++ b/exchange/exchange-ps/exchange/Clear-MobileDevice.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/clear-mobiledevice
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Clear-MobileDevice
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/clear-mobiledevice
-schema: 2.0.0
-title: Clear-MobileDevice
+ms.reviewer:
---
# Clear-MobileDevice
@@ -65,9 +64,6 @@ This example cancels a previously sent Clear-MobileDevice command request for th
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mobile device that you want to reset. You can use the following values that uniquely identifies the mobile device:
- Identity (`\ExchangeActiveSyncDevices\` for example, `CarlosM\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac`)
@@ -78,6 +74,7 @@ The Identity parameter specifies the mobile device that you want to reset. You c
Type: MobileDeviceIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -87,9 +84,6 @@ Accept wildcard characters: False
```
### -AccountOnly
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AccountOnly switch specifies whether to perform an account-only remote device wipe where only Exchange mailbox data is removed from the device. You don't need to specify a value with this switch.
You don't need to use this switch for the DeviceType value Outlook, because an account-only remote device wipe is the only type of wipe that's used on Outlook devices.
@@ -98,6 +92,7 @@ You don't need to use this switch for the DeviceType value Outlook, because an a
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -107,15 +102,13 @@ Accept wildcard characters: False
```
### -Cancel
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Cancel switch specifies whether to issue a cancellation request for a pending remote device wipe. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -125,9 +118,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -139,6 +129,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -148,9 +139,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -159,6 +147,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -168,15 +157,13 @@ Accept wildcard characters: False
```
### -NotificationEmailAddresses
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The NotificationEmailAddresses parameter specifies the notification email address for the remote device wipe confirmation. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -186,15 +173,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md b/exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
rename to exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md
index 8a3a2a9579..0cfbdb03d1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
+++ b/exchange/exchange-ps/exchange/Clear-TextMessagingAccount.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/clear-textmessagingaccount
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Clear-TextMessagingAccount
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/clear-textmessagingaccount
-schema: 2.0.0
-title: Clear-TextMessagingAccount
+ms.reviewer:
---
# Clear-TextMessagingAccount
@@ -47,9 +46,6 @@ This example clears the text messaging account settings and notification setting
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the target mailbox. You can any value that uniquely identifies the mailbox. For example:
- Name
@@ -67,6 +63,7 @@ The Identity parameter specifies the target mailbox. You can any value that uniq
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -76,9 +73,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -88,6 +82,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -97,9 +92,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -108,6 +100,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -117,9 +110,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -131,6 +121,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -140,15 +131,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md b/exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
rename to exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md
index 1eb6f7ca40..c536c48908 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
+++ b/exchange/exchange-ps/exchange/Compare-TextMessagingVerificationCode.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/compare-textmessagingverificationcode
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Compare-TextMessagingVerificationCode
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/compare-textmessagingverificationcode
-schema: 2.0.0
-title: Compare-TextMessagingVerificationCode
+ms.reviewer:
---
# Compare-TextMessagingVerificationCode
@@ -62,9 +61,6 @@ This example compares the verification code 111555 to the code sent to Tony Smit
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox where you are trying to enable text messaging notifications. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -82,6 +78,7 @@ The Identity parameter specifies the mailbox where you are trying to enable text
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -91,15 +88,13 @@ Accept wildcard characters: False
```
### -VerificationCode
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The VerificationCode parameter contains the verification code that the user specified.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -109,9 +104,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -121,6 +113,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -130,9 +123,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -141,6 +131,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -150,15 +141,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md b/exchange/exchange-ps/exchange/Complete-MigrationBatch.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
rename to exchange/exchange-ps/exchange/Complete-MigrationBatch.md
index a47891ea77..922eeca5b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
+++ b/exchange/exchange-ps/exchange/Complete-MigrationBatch.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/complete-migrationbatch
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Complete-MigrationBatch
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/complete-migrationbatch
-schema: 2.0.0
-title: Complete-MigrationBatch
+ms.reviewer:
---
# Complete-MigrationBatch
@@ -60,15 +59,13 @@ This example completes the migration batch LocalMove1 and sends a notification e
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name of the migration batch that you want to complete. The value for this parameter is specified by the Name parameter for the New-MigrationBatch cmdlet. Use the Get-MigrationBatch cmdlet to determine the value of this parameter for the migration batch.
```yaml
Type: MigrationBatchIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -CompletePublicFolderMigrationWithDataLoss
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -89,6 +83,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -98,9 +93,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -112,6 +104,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -121,9 +114,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -132,6 +122,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,9 +132,6 @@ Accept wildcard characters: False
```
### -NotificationEmails
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The NotificationEmails parameter specifies one or more email addresses that status reports are sent to after the migration batch is completed. You can specify multiple email addresses separated by commas.
@@ -154,6 +142,7 @@ If you don't use this parameter, the final status report is sent to the administ
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -163,9 +152,6 @@ Accept wildcard characters: False
```
### -Partition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -174,6 +160,7 @@ This parameter is reserved for internal Microsoft use.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -183,15 +170,13 @@ Accept wildcard characters: False
```
### -SyncAndComplete
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SyncAndComplete switch specifies whether to trigger a synchronization immediately followed by a completion of the migration batch if the synchronization was successful. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -201,15 +186,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md b/exchange/exchange-ps/exchange/Connect-ExchangeOnline.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md
rename to exchange/exchange-ps/exchange/Connect-ExchangeOnline.md
index 04e48a420d..241205492f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md
+++ b/exchange/exchange-ps/exchange/Connect-ExchangeOnline.md
@@ -1,13 +1,13 @@
---
+external help file: ExchangeOnlineManagement-help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/connect-exchangeonline
applicable: Exchange Online
+title: Connect-ExchangeOnline
+schema: 2.0.0
author: chrisda
-external help file: ExchangeOnlineManagement-help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/connect-exchangeonline
-schema: 2.0.0
-title: Connect-ExchangeOnline
+ms.reviewer:
---
# Connect-ExchangeOnline
@@ -17,7 +17,7 @@ This cmdlet is available only in the Exchange Online PowerShell module. For more
Use the Connect-ExchangeOnline cmdlet in the Exchange Online PowerShell module to use modern authentication to connect to Exchange Online PowerShell or Exchange Online Protection PowerShell for cloud protection of on-premises email environments. This cmdlet works for accounts with or without multi-factor authentication (MFA).
-To connect to Security & Compliance PowerShell, use the [Connect-IPPSSession](https://learn.microsoft.com/powershell/module/exchangepowershell/connect-ippssession) cmdlet.
+To connect to Security & Compliance PowerShell, use the [Connect-IPPSSession](https://learn.microsoft.com/powershell/module/exchange/connect-ippssession) cmdlet.
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
@@ -111,9 +111,6 @@ In PowerShell 7.0.3 or later using version 2.0.4 or later of the module, this ex
## PARAMETERS
### -ConnectionUri
-
-> Applicable: Exchange Online
-
**Note**: If you use the ExchangeEnvironmentName parameter, you don't need to use the AzureADAuthorizationEndpointUri or ConnectionUri parameters.
The ConnectionUri parameter specifies the connection endpoint for the PowerShell session. The following Exchange Online PowerShell environments and related values are supported:
@@ -128,6 +125,7 @@ The ConnectionUri parameter specifies the connection endpoint for the PowerShell
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -137,9 +135,6 @@ Accept wildcard characters: False
```
### -AzureADAuthorizationEndpointUri
-
-> Applicable: Exchange Online
-
**Note**: If you use the ExchangeEnvironmentName parameter, you don't need to use the AzureADAuthorizationEndpointUri or ConnectionUri parameters.
The AzureADAuthorizationEndpointUri parameter specifies the Microsoft Entra Authorization endpoint that can issue OAuth2 access tokens. The following Exchange Online PowerShell environments and related values are supported:
@@ -156,6 +151,7 @@ If you use the UserPrincipalName parameter, you don't need to use the AzureADAut
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -165,9 +161,6 @@ Accept wildcard characters: False
```
### -ExchangeEnvironmentName
-
-> Applicable: Exchange Online
-
The ExchangeEnvironmentName specifies the Exchange Online environment and eliminates the need to use the AzureADAuthorizationEndpointUri and ConnectionUri parameters. The following Exchange Online PowerShell environments are supported:
- Microsoft 365 or Microsoft 365 GCC: Don't use this parameter. The required value is `O365Default`, but that's also the default value, so you don't need to use this parameter.
@@ -180,6 +173,7 @@ The ExchangeEnvironmentName specifies the Exchange Online environment and elimin
Type: ExchangeEnvironment
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 2
@@ -189,9 +183,6 @@ Accept wildcard characters: False
```
### -PSSessionOption
-
-> Applicable: Exchange Online
-
**Note**: This parameter doesn't work in REST API connections.
The PSSessionOption parameter specifies the PowerShell session options to use in your connection to Exchange Online. This parameter works only if you also use the UseRPSSession switch in the same command.
@@ -202,6 +193,7 @@ Store the output of the [New-PSSessionOption](https://learn.microsoft.com/powers
Type: PSSessionOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 3
@@ -211,9 +203,6 @@ Accept wildcard characters: False
```
### -DelegatedOrganization
-
-> Applicable: Exchange Online
-
The DelegatedOrganization parameter specifies the customer organization that you want to manage. A valid value for this parameter is the primary .onmicrosoft.com domain or tenant ID of the customer organization.
This parameter works only if the customer organization has agreed to your delegated management via the CSP program.
@@ -224,6 +213,7 @@ After you successfully authenticate, the cmdlets in this session are mapped to t
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 4
@@ -233,9 +223,6 @@ Accept wildcard characters: False
```
### -Prefix
-
-> Applicable: Exchange Online
-
The Prefix parameter specifies a text value to add to the names of Exchange Online PowerShell cmdlets when you connect. For example, Get-InboundConnector becomes Get-ContosoInboundConnector when you use the value Contoso for this parameter.
- The Prefix value can't contain spaces or special characters like underscores or asterisks.
@@ -246,6 +233,7 @@ The Prefix parameter specifies a text value to add to the names of Exchange Onli
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 5
@@ -255,15 +243,13 @@ Accept wildcard characters: False
```
### -CommandName
-
-> Applicable: Exchange Online
-
The CommandName parameter specifies the comma separated list of commands to import into the session. Use this parameter for applications or scripts that use a specific set of cmdlets. Reducing the number of cmdlets in the session helps improve performance and reduces the memory footprint of the application or script.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 6
@@ -273,15 +259,13 @@ Accept wildcard characters: False
```
### -FormatTypeName
-
-> Applicable: Exchange Online
-
The FormatTypeName parameter specifies the output format of the cmdlet.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 7
@@ -291,9 +275,6 @@ Accept wildcard characters: False
```
### -AccessToken
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.1.0 or later of the module.
The AccessToken parameter specifies the OAuth JSON Web Token (JWT) that's used to connect to Exchange Online.
@@ -304,6 +285,7 @@ Depending on the type of access token, you need to use this parameter with the O
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -313,9 +295,6 @@ Accept wildcard characters: False
```
### -AppId
-
-> Applicable: Exchange Online
-
The AppId parameter specifies the application ID of the service principal that's used in certificate based authentication (CBA). A valid value is the GUID of the application ID (service principal). For example, `36ee4c6c-0812-40a2-b820-b22ebd02bce3`.
For more information, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba).
@@ -324,6 +303,7 @@ For more information, see [App-only authentication for unattended scripts in the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -333,15 +313,13 @@ Accept wildcard characters: False
```
### -BypassMailboxAnchoring
-
-> Applicable: Exchange Online
-
The BypassMailboxAnchoring switch bypasses the use of the mailbox anchoring hint. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -351,9 +329,6 @@ Accept wildcard characters: False
```
### -Certificate
-
-> Applicable: Exchange Online
-
The Certificate parameter specifies the certificate that's used for certificate-based authentication (CBA). A valid value is the X509Certificate2 object value of the certificate.
Don't use this parameter with the CertificateFilePath or CertificateThumbprint parameters.
@@ -364,6 +339,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: X509Certificate2
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -373,9 +349,6 @@ Accept wildcard characters: False
```
### -CertificateFilePath
-
-> Applicable: Exchange Online
-
The CertificateFilePath parameter specifies the certificate that's used for CBA. A valid value is the complete public path to the certificate file. Use the CertificatePassword parameter with this parameter.
Don't use this parameter with the Certificate or CertificateThumbprint parameters.
@@ -386,6 +359,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -395,9 +369,6 @@ Accept wildcard characters: False
```
### -CertificatePassword
-
-> Applicable: Exchange Online
-
The CertificatePassword parameter specifies the password that's required to open the certificate file when you use the CertificateFilePath parameter to identify the certificate that's used for CBA.
You can use the following methods as a value for this parameter:
@@ -414,6 +385,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: SecureString
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -423,9 +395,6 @@ Accept wildcard characters: False
```
### -CertificateThumbprint
-
-> Applicable: Exchange Online
-
The CertificateThumbprint parameter specifies the certificate that's used for CBA. A valid value is the thumbprint value of the certificate. For example, `83213AEAC56D61C97AEE5C1528F4AC5EBA7321C1`.
Don't use this parameter with the Certificate or CertificateFilePath parameters.
@@ -438,6 +407,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -447,9 +417,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Online
-
The Credential parameter specifies the username and password that's used to connect to Exchange Online PowerShell. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. Don't use this parameter for accounts that use multi-factor authentication (MFA).
Before you run the Connect-ExchangeOnline command, store the username and password in a variable (for example, `$UserCredential = Get-Credential`). Then, use the variable name (`$UserCredential`) for this parameter.
@@ -462,6 +429,7 @@ To specify the password for a certificate file, don't use this parameter; use th
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -471,9 +439,6 @@ Accept wildcard characters: False
```
### -Device
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 2.0.4 or later of the module, and only in PowerShell 7.
The Device switch is typically used on computers without web browsers. You don't need to specify a value with this switch.
@@ -486,6 +451,7 @@ If your login was successful, the PowerShell connection continues.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -495,9 +461,6 @@ Accept wildcard characters: False
```
### -DisableWAM
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.7.2-Preview1 or later of the module.
The DisableWAM switch disables Web Account Manager (WAM). You don't need to specify a value with this switch.
@@ -508,6 +471,7 @@ Starting in version 3.7.0, WAM is enabled by default when connecting to Exchange
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -517,15 +481,13 @@ Accept wildcard characters: False
```
### -EnableErrorReporting
-
-> Applicable: Exchange Online
-
The EnableErrorReporting switch specifies whether to enable error reporting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -535,9 +497,6 @@ Accept wildcard characters: False
```
### -InlineCredential
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 2.0.4 or later of the module, and only in PowerShell 7.
The InlineCredential switch specifies whether to pass credentials directly in the Windows PowerShell window. You don't need to specify a value with this switch.
@@ -550,6 +509,7 @@ This switch does not work with accounts that use MFA.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -559,9 +519,6 @@ Accept wildcard characters: False
```
### -LoadCmdletHelp
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.7.0-Preview1 or later of the module.
The LoadCmdletHelp switch downloads cmdlet help files for the Get-Help cmdlet in REST API connections. You don't need to specify a value with this switch.
@@ -574,6 +531,7 @@ Starting in v3.7.0-Preview1, help files for the command line aren't downloaded b
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -583,9 +541,6 @@ Accept wildcard characters: False
```
### -LogDirectoryPath
-
-> Applicable: Exchange Online
-
The LogDirectoryPath parameter specifies the location of the log files. The default location is `%TMP%\EXOCmdletTelemetry\EXOCmdletTelemetry-yyyymmdd-hhmmss.csv`.
If you specify a custom location and filename that contains spaces, enclose the value in quotation marks (").
@@ -594,6 +549,7 @@ If you specify a custom location and filename that contains spaces, enclose the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -603,15 +559,13 @@ Accept wildcard characters: False
```
### -LogLevel
-
-> Applicable: Exchange Online
-
The LogLevel parameter specifies the logging level. Valid values are Default and All.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -621,9 +575,6 @@ Accept wildcard characters: False
```
### -ManagedIdentity
-
-> Applicable: Exchange Online
-
The ManagedIdentity switch specifies that you're using managed identity to connect. You don't need to specify a value with this switch.
Managed identity connections are currently supported for the following types of Azure resources:
@@ -643,6 +594,7 @@ For more information about connecting with managed identity, see [Use Azure mana
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -652,9 +604,6 @@ Accept wildcard characters: False
```
### -ManagedIdentityAccountId
-
-> Applicable: Exchange Online
-
The ManagedIdentityAccountId parameter specifies the user-assigned managed identity that you're using to connect. A valid value for this parameter is the application ID (GUID) of the service principal that corresponds to the user-assigned managed identity in Azure.
You must use this parameter with the Organization parameter and the ManagedIdentity switch.
@@ -665,6 +614,7 @@ For more information about connecting with managed identity, see [Use Azure mana
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -674,9 +624,6 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Exchange Online
-
The Organization parameter specifies the organization when you connect using CBA or managed identity. A valid value for this parameter is the primary .onmicrosoft.com domain or tenant ID of the organization.
For more information about connecting with CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba).
@@ -687,6 +634,7 @@ For more information about connecting with managed identity, see [Use Azure mana
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -696,15 +644,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 1000. The default value is 1000.
```yaml
Type: UInt32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -714,9 +660,6 @@ Accept wildcard characters: False
```
### -ShowBanner
-
-> Applicable: Exchange Online
-
The ShowBanner switch shows or hides the banner message that's displayed when you run Connect-ExchangeOnline. You don't need to specify a value with this switch.
- To show the banner, you don't need to use this switch (the banner is displayed by default).
@@ -726,6 +669,7 @@ The ShowBanner switch shows or hides the banner message that's displayed when yo
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -735,9 +679,6 @@ Accept wildcard characters: False
```
### -ShowProgress
-
-> Applicable: Exchange Online
-
The ShowProgress parameter specifies whether to show or hide the progress bar of imported cmdlets when you connect. Valid values are:
- $true: The progress bar is displayed. This is the default value.
@@ -747,6 +688,7 @@ The ShowProgress parameter specifies whether to show or hide the progress bar of
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -756,9 +698,6 @@ Accept wildcard characters: False
```
### -SigningCertificate
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.2.0 or later of the module.
The SigningCertificate parameter specifies the client certificate that's used to sign the format files (\*.Format.ps1xml) or script module files (.psm1) in the temporary module that Connect-ExchangeOnline creates.
@@ -771,6 +710,7 @@ To find the certificate, use the Get-PfxCertificate cmdlet in the Microsoft.Powe
Type: X509Certificate2
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -780,9 +720,6 @@ Accept wildcard characters: False
```
### -SkipLoadingCmdletHelp
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.3.0 or later of the module.
In version 3.7.0-Preview1 or later, this parameter is replaced by the LoadCmdletHelp parameter. The SkipLoadingCmdletHelp parameter is no longer required and no longer does anything, because cmdlet help files are no longer downloaded by default. Eventually, this parameter will be retired, so remove it from any scripts.
@@ -797,6 +734,7 @@ This switch doesn't work with the UseRPSSession switch.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -806,9 +744,6 @@ Accept wildcard characters: False
```
### -SkipLoadingFormatData
-
-> Applicable: Exchange Online
-
The SkipLoadingFormatData switch prevents downloading the format data for REST API connections. You don't need to specify a value with this switch.
When you use this switch, the output of any Exchange cmdlet will be unformatted.
@@ -821,6 +756,7 @@ This switch doesn't work with the UseRPSSession switch.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -830,9 +766,6 @@ Accept wildcard characters: False
```
### -TrackPerformance
-
-> Applicable: Exchange Online
-
The TrackPerformance parameter measures additional events (for example, CPU load and memory consumed). Valid values are:
- $true: Performance tracking is enabled.
@@ -844,6 +777,7 @@ This parameter works only when logging is enabled.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -853,9 +787,6 @@ Accept wildcard characters: False
```
### -UseMultithreading
-
-> Applicable: Exchange Online
-
The UseMultithreading parameter specifies whether to disable or enable multi-threading in the Exchange Online PowerShell module. Valid values are:
- $true: Enable multi-threading. This is the default value.
@@ -865,6 +796,7 @@ The UseMultithreading parameter specifies whether to disable or enable multi-thr
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -874,9 +806,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter specifies the account that you want to use to connect (for example, `navin@contoso.onmicrosoft.com`). Using this parameter allows you to skip entering a username in the modern authentication credentials prompt (you're prompted to enter a password).
If you use the UserPrincipalName parameter, you don't need to use the AzureADAuthorizationEndpointUri parameter for MFA or federated users in environments that normally require it (UserPrincipalName or AzureADAuthorizationEndpointUri is required; OK to use both).
@@ -885,6 +814,7 @@ If you use the UserPrincipalName parameter, you don't need to use the AzureADAut
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -894,9 +824,6 @@ Accept wildcard characters: False
```
### -UseRPSSession
-
-> Applicable: Exchange Online
-
**Note**: Remote PowerShell connections to Exchange Online PowerShell are deprecated. For more information, see [Deprecation of Remote PowerShell in Exchange Online](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-in-exchange-online-re-enabling/ba-p/3779692).
The UseRPSSession switch allows you to connect to Exchange Online PowerShell using traditional remote PowerShell access to all cmdlets. You don't need to specify a value with this switch.
@@ -909,6 +836,7 @@ If you don't use this switch, REST API mode is used for the connection, so Basic
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-IPPSSession.md b/exchange/exchange-ps/exchange/Connect-IPPSSession.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Connect-IPPSSession.md
rename to exchange/exchange-ps/exchange/Connect-IPPSSession.md
index 1fdc9b65e9..a260cad194 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Connect-IPPSSession.md
+++ b/exchange/exchange-ps/exchange/Connect-IPPSSession.md
@@ -1,13 +1,13 @@
---
+external help file: ExchangeOnlineManagement-help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/connect-ippssession
applicable: Exchange Online
+title: Connect-IPPSSession
+schema: 2.0.0
author: chrisda
-external help file: ExchangeOnlineManagement-help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/connect-ippssession
-schema: 2.0.0
-title: Connect-IPPSSession
+ms.reviewer:
---
# Connect-IPPSSession
@@ -82,9 +82,6 @@ This example connects to Security & Compliance PowerShell in an unattended scrip
## PARAMETERS
### -ConnectionUri
-
-> Applicable: Exchange Online
-
The ConnectionUri parameter specifies the connection endpoint for the PowerShell session. The following PowerShell environments and related values are supported:
- Security & Compliance PowerShell in Microsoft 365 or Microsoft 365 GCC: Don't use this parameter. The required value is `https://ps.compliance.protection.outlook.com/powershell-liveid/`, but that's also the default value, so you don't need to use this parameter.
@@ -96,6 +93,7 @@ The ConnectionUri parameter specifies the connection endpoint for the PowerShell
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -105,9 +103,6 @@ Accept wildcard characters: False
```
### -AzureADAuthorizationEndpointUri
-
-> Applicable: Exchange Online
-
The AzureADAuthorizationEndpointUri parameter specifies the Microsoft Entra Authorization endpoint that can issue OAuth2 access tokens. The following PowerShell environments and related values are supported:
- Security & Compliance PowerShell in Microsoft 365 or Microsoft 365 GCC: Don't use this parameter. The required value is `https://login.microsoftonline.com/common`, but that's also the default value, so you don't need to use this parameter.
@@ -120,6 +115,7 @@ If you use the UserPrincipalName parameter, you don't need to use the AzureADAut
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -129,9 +125,6 @@ Accept wildcard characters: False
```
### -DelegatedOrganization
-
-> Applicable: Exchange Online
-
The DelegatedOrganization parameter specifies the customer organization that you want to manage (for example, contosoelectronics.onmicrosoft.com). This parameter works only if the customer organization has agreed to your delegated management via the CSP program.
After you successfully authenticate, the cmdlets in this session are mapped to the customer organization, and all operations in this session are done on the customer organization.
@@ -145,6 +138,7 @@ After you successfully authenticate, the cmdlets in this session are mapped to t
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 2
@@ -154,9 +148,6 @@ Accept wildcard characters: False
```
### -PSSessionOption
-
-> Applicable: Exchange Online
-
**Note**: This parameter doesn't work in REST API connections.
The PSSessionOption parameter specifies the remote PowerShell session options to use in your connection to Security & Compliance PowerShell. This parameter works only if you also use the UseRPSSession switch in the same command.
@@ -167,6 +158,7 @@ Store the output of the [New-PSSessionOption](https://learn.microsoft.com/powers
Type: PSSessionOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 3
@@ -176,9 +168,6 @@ Accept wildcard characters: False
```
### -Prefix
-
-> Applicable: Exchange Online
-
The Prefix parameter specifies a text value to add to the names of Security & Compliance PowerShell cmdlets when you connect. For example, Get-ComplianceCase becomes Get-ContosoComplianceCase when you use the value Contoso for this parameter.
- The Prefix value can't contain spaces or special characters like underscores or asterisks.
@@ -189,6 +178,7 @@ The Prefix parameter specifies a text value to add to the names of Security & Co
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 4
@@ -198,15 +188,13 @@ Accept wildcard characters: False
```
### -CommandName
-
-> Applicable: Exchange Online
-
The CommandName parameter specifies the comma separated list of commands to import into the session. Use this parameter for applications or scripts that use a specific set of cmdlets. Reducing the number of cmdlets in the session helps improve performance and reduces the memory footprint of the application or script.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 5
@@ -216,15 +204,13 @@ Accept wildcard characters: False
```
### -FormatTypeName
-
-> Applicable: Exchange Online
-
The FormatTypeName parameter specifies the output format of the cmdlet.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 6
@@ -234,9 +220,6 @@ Accept wildcard characters: False
```
### -AccessToken
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.8.0-Preview1 or later of the module.
The AccessToken parameter specifies the OAuth JSON Web Token (JWT) that's used to connect to Security and Compliance PowerShell.
@@ -247,6 +230,7 @@ Depending on the type of access token, you need to use this parameter with the O
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -256,9 +240,6 @@ Accept wildcard characters: False
```
### -AppId
-
-> Applicable: Exchange Online
-
The AppId parameter specifies the application ID of the service principal that's used in certificate based authentication (CBA). A valid value is the GUID of the application ID (service principal). For example, `36ee4c6c-0812-40a2-b820-b22ebd02bce3`.
For more information, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba).
@@ -267,6 +248,7 @@ For more information, see [App-only authentication for unattended scripts in the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -276,15 +258,13 @@ Accept wildcard characters: False
```
### -BypassMailboxAnchoring
-
-> Applicable: Exchange Online
-
The BypassMailboxAnchoring switch bypasses the use of the mailbox anchoring hint. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -294,9 +274,6 @@ Accept wildcard characters: False
```
### -Certificate
-
-> Applicable: Exchange Online
-
The Certificate parameter specifies the certificate that's used for certificate-based authentication (CBA). A valid value is the X509Certificate2 object value of the certificate.
Don't use this parameter with the CertificateFilePath or CertificateThumbprint parameters.
@@ -307,6 +284,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: X509Certificate2
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -316,9 +294,6 @@ Accept wildcard characters: False
```
### -CertificateFilePath
-
-> Applicable: Exchange Online
-
The CertificateFilePath parameter specifies the certificate that's used for CBA. A valid value is the complete public path to the certificate file. Use the CertificatePassword parameter with this parameter.
Don't use this parameter with the Certificate or CertificateThumbprint parameters.
@@ -329,6 +304,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -338,9 +314,6 @@ Accept wildcard characters: False
```
### -CertificatePassword
-
-> Applicable: Exchange Online
-
The CertificatePassword parameter specifies the password that's required to open the certificate file when you use the CertificateFilePath parameter to identify the certificate that's used for CBA.
You can use the following methods as a value for this parameter:
@@ -357,6 +330,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: SecureString
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -366,9 +340,6 @@ Accept wildcard characters: False
```
### -CertificateThumbprint
-
-> Applicable: Exchange Online
-
The CertificateThumbprint parameter specifies the certificate that's used for CBA. A valid value is the thumbprint value of the certificate. For example, `83213AEAC56D61C97AEE5C1528F4AC5EBA7321C1`.
Don't use this parameter with the Certificate or CertificateFilePath parameters.
@@ -381,6 +352,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -390,9 +362,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Online
-
The Credential parameter specifies the username and password that's used to connect to Exchange Online PowerShell. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions. Don't use this parameter for accounts that use multi-factor authentication (MFA).
Before you run the Connect-IPPSSession command, store the username and password in a variable (for example, `$UserCredential = Get-Credential`). Then, use the variable name (`$UserCredential`) for this parameter.
@@ -403,6 +372,7 @@ After the Connect-IPPSSession command is complete, the password key in the varia
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -412,9 +382,6 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Exchange Online
-
The Organization parameter specifies the organization when you connect using CBA. You must use the primary .onmicrosoft.com domain of the organization for the value of this parameter.
For more information about CBA, see [App-only authentication for unattended scripts in the Exchange Online PowerShell module](https://aka.ms/exo-cba).
@@ -423,6 +390,7 @@ For more information about CBA, see [App-only authentication for unattended scri
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -432,9 +400,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter specifies the account that you want to use to connect (for example, navin@contoso.onmicrosoft.com). Using this parameter allows you to skip entering a username in the modern authentication credentials prompt (you're prompted to enter a password).
If you use the UserPrincipalName parameter, you don't need to use the AzureADAuthorizationEndpointUri parameter for MFA or federated users in environments that normally require it (UserPrincipalName or AzureADAuthorizationEndpointUri is required; OK to use both).
@@ -443,6 +408,7 @@ If you use the UserPrincipalName parameter, you don't need to use the AzureADAut
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -452,9 +418,6 @@ Accept wildcard characters: False
```
### -UseRPSSession
-
-> Applicable: Exchange Online
-
This parameter is available in version 3.2.0 or later of the module.
**Note**: Remote PowerShell connections to Security & Compliance are deprecated. For more information, see [Deprecation of Remote PowerShell in Security and Compliance PowerShell](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432).
@@ -469,6 +432,7 @@ If you don't use this switch, Basic authentication in WinRM is not required.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md b/exchange/exchange-ps/exchange/Connect-Mailbox.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
rename to exchange/exchange-ps/exchange/Connect-Mailbox.md
index cb4c8cfa49..87bea6279a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
+++ b/exchange/exchange-ps/exchange/Connect-Mailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/connect-mailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Connect-Mailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/connect-mailbox
-schema: 2.0.0
-title: Connect-Mailbox
+ms.reviewer:
---
# Connect-Mailbox
@@ -167,9 +166,6 @@ This example connects a room mailbox.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox that you want to connect to a user account. This parameter doesn't specify an Active Directory object. You can use the following values to identify the mailbox:
- Display name
@@ -182,6 +178,7 @@ You use this parameter with the Database parameter to specify the mailbox that y
Type: StoreMailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -191,9 +188,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Database parameter specifies the Exchange database that contains the mailbox that you want to connect. You can use any value that uniquely identifies the database. For example:
- Name
@@ -206,6 +200,7 @@ You use this parameter with the Identity parameter to specify the mailbox that y
Type: DatabaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 2
@@ -215,9 +210,6 @@ Accept wildcard characters: False
```
### -Equipment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Equipment switch is required to connect equipment mailboxes. You don't need to specify a value with this switch.
Equipment mailboxes are resource mailboxes that aren't associated with a specific location (for example, vehicles or computers).
@@ -226,6 +218,7 @@ Equipment mailboxes are resource mailboxes that aren't associated with a specifi
Type: SwitchParameter
Parameter Sets: Equipment
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -235,9 +228,6 @@ Accept wildcard characters: False
```
### -LinkedDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LinkedDomainController parameter specifies the domain controller in the forest where the user account resides, if the mailbox is a linked mailbox. The domain controller in the forest where the user account resides is used to get security information for the account specified by the LinkedMasterAccount parameter. Use the fully qualified domain name (FQDN) of the domain controller that you want to use as the value for this parameter.
This parameter is required only if you're connecting a linked mailbox.
@@ -246,6 +236,7 @@ This parameter is required only if you're connecting a linked mailbox.
Type: Fqdn
Parameter Sets: Linked
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -255,9 +246,6 @@ Accept wildcard characters: False
```
### -LinkedMasterAccount
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LinkedMasterAccount parameter specifies the master account in the forest where the user account resides, if this mailbox is a linked mailbox. The master account is the account that the mailbox is linked to. The master account grants access to the mailbox. This parameter is required only if you're creating a linked mailbox. You can use any value that uniquely identifies the master account. For example:
- Name
@@ -271,6 +259,7 @@ This parameter is required only if you're connecting a linked mailbox.
Type: UserIdParameter
Parameter Sets: Linked
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -280,9 +269,6 @@ Accept wildcard characters: False
```
### -Room
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Room switch is required to connect room mailboxes. You don't need to specify a value with this switch.
Room mailboxes are resource mailboxes that are associated with a specific location (for example, conference rooms).
@@ -291,6 +277,7 @@ Room mailboxes are resource mailboxes that are associated with a specific locati
Type: SwitchParameter
Parameter Sets: Room
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -300,9 +287,6 @@ Accept wildcard characters: False
```
### -Shared
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Shared switch is required to connect shared mailboxes. You don't need to specify a value with this switch.
A shared mailbox is a mailbox where multiple users can log on to access the mailbox contents. This mailbox isn't associated with any of the users that can log on. It's associated with a disabled user account.
@@ -311,6 +295,7 @@ A shared mailbox is a mailbox where multiple users can log on to access the mail
Type: SwitchParameter
Parameter Sets: Shared
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -320,9 +305,6 @@ Accept wildcard characters: False
```
### -ValidateOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. You don't need to specify a value with this switch.
No changes are made when you use this switch.
@@ -331,6 +313,7 @@ No changes are made when you use this switch.
Type: SwitchParameter
Parameter Sets: ValidateOnly
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -340,9 +323,6 @@ Accept wildcard characters: False
```
### -ActiveSyncMailboxPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ActiveSyncMailboxPolicy parameter specifies the mobile device mailbox policy that's applied to the mailbox. You can use any value that uniquely identifies the policy. For example:.
- Name
@@ -355,6 +335,7 @@ If you don't use this parameter, the default mobile device mailbox policy is use
Type: MailboxPolicyIdParameter
Parameter Sets: Equipment, Linked, Room, Shared, User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -364,9 +345,6 @@ Accept wildcard characters: False
```
### -AddressBookPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AddressBookPolicy parameter specifies the address book policy that's applied to the mailbox. You can use any value that uniquely identifies the address book policy. For example:
- Name
@@ -379,6 +357,7 @@ For more information about address book policies, see [Address book policies in
Type: AddressBookMailboxPolicyIdParameter
Parameter Sets: User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -388,9 +367,6 @@ Accept wildcard characters: False
```
### -Alias
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
The Alias value can contain letters, numbers and the following characters:
@@ -415,6 +391,7 @@ The Alias parameter never generates or updates the primary email address of a ma
Type: String
Parameter Sets: Equipment, Linked, Room, Shared, User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -424,15 +401,13 @@ Accept wildcard characters: False
```
### -AllowLegacyDNMismatch
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: User
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -442,15 +417,13 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Archive switch specifies whether to connect the associated archive mailbox. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -460,9 +433,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -472,6 +442,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -481,15 +452,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -499,9 +468,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -510,6 +476,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -519,9 +486,6 @@ Accept wildcard characters: False
```
### -LinkedCredential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LinkedCredential parameter specifies the credentials used to access the domain controller that's specified by the LinkedDomainController parameter. This parameter is optional, even if you're connecting a linked mailbox.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -530,6 +494,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: Linked
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -539,15 +504,13 @@ Accept wildcard characters: False
```
### -ManagedFolderMailboxPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MailboxPolicyIdParameter
Parameter Sets: Equipment, Linked, Room, Shared, User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -557,15 +520,13 @@ Accept wildcard characters: False
```
### -ManagedFolderMailboxPolicyAllowed
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: Equipment, Linked, Room, Shared, User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -575,9 +536,6 @@ Accept wildcard characters: False
```
### -RetentionPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RetentionPolicy parameter specifies the retention policy that's applied to the mailbox. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -590,6 +548,7 @@ Retention policies consist of tags that are applied to mailbox folders and mail
Type: MailboxPolicyIdParameter
Parameter Sets: Equipment, Linked, Room, Shared, User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -599,9 +558,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The User parameter specifies the user object in Active Directory that you want to connect the mailbox to.
For the best results, we recommend using the following values:
@@ -622,6 +578,7 @@ If you don't use this parameter, the command uses the LegacyExchangeDN and Displ
Type: UserIdParameter
Parameter Sets: Equipment, Linked, Room, Shared, User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -631,15 +588,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md b/exchange/exchange-ps/exchange/Delete-QuarantineMessage.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md
rename to exchange/exchange-ps/exchange/Delete-QuarantineMessage.md
index 4fb377a2a5..3dc21e421f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md
+++ b/exchange/exchange-ps/exchange/Delete-QuarantineMessage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/delete-quarantinemessage
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Delete-QuarantineMessage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/delete-quarantinemessage
-schema: 2.0.0
-title: Delete-QuarantineMessage
+ms.reviewer:
---
# Delete-QuarantineMessage
@@ -77,9 +76,6 @@ This example deletes all quarantined messages. The Identity parameter is require
## PARAMETERS
### -Identities
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identities parameter identifies quarantined messages for bulk operations. You identify the messages by using the syntax: `value1,value2...valueN`. Each value is a unique quarantined message identifier in the format `GUID1\GUID2` (for example `c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7`).
You can find the Identity value for a quarantined message by using the Get-QuarantineMessage cmdlet.
@@ -90,6 +86,7 @@ When you use this parameter, the Identity parameter is required, but the value i
Type: QuarantineMessageIdentity[]
Parameter Sets: Identities
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -99,17 +96,15 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the quarantined message that you want to delete. The value is a unique quarantined message identifier in the format `GUID1\GUID2` (for example `c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7`).
You can find the Identity value for a quarantined message by using the Get-QuarantineMessage cmdlet.
```yaml
Type: QuarantineMessageIdentity
-Parameter Sets: Identities, IdentityOnly
+Parameter Sets: Identities
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -118,10 +113,20 @@ Accept pipeline input: True
Accept wildcard characters: False
```
-### -Confirm
+```yaml
+Type: QuarantineMessageIdentity
+Parameter Sets: IdentityOnly
+Aliases:
+Applicable: Exchange Online, Exchange Online Protection
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: True
+Accept wildcard characters: False
+```
+### -Confirm
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -131,6 +136,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -140,9 +146,6 @@ Accept wildcard characters: False
```
### -EntityType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EntityType parameter filters the results by EntityType. Valid values are:
- Email
@@ -154,6 +157,7 @@ The EntityType parameter filters the results by EntityType. Valid values are:
Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -163,9 +167,6 @@ Accept wildcard characters: False
```
### -HardDelete
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The HardDelete switch specifies the message is permanently deleted and isn't recoverable. You don't need to specify a value with this switch.
If you don't use this switch, the message is deleted, but is potentially recoverable.
@@ -174,6 +175,7 @@ If you don't use this switch, the message is deleted, but is potentially recover
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -183,15 +185,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -201,15 +201,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md
index 8352e7a409..fe87141f2e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/Disable-ATPProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-atpprotectionpolicyrule
applicable: Exchange Online
+title: Disable-ATPProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-atpprotectionpolicyrule
-schema: 2.0.0
-title: Disable-ATPProtectionPolicyRule
+ms.reviewer:
---
# Disable-ATPProtectionPolicyRule
@@ -47,9 +46,6 @@ In organizations with Defender for Office 365, this example turns off the Standa
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -62,6 +58,7 @@ By default, the available rules (if they exist) are named Standard Preset Securi
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -83,6 +77,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md b/exchange/exchange-ps/exchange/Disable-AddressListPaging.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
rename to exchange/exchange-ps/exchange/Disable-AddressListPaging.md
index eaf4c603a6..45471267d2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
+++ b/exchange/exchange-ps/exchange/Disable-AddressListPaging.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-addresslistpaging
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-AddressListPaging
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-addresslistpaging
-schema: 2.0.0
-title: Disable-AddressListPaging
+ms.reviewer:
---
# Disable-AddressListPaging
@@ -43,9 +42,6 @@ This example disables virtual list view for address lists in your organization.
## PARAMETERS
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -57,6 +53,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -66,15 +63,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -84,15 +79,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md b/exchange/exchange-ps/exchange/Disable-AntiPhishRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md
rename to exchange/exchange-ps/exchange/Disable-AntiPhishRule.md
index e736bcd2b3..df08fecd4f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md
+++ b/exchange/exchange-ps/exchange/Disable-AntiPhishRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-antiphishrule
applicable: Exchange Online, Exchange Online Protection
+title: Disable-AntiPhishRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-antiphishrule
-schema: 2.0.0
-title: Disable-AntiPhishRule
+ms.reviewer:
---
# Disable-AntiPhishRule
@@ -43,9 +42,6 @@ This example disables the antiphish rule named Engineering Department Phishing R
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the antiphish rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -56,6 +52,7 @@ The Identity parameter specifies the antiphish rule that you want to disable. Yo
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -79,6 +73,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -88,15 +83,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md b/exchange/exchange-ps/exchange/Disable-App.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-App.md
rename to exchange/exchange-ps/exchange/Disable-App.md
index 42abdab2d3..881f7f9195 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
+++ b/exchange/exchange-ps/exchange/Disable-App.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-app
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Disable-App
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-app
-schema: 2.0.0
-title: Disable-App
+ms.reviewer:
---
# Disable-App
@@ -63,15 +62,13 @@ This example disables the Share to Teams app for user Tony.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID of the app.
```yaml
Type: AppIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -81,9 +78,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -95,6 +89,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -104,9 +99,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -115,6 +107,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -124,9 +117,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the identity of the mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -146,6 +136,7 @@ You can't use this parameter with the Identity parameter.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -155,15 +146,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md b/exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
rename to exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md
index 950d45cb73..fa38ef00f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/exchange/Disable-CmdletExtensionAgent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-cmdletextensionagent
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-CmdletExtensionAgent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-cmdletextensionagent
-schema: 2.0.0
-title: Disable-CmdletExtensionAgent
+ms.reviewer:
---
# Disable-CmdletExtensionAgent
@@ -48,9 +47,6 @@ This example disables the cmdlet extension agent named Scripting Agent.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the enabled cmdlet extension agent that you want to disable. You can use any value that uniquely identifies the agent. For example:
- Name
@@ -61,6 +57,7 @@ The Identity parameter specifies the enabled cmdlet extension agent that you wan
Type: CmdletExtensionAgentIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -70,9 +67,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -84,6 +78,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -93,15 +88,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -111,15 +104,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md b/exchange/exchange-ps/exchange/Disable-DistributionGroup.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
rename to exchange/exchange-ps/exchange/Disable-DistributionGroup.md
index 1bf77a6557..e773646d76 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
+++ b/exchange/exchange-ps/exchange/Disable-DistributionGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-distributiongroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-DistributionGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-distributiongroup
-schema: 2.0.0
-title: Disable-DistributionGroup
+ms.reviewer:
---
# Disable-DistributionGroup
@@ -47,9 +46,6 @@ This example mail-disables the distribution group named Distribution Group1.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the distribution group or mail-enabled security group that you want to mail-disable. You can use any value that uniquely identifies the group. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the distribution group or mail-enabled security
Type: DistributionGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -86,6 +80,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,9 +106,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -127,6 +117,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -136,15 +127,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md
rename to exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md
index d6bba5f7e1..9b1751508e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md
+++ b/exchange/exchange-ps/exchange/Disable-DnssecForVerifiedDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-dnssecforverifieddomain
applicable: Exchange Online
+title: Disable-DnssecForVerifiedDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-dnssecforverifieddomain
-schema: 2.0.0
-title: Disable-DnssecForVerifiedDomain
+ms.reviewer:
---
# Disable-DnssecForVerifiedDomain
@@ -45,15 +44,13 @@ This example disables DNSSEC for mail sent to contoso.com.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Online
-
The DomainName parameter specifies the accepted domain in the Exchange Online organization where you want to disable DNSSEC (for example, contoso.com). Use the Get-DnssecForVerifiedDomain cmdlet to see information about DNSSEC for the domain.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -63,15 +60,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -81,15 +76,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md
index df608cff7f..b611fc63b1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/Disable-EOPProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-eopprotectionpolicyrule
applicable: Exchange Online, Exchange Online Protection
+title: Disable-EOPProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-eopprotectionpolicyrule
-schema: 2.0.0
-title: Disable-EOPProtectionPolicyRule
+ms.reviewer:
---
# Disable-EOPProtectionPolicyRule
@@ -54,9 +53,6 @@ In organizations with Defender for Office 365, this example turns off the Standa
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -69,6 +65,7 @@ By default, the available rules (if they exist) are named Standard Preset Securi
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -92,6 +86,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -101,15 +96,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md
rename to exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md
index 7630a48749..7adfa0cbae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/exchange/Disable-HostedContentFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-hostedcontentfilterrule
applicable: Exchange Online, Exchange Online Protection
+title: Disable-HostedContentFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-hostedcontentfilterrule
-schema: 2.0.0
-title: Disable-HostedContentFilterRule
+ms.reviewer:
---
# Disable-HostedContentFilterRule
@@ -43,9 +42,6 @@ This example disables the enabled spam filter rule named Contoso Recipients.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the spam filter rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -56,6 +52,7 @@ The Identity parameter specifies the spam filter rule that you want to disable.
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -79,6 +73,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -88,15 +83,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md
rename to exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md
index 9a3ea41209..442273d3c0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/exchange/Disable-HostedOutboundSpamFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-hostedoutboundspamfilterrule
applicable: Exchange Online, Exchange Online Protection
+title: Disable-HostedOutboundSpamFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-hostedoutboundspamfilterrule
-schema: 2.0.0
-title: Disable-HostedOutboundSpamFilterRule
+ms.reviewer:
---
# Disable-HostedOutboundSpamFilterRule
@@ -43,9 +42,6 @@ This example disables the enabled outbound spam filter rule named Contoso Execut
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the outbound spam filter rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -56,6 +52,7 @@ The Identity parameter specifies the outbound spam filter rule that you want to
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -79,6 +73,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -88,15 +83,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md
rename to exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md
index 3e0dadb098..59ff3a79b1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md
+++ b/exchange/exchange-ps/exchange/Disable-IPv6ForAcceptedDomain.md
@@ -1,12 +1,12 @@
---
+external help file:
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-ipv6foraccepteddomain
applicable: Exchange Online
+title: Disable-IPv6ForAcceptedDomain
+schema: 2.0.0
author: chrisda
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-ipv6foraccepteddomain
-schema: 2.0.0
-title: Disable-IPv6ForAcceptedDomain
+ms.reviewer:
---
# Disable-IPv6ForAcceptedDomain
@@ -46,15 +46,13 @@ This example disables IPv6 support for mail sent to contoso.com. Mail can be del
## PARAMETERS
### -Domain
-
-> Applicable: Exchange Online
-
The Domain parameter specifies the accepted domain that you want to disable mail delivery using IPv6 for.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -64,15 +62,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -82,15 +78,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md b/exchange/exchange-ps/exchange/Disable-InboxRule.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
rename to exchange/exchange-ps/exchange/Disable-InboxRule.md
index 63aca8800c..7bc6e6bce3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
+++ b/exchange/exchange-ps/exchange/Disable-InboxRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-inboxrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Disable-InboxRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-inboxrule
-schema: 2.0.0
-title: Disable-InboxRule
+ms.reviewer:
---
# Disable-InboxRule
@@ -49,9 +48,6 @@ This example disables the Inbox rule MoveAnnouncements in the mailbox Joe@Contos
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the Inbox rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the Inbox rule that you want to disable. You ca
Type: InboxRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -72,15 +69,13 @@ Accept wildcard characters: False
```
### -AlwaysDeleteOutlookRulesBlob
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -90,9 +85,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -104,6 +96,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -113,9 +106,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -124,6 +114,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -133,9 +124,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -146,6 +134,7 @@ A confirmation prompt warns you if the mailbox contains rules that were created
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -155,9 +144,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -175,6 +161,7 @@ The Mailbox parameter specifies the mailbox that contains the Inbox rule. You ca
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -184,15 +171,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch doesn't work on this cmdlet.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md b/exchange/exchange-ps/exchange/Disable-JournalArchiving.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md
rename to exchange/exchange-ps/exchange/Disable-JournalArchiving.md
index cc3806b3c5..a1bf697510 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md
+++ b/exchange/exchange-ps/exchange/Disable-JournalArchiving.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-journalarchiving
applicable: Exchange Online
+title: Disable-JournalArchiving
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-journalarchiving
-schema: 2.0.0
-title: Disable-JournalArchiving
+ms.reviewer:
---
# Disable-JournalArchiving
@@ -50,9 +49,6 @@ This example disables the journal archiving for the user named Timothy Amaral. T
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the identity of the user's journal archive mailbox in Exchange Online. You can use any value that uniquely identifies the journal archive mailbox. For example:
- Name
@@ -70,6 +66,7 @@ The Identity parameter specifies the identity of the user's journal archive mail
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -PreserveMailUser
-
-> Applicable: Exchange Online
-
The PreserveMailUser switch specifies that you want to keep the mail user that's associated with the archive mailbox. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -115,15 +108,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md b/exchange/exchange-ps/exchange/Disable-JournalRule.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
rename to exchange/exchange-ps/exchange/Disable-JournalRule.md
index d3a8397ba1..f36f1eaaaa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
+++ b/exchange/exchange-ps/exchange/Disable-JournalRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-journalrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Disable-JournalRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-journalrule
-schema: 2.0.0
-title: Disable-JournalRule
+ms.reviewer:
---
# Disable-JournalRule
@@ -53,15 +52,13 @@ This example disables all journal rules. The Get-JournalRule cmdlet is used to a
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the journal rule you want to disable. Enter either the name or the GUID of the journal rule. You can omit this parameter label.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -85,6 +79,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -94,9 +89,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -105,6 +97,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -114,15 +107,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md b/exchange/exchange-ps/exchange/Disable-MailContact.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
rename to exchange/exchange-ps/exchange/Disable-MailContact.md
index 3f7988f388..97902c5fd6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
+++ b/exchange/exchange-ps/exchange/Disable-MailContact.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailcontact
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-MailContact
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-mailcontact
-schema: 2.0.0
-title: Disable-MailContact
+ms.reviewer:
---
# Disable-MailContact
@@ -47,9 +46,6 @@ This example mail-disables the mail contact named Ed Meadows.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mail contact that you want to mail-disable. You can use any value that uniquely identifies the mail contact. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the mail contact that you want to mail-disable.
Type: MailContactIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -86,6 +80,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,9 +106,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -127,6 +117,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -136,15 +127,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md b/exchange/exchange-ps/exchange/Disable-MailPublicFolder.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
rename to exchange/exchange-ps/exchange/Disable-MailPublicFolder.md
index e3f87cb3ae..a4aadbbe70 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
+++ b/exchange/exchange-ps/exchange/Disable-MailPublicFolder.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailpublicfolder
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Disable-MailPublicFolder
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-mailpublicfolder
-schema: 2.0.0
-title: Disable-MailPublicFolder
+ms.reviewer:
---
# Disable-MailPublicFolder
@@ -45,9 +44,6 @@ This example mail-disables the public folder Help Desk.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\\PublicFolder.
You can omit the parameter label Identity so that only the public folder name or GUID is supplied.
@@ -56,6 +52,7 @@ You can omit the parameter label Identity so that only the public folder name or
Type: PublicFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -79,6 +73,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -88,9 +83,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -99,6 +91,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -108,9 +101,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
@@ -126,6 +116,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -135,15 +126,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md b/exchange/exchange-ps/exchange/Disable-MailUser.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
rename to exchange/exchange-ps/exchange/Disable-MailUser.md
index c2a47e5857..c0728ff91a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
+++ b/exchange/exchange-ps/exchange/Disable-MailUser.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailuser
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-MailUser
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-mailuser
-schema: 2.0.0
-title: Disable-MailUser
+ms.reviewer:
---
# Disable-MailUser
@@ -48,9 +47,6 @@ This example mail-disables an existing mail user.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mail user that you want to mail-disable. You can use any value that uniquely identifies the mail user. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the mail user that you want to mail-disable. Yo
Type: MailUserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -87,6 +81,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -96,15 +91,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -114,9 +107,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -128,6 +118,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -137,9 +128,6 @@ Accept wildcard characters: False
```
### -IgnoreLegalHold
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreLegalHold switch ignores the legal hold status of the user. You don't need to specify a value with this switch.
When you disable or remove the user, the user's cloud-based mailbox that's on legal hold is also disabled or removed.
@@ -150,6 +138,7 @@ After you disable or remove a mailbox, you can't include it in a discovery searc
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -159,15 +148,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md b/exchange/exchange-ps/exchange/Disable-Mailbox.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
rename to exchange/exchange-ps/exchange/Disable-Mailbox.md
index 57ce870b95..8997b03b35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
+++ b/exchange/exchange-ps/exchange/Disable-Mailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Disable-Mailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-mailbox
-schema: 2.0.0
-title: Disable-Mailbox
+ms.reviewer:
---
# Disable-Mailbox
@@ -100,9 +99,6 @@ This example disables the remote archive for the on-premises user named John Woo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the mailbox that you want to mailbox-disable. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -120,6 +116,7 @@ The Identity parameter specifies the mailbox that you want to mailbox-disable. Y
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -129,9 +126,6 @@ Accept wildcard characters: False
```
### -Arbitration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Arbitration switch is required to mailbox-disable arbitration mailboxes. You don't need to specify a value with this switch.
@@ -142,6 +136,7 @@ Arbitration mailboxes are system mailboxes that are used for storing different t
Type: SwitchParameter
Parameter Sets: Arbitration
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -151,9 +146,6 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Archive switch specifies whether to disconnect the archive mailbox from the associated user. You don't need to specify a value with this switch.
You can't use this switch with the RemoteArchive switch.
@@ -162,6 +154,7 @@ You can't use this switch with the RemoteArchive switch.
Type: SwitchParameter
Parameter Sets: Archive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -171,9 +164,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -185,6 +175,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -194,9 +185,6 @@ Accept wildcard characters: False
```
### -DisableArbitrationMailboxWithOABsAllowed
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DisableArbitrationMailboxWithOABsAllowed switch specifies whether to bypass the checks for offline address books (OABs) within the specified arbitration mailbox that is being mail-disabled. When you use this switch, the arbitration mailbox is disabled even if OABs are present in the mailbox. You don't need to specify a value with this switch.
@@ -205,6 +193,7 @@ The DisableArbitrationMailboxWithOABsAllowed switch specifies whether to bypass
Type: SwitchParameter
Parameter Sets: Arbitration
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -214,9 +203,6 @@ Accept wildcard characters: False
```
### -DisableLastArbitrationMailboxAllowed
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DisableLastArbitrationMailboxAllowed switch specifies whether to disable the specified mailbox, even if it's the last arbitration mailbox in the organization. If you disable the last arbitration mailbox in the organization, you can't have user-created distribution groups or moderated recipients. You don't need to specify a value with this switch.
@@ -225,6 +211,7 @@ The DisableLastArbitrationMailboxAllowed switch specifies whether to disable the
Type: SwitchParameter
Parameter Sets: Arbitration
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -234,9 +221,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -245,6 +229,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -254,9 +239,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -270,6 +252,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -279,9 +262,6 @@ Accept wildcard characters: False
```
### -IgnoreLegalHold
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreLegalHold switch ignores the legal hold status of the user. You don't need to specify a value with this switch.
@@ -294,6 +274,7 @@ After you disable or remove a mailbox, you can't include it in a discovery searc
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -303,9 +284,6 @@ Accept wildcard characters: False
```
### -PermanentlyDisable
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The PermanentlyDisable switch specifies whether to permanently disable the mailbox. You don't need to specify a value with this switch.
@@ -319,6 +297,7 @@ The PermanentlyDisable switch specifies whether to permanently disable the mailb
Type: SwitchParameter
Parameter Sets: Archive
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -328,9 +307,6 @@ Accept wildcard characters: False
```
### -PublicFolder
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The PublicFolder switch is required to mailbox-disable public folder mailboxes. You don't need to specify a value with this switch.
@@ -341,6 +317,7 @@ Public folder mailboxes are specially designed mailboxes that store the hierarch
Type: SwitchParameter
Parameter Sets: PublicFolder
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -350,9 +327,6 @@ Accept wildcard characters: False
```
### -RemoteArchive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RemoteArchive switch specifies whether to disconnect the remote archive for this mailbox. Remote archives exist in the cloud-based service. When you use this switch, the RemoteRecipientType property for the mailbox is reset to specify that this mailbox doesn't have a remote archive. You don't need to specify a value with this switch.
@@ -363,6 +337,7 @@ You can't use this switch with the Archive switch.
Type: SwitchParameter
Parameter Sets: RemoteArchive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -372,15 +347,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md b/exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
rename to exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md
index 1bb4f37eb4..98aaf73776 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
+++ b/exchange/exchange-ps/exchange/Disable-MailboxQuarantine.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-mailboxquarantine
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-MailboxQuarantine
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-mailboxquarantine
-schema: 2.0.0
-title: Disable-MailboxQuarantine
+ms.reviewer:
---
# Disable-MailboxQuarantine
@@ -84,9 +83,6 @@ This example releases the mailbox for the user Brian Johnson from quarantine.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013
-
The Identity parameter specifies the mailbox that you want to release from quarantine. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -104,8 +100,9 @@ You can't use this parameter with the Database or Server parameters.
```yaml
Type: GeneralMailboxIdParameter
-Parameter Sets: MailboxIdentity, MailboxOrMailUserIdentity
+Parameter Sets: MailboxIdentity
Aliases:
+Applicable: Exchange Server 2013
Required: True
Position: 1
@@ -114,10 +111,20 @@ Accept pipeline input: True
Accept wildcard characters: False
```
-### -Database
+```yaml
+Type: GeneralMailboxOrMailUserIdParameter
+Parameter Sets: MailboxOrMailUserIdentity
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
-> Applicable: Exchange Server 2016, Exchange Server 2019
+Required: True
+Position: 1
+Default value: None
+Accept pipeline input: True
+Accept wildcard characters: False
+```
+### -Database
The Database parameter specifies the database that contains the mailboxes you want to release from quarantine. You can use any value that uniquely identifies the database. For example:
- Name
@@ -132,6 +139,7 @@ You can't use this parameter with the Identity or Server parameters.
Type: DatabaseIdParameter
Parameter Sets: StoreMailboxIdentity, IncludeAllMailboxes
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -141,9 +149,6 @@ Accept wildcard characters: False
```
### -IncludeAllDatabases
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The IncludeAllDatabases switch specifies that you want to release all quarantined mailboxes in all databases on the server you specify with the Server parameter. You don't need to specify a value with this switch.
You can only use this switch with the Identity or Database parameters.
@@ -152,6 +157,7 @@ You can only use this switch with the Identity or Database parameters.
Type: SwitchParameter
Parameter Sets: IncludeAllDatabases
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -161,9 +167,6 @@ Accept wildcard characters: False
```
### -IncludeAllMailboxes
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The IncludeAllMailboxes switch specifies that you want to release all mailboxes from quarantine in the database you specify with the Database parameter. You don't need to specify a value with this switch.
You can't use this switch with the StoreMailboxIdentity parameter.
@@ -172,6 +175,7 @@ You can't use this switch with the StoreMailboxIdentity parameter.
Type: SwitchParameter
Parameter Sets: IncludeAllMailboxes
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -181,9 +185,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the server that contains the mailboxes that you want to release from quarantine by using the IncludeAllDatabases switch. You can use any value that uniquely identifies the server. For example:
- Name
@@ -197,6 +198,7 @@ You can't use this parameter with the Identity or Database parameters.
Type: ServerIdParameter
Parameter Sets: IncludeAllDatabases
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -206,9 +208,6 @@ Accept wildcard characters: False
```
### -StoreMailboxIdentity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The StoreMailboxIdentity parameter specifies the mailbox that you want to release from quarantine when you use the Database parameter.
You identify the mailbox by its GUID value. You can find the GUID value by using the Get-Mailbox or Get-MailboxStatistics cmdlets.
@@ -219,6 +218,7 @@ You can't use this switch with the IncludeAllMailboxes switch.
Type: StoreMailboxIdParameter
Parameter Sets: StoreMailboxIdentity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -228,9 +228,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -242,6 +239,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -251,15 +249,13 @@ Accept wildcard characters: False
```
### -IncludePassive
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The IncludePassive switch specifies that you also want to release inactive copies of the mailbox from quarantine. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: StoreMailboxIdentity, IncludeAllMailboxes, MailboxOrMailUserIdentity, IncludeAllDatabases
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -269,15 +265,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md b/exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
rename to exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md
index 44824fbe35..127a8f0542 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
+++ b/exchange/exchange-ps/exchange/Disable-MalwareFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-malwarefilterrule
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Disable-MalwareFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-malwarefilterrule
-schema: 2.0.0
-title: Disable-MalwareFilterRule
+ms.reviewer:
---
# Disable-MalwareFilterRule
@@ -44,15 +43,13 @@ This example disables the enabled malware filter rule named Contoso Recipients.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the malware filter rule that you want to disable. You can use any value that uniquely identifies the rule. For example, you can use the name, GUID or distinguished name (DN) of the malware filter rule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -62,9 +59,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -76,6 +70,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -85,9 +80,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -96,6 +88,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -105,15 +98,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md b/exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
rename to exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md
index 3d4485454e..87451f2763 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
+++ b/exchange/exchange-ps/exchange/Disable-MetaCacheDatabase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-metacachedatabase
applicable: Exchange Server 2019
+title: Disable-MetaCacheDatabase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-metacachedatabase
-schema: 2.0.0
-title: Disable-MetaCacheDatabase
+ms.reviewer:
---
# Disable-MetaCacheDatabase
@@ -43,9 +42,6 @@ This example disables the metacache database on the Exchange server named Mailbo
## PARAMETERS
### -Server
-
-> Applicable: Exchange Server 2019
-
The Server parameter specifies the Mailbox server where you want to disable the metacache database. You can use any value that uniquely identifies the server. For example:
- Name
@@ -59,6 +55,7 @@ You can specify multiple values separated by commas. If the value contains space
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: True
Position: Named
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -80,6 +74,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -89,15 +84,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md b/exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md
rename to exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md
index 8cfbf56343..30685164f7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md
+++ b/exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-outlookanywhere
applicable: Exchange Server 2010
+title: Disable-OutlookAnywhere
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-outlookanywhere
-schema: 2.0.0
-title: Disable-OutlookAnywhere
+ms.reviewer:
---
# Disable-OutlookAnywhere
@@ -67,9 +66,6 @@ This example disables Outlook Anywhere on the specified virtual directory on the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the Outlook Anywhere virtual directory that you want to disable. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -84,6 +80,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: 1
@@ -93,9 +90,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -105,6 +99,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -114,15 +109,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -132,9 +125,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
The Server parameter specifies the Client Access server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -146,6 +136,7 @@ The Server parameter specifies the Client Access server where you want to run th
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -155,15 +146,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
rename to exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md
index 17ffbc57db..6032b60587 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-outlookprotectionrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Disable-OutlookProtectionRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-outlookprotectionrule
-schema: 2.0.0
-title: Disable-OutlookProtectionRule
+ms.reviewer:
---
# Disable-OutlookProtectionRule
@@ -50,15 +49,13 @@ This example disables the Outlook protection rule Project Contoso.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name of the rule being disabled.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -82,6 +76,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -91,9 +86,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -102,6 +94,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -111,15 +104,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md b/exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
rename to exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md
index 069b955360..ade8f3935d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
+++ b/exchange/exchange-ps/exchange/Disable-PushNotificationProxy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-pushnotificationproxy
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-PushNotificationProxy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-pushnotificationproxy
-schema: 2.0.0
-title: Disable-PushNotificationProxy
+ms.reviewer:
---
# Disable-PushNotificationProxy
@@ -44,9 +43,6 @@ This example disables the push notification proxy in the on-premises Exchange or
## PARAMETERS
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -58,6 +54,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -67,15 +64,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md b/exchange/exchange-ps/exchange/Disable-RemoteMailbox.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
rename to exchange/exchange-ps/exchange/Disable-RemoteMailbox.md
index 3549b91ef4..8039e5d1fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
+++ b/exchange/exchange-ps/exchange/Disable-RemoteMailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-remotemailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-RemoteMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-remotemailbox
-schema: 2.0.0
-title: Disable-RemoteMailbox
+ms.reviewer:
---
# Disable-RemoteMailbox
@@ -68,9 +67,6 @@ This example removes the cloud-based archive mailbox but keeps the cloud-based m
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the cloud-based mailbox. Valid values are:
- ADObjectID
@@ -86,6 +82,7 @@ The Identity parameter specifies the cloud-based mailbox. Valid values are:
Type: RemoteMailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -95,9 +92,6 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Archive switch specifies whether to disconnect the cloud-based archive mailbox from the associated cloud-based mailbox. You don't need to specify a value with this switch.
The on-premises mail user and its associated cloud-based mailbox aren't removed if you use this switch.
@@ -106,6 +100,7 @@ The on-premises mail user and its associated cloud-based mailbox aren't removed
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -115,9 +110,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -129,6 +121,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -138,15 +131,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -156,9 +147,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -170,6 +158,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -179,9 +168,6 @@ Accept wildcard characters: False
```
### -IgnoreLegalHold
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreLegalHold switch ignores the legal hold status of the remote user. You don't need to specify a value with this switch.
This switch disables the instance of the remote object in the on-premises organization, and the request to disable the mailbox is synchronized to the cloud. However, if the cloud mailbox is on hold, the request to disable the mailbox is blocked, and an error is returned.
@@ -190,6 +176,7 @@ This switch disables the instance of the remote object in the on-premises organi
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -199,15 +186,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md
rename to exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md
index 1fbb643e5a..8e8073a184 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/exchange/Disable-ReportSubmissionRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-reportsubmissionrule
applicable: Exchange Online
+title: Disable-ReportSubmissionRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-reportsubmissionrule
-schema: 2.0.0
-title: Disable-ReportSubmissionRule
+ms.reviewer:
---
# Disable-ReportSubmissionRule
@@ -43,15 +42,13 @@ This example disables the report submission rule if it's already enabled.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the report submission rule that you want to disable. The default rule is named DefaultReportSubmissionRule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
@@ -61,9 +58,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -75,6 +69,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -84,15 +79,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md
rename to exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md
index 953b770117..35ef4b854d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-safeattachmentrule
applicable: Exchange Online
+title: Disable-SafeAttachmentRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-safeattachmentrule
-schema: 2.0.0
-title: Disable-SafeAttachmentRule
+ms.reviewer:
---
# Disable-SafeAttachmentRule
@@ -45,9 +44,6 @@ This example disables the safe attachment rule named Engineering Department Atta
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the enabled safe attachment rule that you want to disable.
You can use any value that uniquely identifies the rule. For example:
@@ -60,6 +56,7 @@ You can use any value that uniquely identifies the rule. For example:
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -83,6 +77,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md b/exchange/exchange-ps/exchange/Disable-SafeLinksRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md
rename to exchange/exchange-ps/exchange/Disable-SafeLinksRule.md
index 3327a72700..fa714bf72f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md
+++ b/exchange/exchange-ps/exchange/Disable-SafeLinksRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-safelinksrule
applicable: Exchange Online
+title: Disable-SafeLinksRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-safelinksrule
-schema: 2.0.0
-title: Disable-SafeLinksRule
+ms.reviewer:
---
# Disable-SafeLinksRule
@@ -45,9 +44,6 @@ This example disables the enabled Safe Links rule named Engineering Department U
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the enabled Safe Links rule that you want to disable.
You can use any value that uniquely identifies the rule. For example:
@@ -60,6 +56,7 @@ You can use any value that uniquely identifies the rule. For example:
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -83,6 +77,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md b/exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
rename to exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md
index 4e82617c25..13a29e56ed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
+++ b/exchange/exchange-ps/exchange/Disable-ServiceEmailChannel.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-serviceemailchannel
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-ServiceEmailChannel
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-serviceemailchannel
-schema: 2.0.0
-title: Disable-ServiceEmailChannel
+ms.reviewer:
---
# Disable-ServiceEmailChannel
@@ -60,9 +59,6 @@ This example disables the .NET service channel for the user Jeff Hay without req
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the user for which you want to enable the .NET service channel. The user specified must be a valid user in Active Directory who has an Exchange mailbox.
You can use any value that uniquely identifies the mailbox. For example:
@@ -82,6 +78,7 @@ You can use any value that uniquely identifies the mailbox. For example:
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -91,9 +88,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -105,6 +99,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -114,15 +109,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -132,15 +125,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md b/exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md
rename to exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md
index 658111797e..927fd4cd53 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md
+++ b/exchange/exchange-ps/exchange/Disable-SmtpDaneInbound.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-smtpdaneinbound
applicable: Exchange Online
+title: Disable-SmtpDaneInbound
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-smtpdaneinbound
-schema: 2.0.0
-title: Disable-SmtpDaneInbound
+ms.reviewer:
---
# Disable-SmtpDaneInbound
@@ -45,15 +44,13 @@ This example disables SMTP DANE for mail sent to contoso.com.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Online
-
The DomainName parameter specifies the accepted domain in the Exchange Online organization where you want to disable SMTP DANE (for example, contoso.com). Use the Get-SmtpDaneInboundStatus cmdlet to see information about SMTP DNAME for the domain.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
@@ -63,15 +60,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -81,15 +76,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md b/exchange/exchange-ps/exchange/Disable-SweepRule.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
rename to exchange/exchange-ps/exchange/Disable-SweepRule.md
index 95de0ed658..225c628693 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
+++ b/exchange/exchange-ps/exchange/Disable-SweepRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-sweeprule
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Disable-SweepRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-sweeprule
-schema: 2.0.0
-title: Disable-SweepRule
+ms.reviewer:
---
# Disable-SweepRule
@@ -52,9 +51,6 @@ This example disables all Sweep rules in the specified mailbox.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the Sweep rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
- RuleId property (for example, x2hlsdpGmUifjFgxxGIOJw==).
@@ -65,6 +61,7 @@ The Identity parameter specifies the Sweep rule that you want to disable. You ca
Type: SweepRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -86,6 +80,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -106,6 +98,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that contains the rule you want to disable. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -135,6 +125,7 @@ The Mailbox parameter specifies the mailbox that contains the rule you want to d
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -144,15 +135,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md b/exchange/exchange-ps/exchange/Disable-TransportAgent.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
rename to exchange/exchange-ps/exchange/Disable-TransportAgent.md
index dde2c3a4c3..5ccd3fab73 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
+++ b/exchange/exchange-ps/exchange/Disable-TransportAgent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-transportagent
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Disable-TransportAgent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-transportagent
-schema: 2.0.0
-title: Disable-TransportAgent
+ms.reviewer:
---
# Disable-TransportAgent
@@ -45,15 +44,13 @@ This example shows how a fictitious application named Test App is disabled in th
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the display name of the transport agent to be disabled. The length of the name can't exceed 64 characters.
```yaml
Type: TransportAgentObjectId
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -63,9 +60,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -77,6 +71,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -86,9 +81,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -97,6 +89,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -106,9 +99,6 @@ Accept wildcard characters: False
```
### -TransportService
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
- Hub for the Transport service on Mailbox servers.
@@ -121,6 +111,7 @@ The TransportService parameter specifies the transport service that you want to
Type: TransportService
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,15 +121,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md b/exchange/exchange-ps/exchange/Disable-TransportRule.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
rename to exchange/exchange-ps/exchange/Disable-TransportRule.md
index 1921db70e4..03d4189525 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
+++ b/exchange/exchange-ps/exchange/Disable-TransportRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-transportrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Disable-TransportRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-transportrule
-schema: 2.0.0
-title: Disable-TransportRule
+ms.reviewer:
---
# Disable-TransportRule
@@ -46,9 +45,6 @@ This example disables the rule named Sales Disclaimer.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -59,6 +55,7 @@ The Identity parameter specifies the rule that you want to disable. You can use
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -82,6 +76,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -91,9 +86,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -104,6 +96,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,15 +106,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md b/exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md
rename to exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md
index 1ef66ad50b..9a332903c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md
+++ b/exchange/exchange-ps/exchange/Disable-UMAutoAttendant.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-umautoattendant
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Disable-UMAutoAttendant
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-umautoattendant
-schema: 2.0.0
-title: Disable-UMAutoAttendant
+ms.reviewer:
---
# Disable-UMAutoAttendant
@@ -48,15 +47,13 @@ This example disables the UM auto attendant MyUMAutoAttendant.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for the UM auto attendant that's being disabled.
```yaml
Type: UMAutoAttendantIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -66,9 +63,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -78,6 +72,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -87,15 +82,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -105,15 +98,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md
rename to exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md
index 28f9e0bd91..d9f8154eaf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/exchange/Disable-UMCallAnsweringRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-umcallansweringrule
applicable: Exchange Server 2013, Exchange Server 2016
+title: Disable-UMCallAnsweringRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-umcallansweringrule
-schema: 2.0.0
-title: Disable-UMCallAnsweringRule
+ms.reviewer:
---
# Disable-UMCallAnsweringRule
@@ -63,15 +62,13 @@ This example disables the call answering rule MyUMCallAnsweringRule in the mailb
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the UM call answering rule in a UM-enabled mailbox that's to be disabled.
```yaml
Type: UMCallAnsweringRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -81,9 +78,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -95,6 +89,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -104,15 +99,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -122,9 +115,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Mailbox parameter specifies the UM-enabled mailbox that contains the UM call answering rule. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -144,6 +134,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -153,15 +144,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md b/exchange/exchange-ps/exchange/Disable-UMIPGateway.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md
rename to exchange/exchange-ps/exchange/Disable-UMIPGateway.md
index a715ac322d..f0738b7185 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md
+++ b/exchange/exchange-ps/exchange/Disable-UMIPGateway.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-umipgateway
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Disable-UMIPGateway
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-umipgateway
-schema: 2.0.0
-title: Disable-UMIPGateway
+ms.reviewer:
---
# Disable-UMIPGateway
@@ -54,15 +53,13 @@ This example disables the UM IP gateway MyUMIPGateway and disconnects all curren
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for the UM IP gateway being disabled. This is the directory object ID for the UM IP gateway.
```yaml
Type: UMIPGatewayIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -86,6 +80,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -113,15 +106,13 @@ Accept wildcard characters: False
```
### -Immediate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Immediate parameter specifies whether the Mailbox server running the Microsoft Exchange Unified Messaging service drops incoming calls associated with this UM IP gateway immediately or waits for the current calls to finish processing.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -131,15 +122,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md b/exchange/exchange-ps/exchange/Disable-UMMailbox.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md
rename to exchange/exchange-ps/exchange/Disable-UMMailbox.md
index ea3727bee6..f9ea3dd8ba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md
+++ b/exchange/exchange-ps/exchange/Disable-UMMailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-ummailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Disable-UMMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-ummailbox
-schema: 2.0.0
-title: Disable-UMMailbox
+ms.reviewer:
---
# Disable-UMMailbox
@@ -48,9 +47,6 @@ This example disables Unified Messaging on the mailbox for tonysmith@contoso.com
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the mailbox that you want to disable for Unified Messaging. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -68,6 +64,7 @@ The Identity parameter specifies the mailbox that you want to disable for Unifie
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -77,9 +74,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -89,6 +83,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -130,6 +120,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -139,9 +130,6 @@ Accept wildcard characters: False
```
### -KeepProperties
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The KeepProperties parameter specifies whether to keep or remove the UM properties for the mailbox. Valid values are:
- $true: The UM properties are retained on the mailbox. This is the default value.
@@ -151,6 +139,7 @@ The KeepProperties parameter specifies whether to keep or remove the UM properti
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -160,15 +149,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md b/exchange/exchange-ps/exchange/Disable-UMServer.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md
rename to exchange/exchange-ps/exchange/Disable-UMServer.md
index a4713a795f..2b34bd0f25 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md
+++ b/exchange/exchange-ps/exchange/Disable-UMServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-umserver
applicable: Exchange Server 2010
+title: Disable-UMServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-umserver
-schema: 2.0.0
-title: Disable-UMServer
+ms.reviewer:
---
# Disable-UMServer
@@ -61,15 +60,13 @@ This example disables Unified Messaging on the Unified Messaging server named My
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the identifier for the Unified Messaging server being disabled. This is the directory object ID for the UM server.
```yaml
Type: UMServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: 1
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -91,6 +85,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -100,15 +95,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -118,15 +111,13 @@ Accept wildcard characters: False
```
### -Immediate
-
-> Applicable: Exchange Server 2010
-
The Immediate parameter specifies whether the Unified Messaging server drops all current calls or enables current calls to finish. If this parameter is set to $true, all calls that are currently connected are disconnected.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -136,15 +127,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md b/exchange/exchange-ps/exchange/Disable-UMService.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md
rename to exchange/exchange-ps/exchange/Disable-UMService.md
index f712294833..48cc82a85b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md
+++ b/exchange/exchange-ps/exchange/Disable-UMService.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/disable-umservice
applicable: Exchange Server 2013, Exchange Server 2016
+title: Disable-UMService
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disable-umservice
-schema: 2.0.0
-title: Disable-UMService
+ms.reviewer:
---
# Disable-UMService
@@ -63,9 +62,6 @@ This example disables Unified Messaging on the UM server MyUMServer and disconne
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the Exchange 2010 UM server that you want to disable. You can use any value that uniquely identifies the UM server. For example:
- Name
@@ -77,6 +73,7 @@ The Identity parameter specifies the Exchange 2010 UM server that you want to di
Type: UMServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -86,9 +83,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -98,6 +92,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -107,15 +102,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -125,15 +118,13 @@ Accept wildcard characters: False
```
### -Immediate
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Immediate parameter specifies whether the UM server drops all current calls or enables current calls to finish. If this parameter is set to $true, all calls that are currently connected are disconnected.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -143,15 +134,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disconnect-ExchangeOnline.md b/exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Disconnect-ExchangeOnline.md
rename to exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md
index c79725b236..c2a6bb1153 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disconnect-ExchangeOnline.md
+++ b/exchange/exchange-ps/exchange/Disconnect-ExchangeOnline.md
@@ -1,13 +1,13 @@
---
+external help file: ExchangeOnlineManagement-help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/disconnect-exchangeonline
applicable: Exchange Online
+title: Disconnect-ExchangeOnline
+schema: 2.0.0
author: chrisda
-external help file: ExchangeOnlineManagement-help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/disconnect-exchangeonline
-schema: 2.0.0
-title: Disconnect-ExchangeOnline
+ms.reviewer:
---
# Disconnect-ExchangeOnline
@@ -85,9 +85,6 @@ This example disconnects the REST-based Exchange Online PowerShell connections t
## PARAMETERS
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -97,6 +94,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -106,9 +104,6 @@ Accept wildcard characters: False
```
### -ConnectionId
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.2.0 or later of the module.
The ConnectionId parameter specifies the REST API connections to disconnect by ConnectionId. ConnectionId is a GUID value in the output of the Get-ConnectionInformation cmdlet that uniquely identifies a connection, even if you have multiple connections open. You can specify multiple ConnectionId values separated by commas.
@@ -119,6 +114,7 @@ Don't use this parameter with the ModulePrefix parameter.
Type: String[]
Parameter Sets: ConnectionId
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -128,9 +124,6 @@ Accept wildcard characters: False
```
### -ModulePrefix
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.2.0 or later of the module.
The ModulePrefix parameter specifies the REST API connections to disconnect by ModulePrefix. When you use the Prefix parameter with the Connect-ExchangeOnline cmdlet, the specified text is added to the names of all Exchange Online cmdlets (for example, Get-InboundConnector becomes Get-ContosoInboundConnector). The ModulePrefix value is visible in the output of the Get-ConnectionInformation cmdlet. You can specify multiple ModulePrefix values separated by commas.
@@ -141,6 +134,7 @@ Don't use this parameter with the ConnectionId parameter.
Type: String[]
Parameter Sets: ModulePrefix
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -150,15 +144,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md b/exchange/exchange-ps/exchange/Dismount-Database.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
rename to exchange/exchange-ps/exchange/Dismount-Database.md
index f71b315592..7159912a4e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
+++ b/exchange/exchange-ps/exchange/Dismount-Database.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/dismount-database
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Dismount-Database
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/dismount-database
-schema: 2.0.0
-title: Dismount-Database
+ms.reviewer:
---
# Dismount-Database
@@ -46,9 +45,6 @@ Regardless of where you run this cmdlet, it operates against the server hosting
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the database that you want to dismount. You can use any value that uniquely identifies the database. For example:
- Name
@@ -59,6 +55,7 @@ The Identity parameter specifies the database that you want to dismount. You can
Type: DatabaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -80,6 +74,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -89,15 +84,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -107,15 +100,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md b/exchange/exchange-ps/exchange/Dump-ProvisioningCache.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
rename to exchange/exchange-ps/exchange/Dump-ProvisioningCache.md
index caf85044ed..b16e9a249e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
+++ b/exchange/exchange-ps/exchange/Dump-ProvisioningCache.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/dump-provisioningcache
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Dump-ProvisioningCache
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/dump-provisioningcache
-schema: 2.0.0
-title: Dump-ProvisioningCache
+ms.reviewer:
---
# Dump-ProvisioningCache
@@ -61,15 +60,13 @@ This example displays all cache keys for the specified server and Windows PowerS
## PARAMETERS
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the fully qualified domain name (FQDN) of the server that the application you want to reset is running on.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -Application
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Application parameter specifies the specific administrative application to reset the provisioning cache for. You can use the following values:
- Powershell
@@ -95,6 +89,7 @@ The Application parameter specifies the specific administrative application to r
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -104,15 +99,13 @@ Accept wildcard characters: False
```
### -GlobalCache
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The GlobalCache switch specifies that all cache keys are cleared. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: GlobalCache
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -122,9 +115,6 @@ Accept wildcard characters: False
```
### -CacheKeys
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The CacheKeys parameter specifies the value for the cache key that you want to clear. The format for the values should contain 32 digits separated by four dashes: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Use the Dump-ProvisioningCache cmdlet to return a list of cache keys.
@@ -133,6 +123,7 @@ Use the Dump-ProvisioningCache cmdlet to return a list of cache keys.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -142,9 +133,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -154,6 +142,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -163,15 +152,13 @@ Accept wildcard characters: False
```
### -CurrentOrganization
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The CurrentOrganization switch specifies that the provision cache is reset for this organization. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: OrganizationCache
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -181,15 +168,13 @@ Accept wildcard characters: False
```
### -Organizations
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Organizations parameter specifies the organizations that the provisioning cache will be reset. This parameter is used in multi-tenant deployments.
```yaml
Type: MultiValuedProperty
Parameter Sets: OrganizationCache
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -199,15 +184,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md
index c62fb63b78..af887e025f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/Enable-ATPProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-atpprotectionpolicyrule
applicable: Exchange Online
+title: Enable-ATPProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-atpprotectionpolicyrule
-schema: 2.0.0
-title: Enable-ATPProtectionPolicyRule
+ms.reviewer:
---
# Enable-ATPProtectionPolicyRule
@@ -47,9 +46,6 @@ In organizations with Defender for Office 365, this example turns on the Standar
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -62,6 +58,7 @@ By default, the available rules (if they exist) are named Standard Preset Securi
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -83,6 +77,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md b/exchange/exchange-ps/exchange/Enable-AddressListPaging.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
rename to exchange/exchange-ps/exchange/Enable-AddressListPaging.md
index 7cf35a1dd4..7bdc8deb33 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
+++ b/exchange/exchange-ps/exchange/Enable-AddressListPaging.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-addresslistpaging
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-AddressListPaging
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-addresslistpaging
-schema: 2.0.0
-title: Enable-AddressListPaging
+ms.reviewer:
---
# Enable-AddressListPaging
@@ -45,9 +44,6 @@ This example enables virtual list view for your organization.
## PARAMETERS
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -57,6 +53,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -66,15 +63,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -84,15 +79,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md b/exchange/exchange-ps/exchange/Enable-AntiPhishRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md
rename to exchange/exchange-ps/exchange/Enable-AntiPhishRule.md
index 418b53848b..55bc463ac2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md
+++ b/exchange/exchange-ps/exchange/Enable-AntiPhishRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-antiphishrule
applicable: Exchange Online, Exchange Online Protection
+title: Enable-AntiPhishRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-antiphishrule
-schema: 2.0.0
-title: Enable-AntiPhishRule
+ms.reviewer:
---
# Enable-AntiPhishRule
@@ -43,9 +42,6 @@ This example enables the antiphish rule named Marketing Department Phishing Rule
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the antiphish rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -56,6 +52,7 @@ The Identity parameter specifies the antiphish rule that you want to enable. You
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -77,6 +71,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -86,15 +81,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md b/exchange/exchange-ps/exchange/Enable-AntispamUpdates.md
similarity index 85%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md
rename to exchange/exchange-ps/exchange/Enable-AntispamUpdates.md
index 6a01e8936d..40a8ec1a57 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md
+++ b/exchange/exchange-ps/exchange/Enable-AntispamUpdates.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-antispamupdates
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-AntispamUpdates
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-antispamupdates
-schema: 2.0.0
-title: Enable-AntispamUpdates
+ms.reviewer:
---
# Enable-AntispamUpdates
@@ -42,15 +41,13 @@ This cmdlet was deprecated in Microsoft Exchange Server 2010 Service Pack 1 and
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -60,15 +57,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -78,15 +73,13 @@ Accept wildcard characters: False
```
### -SpamSignatureUpdatesEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -96,15 +89,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md b/exchange/exchange-ps/exchange/Enable-App.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-App.md
rename to exchange/exchange-ps/exchange/Enable-App.md
index fe719c307f..788dc99c86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
+++ b/exchange/exchange-ps/exchange/Enable-App.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-app
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Enable-App
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-app
-schema: 2.0.0
-title: Enable-App
+ms.reviewer:
---
# Enable-App
@@ -63,15 +62,13 @@ This example enables the Share to Teams app for user Tony.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID of the app.
```yaml
Type: AppIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -81,9 +78,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -93,6 +87,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -102,9 +97,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -113,6 +105,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -122,9 +115,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -142,6 +132,7 @@ The Mailbox parameter specifies the mailbox. You can use any value that uniquely
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -151,15 +142,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md b/exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
rename to exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md
index b954efdd4a..926da3eb88 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/exchange/Enable-CmdletExtensionAgent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-cmdletextensionagent
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-CmdletExtensionAgent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-cmdletextensionagent
-schema: 2.0.0
-title: Enable-CmdletExtensionAgent
+ms.reviewer:
---
# Enable-CmdletExtensionAgent
@@ -50,9 +49,6 @@ This example enables the cmdlet extension agent named Scripting Agent. Before yo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the disabled cmdlet extension agent that you want to enable. You can use any value that uniquely identifies the agent. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the disabled cmdlet extension agent that you wa
Type: CmdletExtensionAgentIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -84,6 +78,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -93,15 +88,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -111,15 +104,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md b/exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md
rename to exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md
index a28f12032f..c2a69f5215 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md
+++ b/exchange/exchange-ps/exchange/Enable-ComplianceTagStorage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-compliancetagstorage
applicable: Security & Compliance
+title: Enable-ComplianceTagStorage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-compliancetagstorage
-schema: 2.0.0
-title: Enable-ComplianceTagStorage
+ms.reviewer:
---
# Enable-ComplianceTagStorage
@@ -46,9 +45,6 @@ This example creates the label policy in the Microsoft Purview compliance portal
## PARAMETERS
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -58,6 +54,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -67,15 +64,13 @@ Accept wildcard characters: False
```
### -RecordsManagementSecurityGroupEmail
-
-> Applicable: Security & Compliance
-
This RecordsManagementSecurityGroupEmail parameter specifies the email address of the mail-enabled security group that contains the records managers in the organization.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -85,15 +80,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md b/exchange/exchange-ps/exchange/Enable-DistributionGroup.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
rename to exchange/exchange-ps/exchange/Enable-DistributionGroup.md
index 2b0bca1bab..cda305dfb4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
+++ b/exchange/exchange-ps/exchange/Enable-DistributionGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-distributiongroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-DistributionGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-distributiongroup
-schema: 2.0.0
-title: Enable-DistributionGroup
+ms.reviewer:
---
# Enable-DistributionGroup
@@ -51,9 +50,6 @@ This example mail-enables the universal distribution group named Distribution Gr
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the universal security group or universal distribution group that you want to mail-enable. You can use any value that uniquely identifies the group. For example:
- Name
@@ -65,6 +61,7 @@ The Identity parameter specifies the universal security group or universal distr
Type: GroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -Alias
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
The Alias value can contain letters, numbers and the following characters:
@@ -101,6 +95,7 @@ The Alias parameter never generates or updates the primary email address of a ma
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -122,6 +114,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,15 +124,13 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DisplayName parameter specifies the display name of the group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -149,15 +140,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -167,9 +156,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
By default, the primary SMTP address is generated based on the default email address policy and the value of the Alias parameter or the Name property. If you use the PrimarySmtpAddress parameter to specify the primary email address, the EmailAddressPolicyEnabled property is set to the value False, which means the email addresses of the group won't be automatically updated by email address policies.
@@ -178,6 +164,7 @@ By default, the primary SMTP address is generated based on the default email add
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -187,15 +174,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md
rename to exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md
index ba66a7d906..785b0029ab 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md
+++ b/exchange/exchange-ps/exchange/Enable-DnssecForVerifiedDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-dnssecforverifieddomain
applicable: Exchange Online
+title: Enable-DnssecForVerifiedDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-dnssecforverifieddomain
-schema: 2.0.0
-title: Enable-DnssecForVerifiedDomain
+ms.reviewer:
---
# Enable-DnssecForVerifiedDomain
@@ -47,15 +46,13 @@ This example enables DNSSEC for mail sent to contoso.com.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Online
-
The DomainName parameter specifies the accepted domain in the Exchange Online organization where you want to enable DNSSEC (for example, contoso.com). Use the Get-AcceptedDomain cmdlet to see the accepted domains in the organization.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -65,15 +62,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -83,15 +78,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md
index 55ab46f3c3..a73b54c47d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/Enable-EOPProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-eopprotectionpolicyrule
applicable: Exchange Online, Exchange Online Protection
+title: Enable-EOPProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-eopprotectionpolicyrule
-schema: 2.0.0
-title: Enable-EOPProtectionPolicyRule
+ms.reviewer:
---
# Enable-EOPProtectionPolicyRule
@@ -54,9 +53,6 @@ In organizations with Defender for Office 365, this example turns on the Standar
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -69,6 +65,7 @@ By default, the available rules (if they exist) are named Standard Preset Securi
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -90,6 +84,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -99,15 +94,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
rename to exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md
index 8ac543b37b..29cc1af6d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
+++ b/exchange/exchange-ps/exchange/Enable-ExchangeCertificate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-exchangecertificate
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-ExchangeCertificate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-exchangecertificate
-schema: 2.0.0
-title: Enable-ExchangeCertificate
+ms.reviewer:
---
# Enable-ExchangeCertificate
@@ -17,7 +16,7 @@ This cmdlet is available only in on-premises Exchange.
Use the Enable-ExchangeCertificate cmdlet to enable an existing certificate on the Exchange server for Exchange services such as Internet Information Services (IIS), SMTP, POP, IMAP and Unified Messaging (UM). Once you enable a certificate for a service, you can't disable it.
-To see the existing certificates that are used for Exchange services, use [Get-ExchangeCertificate](https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangecertificate).
+To see the existing certificates that are used for Exchange services, use [Get-ExchangeCertificate](https://learn.microsoft.com/powershell/module/exchange/get-exchangecertificate).
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
@@ -71,9 +70,6 @@ This example enables a certificate for POP, IMAP, SMTP and IIS services.
## PARAMETERS
### -Thumbprint
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Thumbprint parameter specifies the certificate that you want to configure. You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet.
The Thumbprint parameter, not the Identity parameter, is the positional parameter for this cmdlet. Therefore, when you specify a thumbprint value by itself, the command uses that value for the Thumbprint parameter.
@@ -82,6 +78,7 @@ The Thumbprint parameter, not the Identity parameter, is the positional paramete
Type: String
Parameter Sets: Thumbprint
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -91,9 +88,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the certificate that you want to configure. Valid values are:
- `ServerNameOrFQDN\Thumbprint`
@@ -109,6 +103,7 @@ The Thumbprint parameter, not the Identity parameter, is the positional paramete
Type: ExchangeCertificateIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -118,9 +113,6 @@ Accept wildcard characters: False
```
### -Services
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Services parameter specifies the Exchange services that the certificate is enabled for. Valid values are:
- Federation: Don't use this command to enable a certificate for federation. Creating or modifying a federation trust enables or modifies how certificates are used for federation. You manage the certificates that used for federation trusts with the New-FederationTrust and Set-FederationTrust cmdlets.
@@ -141,6 +133,7 @@ Different services have different certificate requirements. For example, some se
Type: AllowedServices
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -150,9 +143,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -162,6 +152,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -171,9 +162,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -182,6 +170,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -191,9 +180,6 @@ Accept wildcard characters: False
```
### -DoNotRequireSsl
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DoNotRequireSsl switch prevents the command from enabling the "require SSL" setting on the default web site when you enable the certificate for IIS. You don't need to specify a value with this switch.
If you don't use this switch, and you use the Services parameter to enable the certificate for IIS, the command enables the "require SSL" setting for the default web site in IIS.
@@ -202,6 +188,7 @@ If you don't use this switch, and you use the Services parameter to enable the c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -211,9 +198,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -224,6 +208,7 @@ By default, when you enable a certificate for SMTP, the command prompts you to r
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -233,15 +218,13 @@ Accept wildcard characters: False
```
### -NetworkServiceAllowed
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The NetworkServiceAllowed switch gives the built-in Network Service account permission to read the certificate's private key without enabling the certificate for SMTP. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -251,9 +234,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -269,6 +249,7 @@ You can't use this parameter with the Identity parameter, but you can use it wit
Type: ServerIdParameter
Parameter Sets: Thumbprint
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -278,15 +259,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md
rename to exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md
index 2e2746777a..8b49e06134 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/exchange/Enable-HostedContentFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-hostedcontentfilterrule
applicable: Exchange Online, Exchange Online Protection
+title: Enable-HostedContentFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-hostedcontentfilterrule
-schema: 2.0.0
-title: Enable-HostedContentFilterRule
+ms.reviewer:
---
# Enable-HostedContentFilterRule
@@ -43,9 +42,6 @@ This example enables the disabled spam filter rule named Contoso Recipients.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the spam filter rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -56,6 +52,7 @@ The Identity parameter specifies the spam filter rule that you want to enable. Y
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -77,6 +71,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -86,15 +81,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md
rename to exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md
index ea9fd1312b..b0b6d2ea45 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/exchange/Enable-HostedOutboundSpamFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-hostedoutboundspamfilterrule
applicable: Exchange Online, Exchange Online Protection
+title: Enable-HostedOutboundSpamFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-hostedoutboundspamfilterrule
-schema: 2.0.0
-title: Enable-HostedOutboundSpamFilterRule
+ms.reviewer:
---
# Enable-HostedOutboundSpamFilterRule
@@ -43,9 +42,6 @@ This example enables the disabled outbound spam filter rule named Contoso Execut
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the outbound spam filter rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -56,6 +52,7 @@ The Identity parameter specifies the outbound spam filter rule that you want to
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -77,6 +71,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -86,15 +81,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md
rename to exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md
index 742bc1c935..1ce4f5db89 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md
+++ b/exchange/exchange-ps/exchange/Enable-IPv6ForAcceptedDomain.md
@@ -1,12 +1,12 @@
---
+external help file:
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-ipv6foraccepteddomain
applicable: Exchange Online
+title: Enable-IPv6ForAcceptedDomain
+schema: 2.0.0
author: chrisda
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-ipv6foraccepteddomain
-schema: 2.0.0
-title: Enable-IPv6ForAcceptedDomain
+ms.reviewer:
---
# Enable-IPv6ForAcceptedDomain
@@ -46,15 +46,13 @@ This example enables IPv6 support for mail sent to contoso.com. Mail can be deli
## PARAMETERS
### -Domain
-
-> Applicable: Exchange Online
-
The Domain parameter specifies the accepted domain that you want to enable mail delivery using IPv6 for.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -64,15 +62,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -82,15 +78,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md b/exchange/exchange-ps/exchange/Enable-InboxRule.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
rename to exchange/exchange-ps/exchange/Enable-InboxRule.md
index d1680d3778..a4e38bdcbb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
+++ b/exchange/exchange-ps/exchange/Enable-InboxRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-inboxrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Enable-InboxRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-inboxrule
-schema: 2.0.0
-title: Enable-InboxRule
+ms.reviewer:
---
# Enable-InboxRule
@@ -49,9 +48,6 @@ This example enables the Inbox rule named Move To Junk Mail in the mailbox that
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the Inbox rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the Inbox rule that you want to enable. You can
Type: InboxRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -72,15 +69,13 @@ Accept wildcard characters: False
```
### -AlwaysDeleteOutlookRulesBlob
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -90,9 +85,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -102,6 +94,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -111,9 +104,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -122,6 +112,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,9 +122,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -144,6 +132,7 @@ A confirmation prompt warns you if the mailbox contains rules that were created
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -153,9 +142,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -173,6 +159,7 @@ The Mailbox parameter specifies the mailbox that contains the Inbox rule. You ca
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -182,15 +169,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md b/exchange/exchange-ps/exchange/Enable-JournalRule.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
rename to exchange/exchange-ps/exchange/Enable-JournalRule.md
index 9cfd07daa1..a642ee6b6f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
+++ b/exchange/exchange-ps/exchange/Enable-JournalRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-journalrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Enable-JournalRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-journalrule
-schema: 2.0.0
-title: Enable-JournalRule
+ms.reviewer:
---
# Enable-JournalRule
@@ -46,15 +45,13 @@ This example enables the existing journal rule Brokerage Communications.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the journal rule you want to enable. Enter either the name or GUID of the journal rule. You can omit this parameter label.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -64,9 +61,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -76,6 +70,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -85,9 +80,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -96,6 +88,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -105,15 +98,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md b/exchange/exchange-ps/exchange/Enable-MailContact.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
rename to exchange/exchange-ps/exchange/Enable-MailContact.md
index 14a850f520..32afb576cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
+++ b/exchange/exchange-ps/exchange/Enable-MailContact.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailcontact
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-MailContact
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-mailcontact
-schema: 2.0.0
-title: Enable-MailContact
+ms.reviewer:
---
# Enable-MailContact
@@ -53,9 +52,6 @@ This example mail-enables an existing contact that isn't mail-enabled.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the non-mail-enabled contact that you want to mail-enable. You can use any value that uniquely identifies the contact. For example:
- Name
@@ -67,6 +63,7 @@ The Identity parameter specifies the non-mail-enabled contact that you want to m
Type: ContactIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -76,9 +73,6 @@ Accept wildcard characters: False
```
### -ExternalEmailAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExternalEmailAddress parameter specifies the target email address of the mail contact or mail user. By default, this value is used as the primary email address of the mail contact or mail user.
In on-premises environments, you can use the PrimarySMTPAddress parameter to set the primary email address to a different value. However, we recommend this only in cross-forest environments.
@@ -87,6 +81,7 @@ In on-premises environments, you can use the PrimarySMTPAddress parameter to set
Type: ProxyAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -96,9 +91,6 @@ Accept wildcard characters: False
```
### -Alias
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
The Alias value can contain letters, numbers and the following characters:
@@ -123,6 +115,7 @@ The Alias parameter never generates or updates the primary email address of a ma
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -132,9 +125,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -144,6 +134,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -153,15 +144,13 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DisplayName parameter specifies the display name of the mail contact. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -171,15 +160,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -189,9 +176,6 @@ Accept wildcard characters: False
```
### -MacAttachmentFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
- BinHex (This is the default value)
@@ -208,6 +192,7 @@ The MacAttachmentFormat and MessageFormat parameters are interdependent:
Type: MacAttachmentFormat
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -217,9 +202,6 @@ Accept wildcard characters: False
```
### -MessageBodyFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
- Text
@@ -235,6 +217,7 @@ The MessageFormat and MessageBodyFormat parameters are interdependent:
Type: MessageBodyFormat
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -244,9 +227,6 @@ Accept wildcard characters: False
```
### -MessageFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
- Text
@@ -263,6 +243,7 @@ Therefore, if you want to change the MessageFormat parameter from Mime to Text,
Type: MessageFormat
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -272,9 +253,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
By default, the primary address is the same as the ExternalEmailAddress parameter value.
@@ -285,6 +263,7 @@ If you use the PrimarySmtpAddress parameter to specify the primary email address
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -294,9 +273,6 @@ Accept wildcard characters: False
```
### -UsePreferMessageFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
- $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact.
@@ -306,6 +282,7 @@ The UsePreferMessageFormat specifies whether the message format settings configu
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -315,15 +292,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md b/exchange/exchange-ps/exchange/Enable-MailPublicFolder.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
rename to exchange/exchange-ps/exchange/Enable-MailPublicFolder.md
index 1c467a88f0..a029579014 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
+++ b/exchange/exchange-ps/exchange/Enable-MailPublicFolder.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailpublicfolder
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Enable-MailPublicFolder
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-mailpublicfolder
-schema: 2.0.0
-title: Enable-MailPublicFolder
+ms.reviewer:
---
# Enable-MailPublicFolder
@@ -54,9 +53,6 @@ This example mail-enables the public folder Reports that's in the parent folder
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\\PublicFolder.
You can omit the parameter label so that only the public folder name or GUID is supplied.
@@ -65,6 +61,7 @@ You can omit the parameter label so that only the public folder name or GUID is
Type: PublicFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -86,6 +80,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -106,6 +98,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -115,15 +108,13 @@ Accept wildcard characters: False
```
### -HiddenFromAddressListsEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The HiddenFromAddressListsEnabled parameter specifies whether the folder is hidden from address lists. Valid values are $true and $false. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -133,9 +124,6 @@ Accept wildcard characters: False
```
### -OverrideRecipientQuotas
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -144,6 +132,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -153,9 +142,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
@@ -171,6 +157,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -180,15 +167,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md b/exchange/exchange-ps/exchange/Enable-MailUser.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
rename to exchange/exchange-ps/exchange/Enable-MailUser.md
index 431b7b0427..0a00e13f2c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
+++ b/exchange/exchange-ps/exchange/Enable-MailUser.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailuser
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-MailUser
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-mailuser
-schema: 2.0.0
-title: Enable-MailUser
+ms.reviewer:
---
# Enable-MailUser
@@ -69,9 +68,6 @@ This example mail-enables user John with the external email address john@contoso
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the user that you want to mail-enable. You can use any value that uniquely identifies the user. For example:
- Name
@@ -83,6 +79,7 @@ The Identity parameter specifies the user that you want to mail-enable. You can
Type: UserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -92,15 +89,13 @@ Accept wildcard characters: False
```
### -ExternalEmailAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExternalEmailAddress parameter specifies an email address outside the organization. Email messages sent to the mail-enabled user are sent to this external address.
```yaml
Type: ProxyAddress
-Parameter Sets: EnabledUser, EnableGuestUser
+Parameter Sets: EnabledUser
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -109,10 +104,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -Alias
+```yaml
+Type: ProxyAddress
+Parameter Sets: EnableGuestUser
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -Alias
The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
The Alias value can contain letters, numbers and the following characters:
@@ -137,6 +142,7 @@ The Alias parameter never generates or updates the primary email address of a ma
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -146,9 +152,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -158,6 +161,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -167,15 +171,13 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DisplayName parameter specifies the display name of the mail user. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -185,15 +187,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -203,9 +203,6 @@ Accept wildcard characters: False
```
### -MacAttachmentFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
- BinHex (This is the default value)
@@ -222,6 +219,7 @@ The MacAttachmentFormat and MessageFormat parameters are interdependent:
Type: MacAttachmentFormat
Parameter Sets: EnabledUser
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -231,9 +229,6 @@ Accept wildcard characters: False
```
### -MessageBodyFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
- Text
@@ -249,6 +244,7 @@ The MessageFormat and MessageBodyFormat parameters are interdependent:
Type: MessageBodyFormat
Parameter Sets: EnabledUser
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -258,9 +254,6 @@ Accept wildcard characters: False
```
### -MessageFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
- Text
@@ -277,6 +270,7 @@ Therefore, if you want to change the MessageFormat parameter from Mime to Text,
Type: MessageFormat
Parameter Sets: EnabledUser
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -286,9 +280,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
By default, the primary address is the same as the ExternalEmailAddress parameter value.
@@ -299,6 +290,7 @@ If you use the PrimarySmtpAddress parameter to specify the primary email address
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -308,9 +300,6 @@ Accept wildcard characters: False
```
### -UsePreferMessageFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
- $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact.
@@ -320,6 +309,7 @@ The UsePreferMessageFormat specifies whether the message format settings configu
Type: Boolean
Parameter Sets: EnabledUser
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -329,15 +319,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md b/exchange/exchange-ps/exchange/Enable-Mailbox.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
rename to exchange/exchange-ps/exchange/Enable-Mailbox.md
index dc154ed3be..3a49c7ac0c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
+++ b/exchange/exchange-ps/exchange/Enable-Mailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Enable-Mailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-mailbox
-schema: 2.0.0
-title: Enable-Mailbox
+ms.reviewer:
---
# Enable-Mailbox
@@ -303,9 +302,6 @@ This example creates a remote archive for the existing on-premises user named Ay
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the user or InetOrgPerson object that you want to mailbox-enable. You can use any value that uniquely identifies the user. For example:
- Name
@@ -317,6 +313,7 @@ The Identity parameter specifies the user or InetOrgPerson object that you want
Type: UserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -326,9 +323,6 @@ Accept wildcard characters: False
```
### -Arbitration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Arbitration switch is required to mailbox-enable arbitration mailboxes. You don't need to specify a value with this switch.
@@ -339,6 +333,7 @@ Arbitration mailboxes are system mailboxes that are used for storing different t
Type: SwitchParameter
Parameter Sets: Arbitration
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -348,9 +343,6 @@ Accept wildcard characters: False
```
### -ArchiveDomain
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ArchiveDomain parameter specifies the domain in the cloud-based service where the archive that's associated with this mailbox exists. For example, if the SMTP email address of the user is tony@contoso.com, the SMTP domain could be archive.contoso.com.
@@ -361,6 +353,7 @@ Only use this parameter if the archive is hosted in the cloud-based service.
Type: SmtpDomain
Parameter Sets: RemoteArchive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -370,9 +363,6 @@ Accept wildcard characters: False
```
### -Discovery
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Discovery switch is required to mailbox-enable Discovery mailboxes. You don't need to specify a value with this switch.
@@ -383,6 +373,7 @@ Discovery mailboxes are created as target mailboxes for Discovery searches. Afte
Type: SwitchParameter
Parameter Sets: Discovery
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -392,9 +383,6 @@ Accept wildcard characters: False
```
### -Equipment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Equipment switch is required to mailbox-enable equipment mailboxes. You don't need to specify a value with this switch.
@@ -405,6 +393,7 @@ Equipment mailboxes are resource mailboxes that aren't associated with a specifi
Type: SwitchParameter
Parameter Sets: Equipment
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -414,9 +403,6 @@ Accept wildcard characters: False
```
### -LinkedDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The LinkedDomainController parameter specifies the domain controller in the forest where the user account resides, if the mailbox is a linked mailbox. The domain controller in the forest where the user account resides is used to get security information for the account specified by the LinkedMasterAccount parameter. Use the fully qualified domain name (FQDN) of the domain controller that you want to use as the value for this parameter.
@@ -427,6 +413,7 @@ This parameter is required only if you're enabling a linked mailbox.
Type: String
Parameter Sets: LinkedRoomMailbox, Linked
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -436,9 +423,6 @@ Accept wildcard characters: False
```
### -LinkedMasterAccount
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The LinkedMasterAccount parameter specifies the master account in the forest where the user account resides, if the mailbox is a linked mailbox. The master account is the account that the mailbox is linked to. The master account grants access to the mailbox. You can use any value that uniquely identifies the master account. For example:
@@ -454,6 +438,7 @@ This parameter is required only if you're enabling a linked mailbox.
Type: UserIdParameter
Parameter Sets: LinkedRoomMailbox, Linked
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -463,9 +448,6 @@ Accept wildcard characters: False
```
### -LinkedRoom
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The LinkedRoom switch is required to mailbox-enable linked resource mailboxes. You don't need to specify a value with this switch.
@@ -476,6 +458,7 @@ A linked resource mailbox is useful in a scenario where you have an account in a
Type: SwitchParameter
Parameter Sets: LinkedRoomMailbox
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -485,9 +468,6 @@ Accept wildcard characters: False
```
### -PublicFolder
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The PublicFolder switch is required to mailbox-enable public folder mailboxes. You don't need to specify a value with this switch.
@@ -498,6 +478,7 @@ Public folder mailboxes are specially designed mailboxes that store the hierarch
Type: SwitchParameter
Parameter Sets: PublicFolder
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -507,9 +488,6 @@ Accept wildcard characters: False
```
### -Room
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Room switch is required to mailbox-enable room mailboxes. You don't need to specify a value with this switch.
@@ -520,6 +498,7 @@ Room mailboxes are resource mailboxes that are associated with a specific locati
Type: SwitchParameter
Parameter Sets: Room
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -529,9 +508,6 @@ Accept wildcard characters: False
```
### -Shared
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Shared switch is required to connect shared mailboxes. You don't need to specify a value with this switch.
@@ -542,6 +518,7 @@ A shared mailbox is a mailbox where multiple users can log on to access the mail
Type: SwitchParameter
Parameter Sets: Shared
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -551,9 +528,6 @@ Accept wildcard characters: False
```
### -ActiveSyncMailboxPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ActiveSyncMailboxPolicy parameter specifies the mobile device mailbox policy that's applied to the mailbox. You can use any value that uniquely identifies the policy. For example:.
@@ -568,6 +542,7 @@ If you don't use this parameter, the default mobile device mailbox policy is app
Type: MailboxPolicyIdParameter
Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User, Archive, AuditLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -577,9 +552,6 @@ Accept wildcard characters: False
```
### -AddressBookPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The AddressBookPolicy parameter specifies the address book policy that's applied to the mailbox. You can use any value that uniquely identifies the address book policy. For example:
@@ -594,6 +566,7 @@ For more information about address book policies, see [Address book policies in
Type: AddressBookMailboxPolicyIdParameter
Parameter Sets: User
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -603,9 +576,6 @@ Accept wildcard characters: False
```
### -Alias
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
@@ -632,6 +602,7 @@ The Alias parameter never generates or updates the primary email address of a ma
Type: String
Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User, Archive, AuditLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -641,15 +612,13 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Archive switch creates an archive mailbox for an existing user that already has a mailbox. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Archive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -659,9 +628,6 @@ Accept wildcard characters: False
```
### -ArchiveDatabase
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ArchiveDatabase parameter specifies the Exchange database that contains the archive that's associated with this mailbox. You can use any value that uniquely identifies the database. For example:
@@ -674,6 +640,7 @@ The ArchiveDatabase parameter specifies the Exchange database that contains the
Type: DatabaseIdParameter
Parameter Sets: Archive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -683,9 +650,6 @@ Accept wildcard characters: False
```
### -ArchiveGuid
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -694,6 +658,7 @@ This parameter is reserved for internal Microsoft use.
Type: Guid
Parameter Sets: Archive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -703,9 +668,6 @@ Accept wildcard characters: False
```
### -ArchiveName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ArchiveName parameter specifies the name of the archive mailbox. This is the name displayed to users in Outlook on the web (formerly known as Outlook Web App). If the value contains spaces, enclose the value in quotation marks (").
In on-premises Exchange, if you don't use this parameter, the following default values are used based on the version of Exchange:
@@ -722,6 +684,7 @@ In Outlook in Exchange Online, the value of this parameter is ignored. The name
Type: MultiValuedProperty
Parameter Sets: Archive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -731,9 +694,6 @@ Accept wildcard characters: False
```
### -AuditLog
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -742,6 +702,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: AuditLog
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -751,9 +712,6 @@ Accept wildcard characters: False
```
### -AutoExpandingArchive
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AutoExpandingArchive switch enables the auto-expanding archiving feature for the specified mailbox. You don't need to specify a value with this switch.
@@ -769,6 +727,7 @@ After you enable auto-expanding archiving, additional storage space is automatic
Type: SwitchParameter
Parameter Sets: AutoExpandingArchive
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -778,9 +737,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -790,6 +746,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -799,9 +756,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Database parameter specifies the Exchange database that contains the new mailbox. You can use any value that uniquely identifies the database. For example:
@@ -814,6 +768,7 @@ The Database parameter specifies the Exchange database that contains the new mai
Type: DatabaseIdParameter
Parameter Sets: Arbitration, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User, AuditLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -823,9 +778,6 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DisplayName parameter specifies the display name of the mailbox. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
@@ -836,6 +788,7 @@ If you don't use DisplayName parameter, the value of the Name property is used f
Type: String
Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User, Archive, AuditLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -845,9 +798,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -856,6 +806,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User, Archive, AuditLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -865,9 +816,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -876,6 +824,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -885,9 +834,6 @@ Accept wildcard characters: False
```
### -HoldForMigration
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The HoldForMigration switch specifies whether to prevent any client or user, except the Microsoft Exchange Mailbox Replication service (MRS) process, from logging on to a public folder mailbox. You don't need to specify a value with this switch.
@@ -900,6 +846,7 @@ Use this switch only if you plan to migrate legacy Exchange 2010 public folders
Type: SwitchParameter
Parameter Sets: PublicFolder
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -909,9 +856,6 @@ Accept wildcard characters: False
```
### -LinkedCredential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The LinkedCredential parameter specifies the credentials used to access the domain controller that's specified by the LinkedDomainController parameter. This parameter is optional, even if you're enabling a linked mailbox.
@@ -922,6 +866,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: LinkedRoomMailbox, Linked
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -931,9 +876,6 @@ Accept wildcard characters: False
```
### -ManagedFolderMailboxPolicy
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The ManagedFolderMailboxPolicy parameter specifies the managed folder mailbox policy to enable for the mailbox that you create. If you don't specify this parameter, the default managed folder mailbox policy is used.
@@ -942,6 +884,7 @@ The ManagedFolderMailboxPolicy parameter specifies the managed folder mailbox po
Type: MailboxPolicyIdParameter
Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -951,9 +894,6 @@ Accept wildcard characters: False
```
### -ManagedFolderMailboxPolicyAllowed
-
-> Applicable: Exchange Server 2010
-
This parameter is available in Exchange Server 2010.
The ManagedFolderMailboxPolicyAllowed switch specifies whether to bypass the warning that messaging records management (MRM) features aren't supported for clients using versions of Outlook earlier than Office Outlook 2007. You don't need to specify a value with this switch.
@@ -966,6 +906,7 @@ Outlook 2003 Service Pack 3 clients are supported but are provided limited funct
Type: SwitchParameter
Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -975,9 +916,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
@@ -988,6 +926,7 @@ If you use the PrimarySmtpAddress parameter to specify the primary email address
Type: SmtpAddress
Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User, Archive, AuditLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -997,9 +936,6 @@ Accept wildcard characters: False
```
### -RemoteArchive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RemoteArchive switch specifies that a remote archive mailbox is created for this mailbox. A remote archive exists in the cloud-based service. You don't need to specify a value with this switch.
@@ -1010,6 +946,7 @@ You need to use this parameter with the ArchiveDomain parameter, and you can't u
Type: SwitchParameter
Parameter Sets: RemoteArchive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -1019,9 +956,6 @@ Accept wildcard characters: False
```
### -RetentionPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RetentionPolicy parameter specifies the retention policy that's applied to the mailbox. You can use any value that uniquely identifies the policy. For example:
@@ -1036,6 +970,7 @@ Retention policies consist of tags that are applied to mailbox folders and mail
Type: MailboxPolicyIdParameter
Parameter Sets: Arbitration, RemoteArchive, Discovery, Equipment, LinkedRoomMailbox, Linked, PublicFolder, Room, Shared, User, Archive, AuditLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -1045,9 +980,6 @@ Accept wildcard characters: False
```
### -RoleAssignmentPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RoleAssignmentPolicy parameter specifies the management role assignment policy that's assigned to the mailbox. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -1060,6 +992,7 @@ If you don't use this parameter, the default role assignment policy is used. If
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1069,15 +1002,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md b/exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
rename to exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md
index cf97201621..94f1b1b2d7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
+++ b/exchange/exchange-ps/exchange/Enable-MailboxQuarantine.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-mailboxquarantine
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-MailboxQuarantine
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-mailboxquarantine
-schema: 2.0.0
-title: Enable-MailboxQuarantine
+ms.reviewer:
---
# Enable-MailboxQuarantine
@@ -68,9 +67,6 @@ This example quarantines the mailbox for the user Brian Johnson.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013
-
The Identity parameter specifies the mailbox that you want to quarantine. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -88,8 +84,9 @@ You can't use this parameter with the Database parameter.
```yaml
Type: GeneralMailboxIdParameter
-Parameter Sets: MailboxIdentity, MailboxOrMailUserIdentity
+Parameter Sets: MailboxIdentity
Aliases:
+Applicable: Exchange Server 2013
Required: True
Position: 1
@@ -98,10 +95,20 @@ Accept pipeline input: True
Accept wildcard characters: False
```
-### -Database
+```yaml
+Type: GeneralMailboxOrMailUserIdParameter
+Parameter Sets: MailboxOrMailUserIdentity
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
-> Applicable: Exchange Server 2016, Exchange Server 2019
+Required: True
+Position: 1
+Default value: None
+Accept pipeline input: True
+Accept wildcard characters: False
+```
+### -Database
The Database parameter specifies the database that contains the mailboxes you want to quarantine. You can use any value that uniquely identifies the database. For example:
- Name
@@ -116,6 +123,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: StoreMailboxIdentity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -125,9 +133,6 @@ Accept wildcard characters: False
```
### -StoreMailboxIdentity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The StoreMailboxIdentity parameter specifies the mailbox that you want to quarantine when you use the Database parameter.
You identify the mailbox by its GUID value. You can find the GUID value by using the Get-Mailbox or Get-MailboxStatistics cmdlets.
@@ -138,6 +143,7 @@ You can't use this parameter with the Identity parameter.
Type: StoreMailboxIdParameter
Parameter Sets: StoreMailboxIdentity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -147,9 +153,6 @@ Accept wildcard characters: False
```
### -AllowMigration
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AllowMigration switch allows a quarantined mailbox to be moved to another mailbox database or to the cloud. You don't need to specify a value with this switch.
Moving a mailbox is one method of correcting data corruption that's required before releasing the mailbox from quarantine.
@@ -158,6 +161,7 @@ Moving a mailbox is one method of correcting data corruption that's required bef
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -167,9 +171,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -181,6 +182,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -190,9 +192,6 @@ Accept wildcard characters: False
```
### -Duration
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Duration parameter specifies how long the mailbox should remain quarantined. The default value is 24 hours.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -201,6 +200,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -210,15 +210,13 @@ Accept wildcard characters: False
```
### -QuarantineReason
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The QuarantineReason parameter specifies why you quarantined the mailbox. The maximum length is 255 characters. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: StoreMailboxIdentity, MailboxOrMailUserIdentity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -228,15 +226,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md b/exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
rename to exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md
index b323fd1b21..d671effeae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
+++ b/exchange/exchange-ps/exchange/Enable-MalwareFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-malwarefilterrule
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Enable-MalwareFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-malwarefilterrule
-schema: 2.0.0
-title: Enable-MalwareFilterRule
+ms.reviewer:
---
# Enable-MalwareFilterRule
@@ -44,15 +43,13 @@ This example enables the disabled malware filter rule named Contoso Recipients.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the malware filter rule that you want to enable. You can use any value that uniquely identifies the rule. For example, you can use the name, GUID or distinguished name (DN) of the malware filter rule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -62,9 +59,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -74,6 +68,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -83,9 +78,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -94,6 +86,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -103,15 +96,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md b/exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
rename to exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md
index e498da9e61..642a0ec9b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
+++ b/exchange/exchange-ps/exchange/Enable-MetaCacheDatabase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-metacachedatabase
applicable: Exchange Server 2019
+title: Enable-MetaCacheDatabase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-metacachedatabase
-schema: 2.0.0
-title: Enable-MetaCacheDatabase
+ms.reviewer:
---
# Enable-MetaCacheDatabase
@@ -43,9 +42,6 @@ This example enables the metacache database on the Exchange server named Mailbox
## PARAMETERS
### -Server
-
-> Applicable: Exchange Server 2019
-
The Server parameter specifies the Mailbox server where you want to enable the metacache database. You can use any value that uniquely identifies the server. For example:
- Name
@@ -59,6 +55,7 @@ You can specify multiple values separated by commas. If the value contains space
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: True
Position: Named
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -80,6 +74,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -89,15 +84,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md b/exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md
rename to exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md
index 0737dacb31..23f178be9e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md
+++ b/exchange/exchange-ps/exchange/Enable-OrganizationCustomization.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-organizationcustomization
applicable: Exchange Online, Exchange Online Protection
+title: Enable-OrganizationCustomization
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-organizationcustomization
-schema: 2.0.0
-title: Enable-OrganizationCustomization
+ms.reviewer:
---
# Enable-OrganizationCustomization
@@ -57,9 +56,6 @@ This example runs the command as required.
## PARAMETERS
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -69,6 +65,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -78,15 +75,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md b/exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md
rename to exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md
index f3108d903a..f2706fde72 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md
+++ b/exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-outlookanywhere
applicable: Exchange Server 2010
+title: Enable-OutlookAnywhere
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-outlookanywhere
-schema: 2.0.0
-title: Enable-OutlookAnywhere
+ms.reviewer:
---
# Enable-OutlookAnywhere
@@ -85,9 +84,6 @@ This example enables the Exchange Client Access server for Outlook Anywhere. The
## PARAMETERS
### -ClientAuthenticationMethod
-
-> Applicable: Exchange Server 2010
-
The ClientAuthenticationMethod parameter specifies the authentication method that the Autodiscover service provides to the Outlook Anywhere clients to authenticate to the Client Access server. Valid values are:
- Basic
@@ -101,6 +97,7 @@ Although this parameter only allows setting one authentication method, the comma
Type: AuthenticationMethod
Parameter Sets: CustomIdentity
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -110,9 +107,6 @@ Accept wildcard characters: False
```
### -DefaultAuthenticationMethod
-
-> Applicable: Exchange Server 2010
-
The DefaultAuthenticationMethod parameter specifies whether to set both the ClientAuthenticationMethod and IISAuthenticationMethods parameters to the same authentication value.
When you set an authentication value by using the DefaultAuthenticationMethod parameter, you force the specified authentication method to be used on the /rpc virtual directory in Internet Information Services (IIS). Valid values are:
@@ -126,6 +120,7 @@ If the DefaultAuthenticationMethod parameter is specified, neither the ClientAut
Type: AuthenticationMethod
Parameter Sets: DefaultIdentity
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -135,15 +130,13 @@ Accept wildcard characters: False
```
### -ExternalHostname
-
-> Applicable: Exchange Server 2010
-
The ExternalHostname parameter specifies the external host name to use in the Outlook profiles for users enabled for Outlook Anywhere.
```yaml
Type: Hostname
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -153,15 +146,13 @@ Accept wildcard characters: False
```
### -SSLOffloading
-
-> Applicable: Exchange Server 2010
-
The SSLOffloading parameter specifies whether the Client Access server requires Secure Sockets Layer (SSL). This value should be set only to $true when an SSL hardware solution is running in front of the Client Access server.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -171,9 +162,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -183,6 +171,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -192,15 +181,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -210,9 +197,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionFlags
-
-> Applicable: Exchange Server 2010
-
The ExtendedProtectionFlags parameter is used to customize the options you use if you're using Extended Protection for Authentication. The possible values are:
- None: Default setting.
@@ -225,6 +209,7 @@ The ExtendedProtectionFlags parameter is used to customize the options you use i
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -234,9 +219,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionSPNList
-
-> Applicable: Exchange Server 2010
-
The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the specified virtual directory.
The possible values are:
@@ -248,6 +230,7 @@ The possible values are:
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -257,9 +240,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionTokenChecking
-
-> Applicable: Exchange Server 2010
-
The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the specified Exchange virtual directory. Extended Protection for Authentication isn't enabled by default. The available settings are:
- None Extended Protection for Authentication won't be used. Connections between the client and Exchange won't use Extended Protection for Authentication on this virtual directory. This is the default setting.
@@ -277,6 +257,7 @@ To learn more about Extended Protection for Authentication, see [Understanding E
Type: ExtendedProtectionTokenCheckingMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -286,9 +267,6 @@ Accept wildcard characters: False
```
### -IISAuthenticationMethods
-
-> Applicable: Exchange Server 2010
-
The IISAuthenticationMethods parameter specifies the authentication method that's enabled on the /rpc virtual directory in IIS. You can set the virtual directory to allow Basic authentication or NTLM authentication. Alternatively, you can also set the virtual directory to allow both Basic and NTLM authentication. All other authentication methods are disabled.
You may want to enable both Basic and NTLM authentication if you're using the IIS virtual directory with multiple applications that require different authentication methods.
@@ -301,6 +279,7 @@ For more information about configuring this parameter with multiple values, see
Type: MultiValuedProperty
Parameter Sets: CustomIdentity
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -310,9 +289,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
The Server parameter specifies the Client Access server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -324,6 +300,7 @@ The Server parameter specifies the Client Access server where you want to run th
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -333,15 +310,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
rename to exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md
index 1224f593ff..63e2c39801 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-outlookprotectionrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Enable-OutlookProtectionRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-outlookprotectionrule
-schema: 2.0.0
-title: Enable-OutlookProtectionRule
+ms.reviewer:
---
# Enable-OutlookProtectionRule
@@ -48,15 +47,13 @@ This example enables the Outlook protection rule Project Contoso.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name of the rule being enabled.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -66,9 +63,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -78,6 +72,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -87,9 +82,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -98,6 +90,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -107,15 +100,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md b/exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
rename to exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md
index 468851c7ae..e23369448c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
+++ b/exchange/exchange-ps/exchange/Enable-PushNotificationProxy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-pushnotificationproxy
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-PushNotificationProxy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-pushnotificationproxy
-schema: 2.0.0
-title: Enable-PushNotificationProxy
+ms.reviewer:
---
# Enable-PushNotificationProxy
@@ -55,9 +54,6 @@ This example enables the push notification proxy in the on-premises Exchange org
## PARAMETERS
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -67,6 +63,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -76,15 +73,13 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Organization parameter specifies the domain name of the Microsoft 365 organization. For example, contoso.onmicrosoft.com.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -94,15 +89,13 @@ Accept wildcard characters: False
```
### -Uri
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Uri parameter specifies the push notification service endpoint in Microsoft 365. The default value is .
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -112,15 +105,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md b/exchange/exchange-ps/exchange/Enable-RemoteMailbox.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
rename to exchange/exchange-ps/exchange/Enable-RemoteMailbox.md
index a6256027c7..e2ca574784 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
+++ b/exchange/exchange-ps/exchange/Enable-RemoteMailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-remotemailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-RemoteMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-remotemailbox
-schema: 2.0.0
-title: Enable-RemoteMailbox
+ms.reviewer:
---
# Enable-RemoteMailbox
@@ -135,9 +134,6 @@ To mail-enable an on-premises user, create the associated mailbox in the service
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the existing on-premises user. You can use any value that uniquely identifies the user. For example:
- ADObjectID
@@ -152,6 +148,7 @@ The Identity parameter specifies the identity of the existing on-premises user.
Type: UserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -161,9 +158,6 @@ Accept wildcard characters: False
```
### -Equipment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Equipment switch specifies that the mailbox in the service should be created as an equipment resource mailbox. You don't need to specify a value with this switch.
Equipment mailboxes are resource mailboxes that aren't associated with a specific location (for example, vehicles or computers).
@@ -174,6 +168,7 @@ You can't use this switch with the Room or Shared switches.
Type: SwitchParameter
Parameter Sets: Equipment, Shared
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -183,9 +178,6 @@ Accept wildcard characters: False
```
### -Room
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Room switch specifies that the mailbox in the service should be created as a room resource mailbox. You don't need to specify a value with this switch.
You can't use this switch with the Equipment or Shared switches.
@@ -194,6 +186,7 @@ You can't use this switch with the Equipment or Shared switches.
Type: SwitchParameter
Parameter Sets: Room
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -203,9 +196,6 @@ Accept wildcard characters: False
```
### -Shared
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
**Note**: This switch is available only in Exchange 2013 CU21 or later and Exchange 2016 CU10 or later. To use this switch, you also need to run setup.exe /PrepareAD. For more information, see [KB4133605](https://support.microsoft.com/help/4133605).
The Shared switch specifies that the mailbox in the service should be created as a shared mailbox. You don't need to specify a value with this switch.
@@ -216,6 +206,7 @@ You can't use this switch with the Room or Equipment switches.
Type: SwitchParameter
Parameter Sets: Shared
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -225,15 +216,13 @@ Accept wildcard characters: False
```
### -ACLableSyncedObjectEnabled
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ACLableSyncedObjectEnabled switch specifies whether the remote mailbox is an ACLableSyncedMailboxUser. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -243,9 +232,6 @@ Accept wildcard characters: False
```
### -Alias
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
The Alias value can contain letters, numbers and the following characters:
@@ -270,6 +256,7 @@ The Alias parameter never generates or updates the primary email address of a ma
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -279,15 +266,13 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Archive switch creates an archive mailbox for an existing cloud-based user that already has a mailbox. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Archive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -297,9 +282,6 @@ Accept wildcard characters: False
```
### -ArchiveName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ArchiveName parameter specifies the name of the archive mailbox. This is the name displayed to users in Outlook on the web (formerly known as Outlook Web App). If the value contains spaces, enclose the value in quotation marks (").
If you don't use this parameter, the following default values are used based on the version of Exchange:
@@ -314,6 +296,7 @@ In Outlook, the value of this parameter is ignored. The name of the archive mail
Type: MultiValuedProperty
Parameter Sets: Archive
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -323,9 +306,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -335,6 +315,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -344,15 +325,13 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DisplayName parameter specifies the display name for the mailbox that's created in the service. The display name is visible in the Exchange admin center, address lists and Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -362,15 +341,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -380,15 +357,13 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
```yaml
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -398,15 +373,13 @@ Accept wildcard characters: False
```
### -RemoteRoutingAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RemoteRoutingAddress parameter specifies the SMTP address of the mailbox in the service that this user is associated with.
```yaml
Type: ProxyAddress
Parameter Sets: Default, Room, Equipment, Shared
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -416,15 +389,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md
rename to exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md
index 56e3f4dd50..9bf1aa79ac 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/exchange/Enable-ReportSubmissionRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-reportsubmissionrule
applicable: Exchange Online
+title: Enable-ReportSubmissionRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-reportsubmissionrule
-schema: 2.0.0
-title: Enable-ReportSubmissionRule
+ms.reviewer:
---
# Enable-ReportSubmissionRule
@@ -43,15 +42,13 @@ This example enables the report submission rule if it's already disabled.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the report submission rule that you want to enable. The default rule is named DefaultReportSubmissionRule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
@@ -61,9 +58,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -73,6 +67,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -82,15 +77,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md
rename to exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md
index f90229ee73..2642212149 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-safeattachmentrule
applicable: Exchange Online
+title: Enable-SafeAttachmentRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-safeattachmentrule
-schema: 2.0.0
-title: Enable-SafeAttachmentRule
+ms.reviewer:
---
# Enable-SafeAttachmentRule
@@ -45,9 +44,6 @@ This example enables the disabled safe attachment rule named Marketing Departmen
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the disabled safe attachment rule that you want to enable.
You can use any value that uniquely identifies the rule. For example:
@@ -60,6 +56,7 @@ You can use any value that uniquely identifies the rule. For example:
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -81,6 +75,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -90,15 +85,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md b/exchange/exchange-ps/exchange/Enable-SafeLinksRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md
rename to exchange/exchange-ps/exchange/Enable-SafeLinksRule.md
index c328540126..1314b22664 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md
+++ b/exchange/exchange-ps/exchange/Enable-SafeLinksRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-safelinksrule
applicable: Exchange Online
+title: Enable-SafeLinksRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-safelinksrule
-schema: 2.0.0
-title: Enable-SafeLinksRule
+ms.reviewer:
---
# Enable-SafeLinksRule
@@ -45,9 +44,6 @@ This example enables the disabled Safe Links rule named Marketing Department URL
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the disabled Safe Links rule that you want to enable.
You can use any value that uniquely identifies the rule. For example:
@@ -60,6 +56,7 @@ You can use any value that uniquely identifies the rule. For example:
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -81,6 +75,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -90,15 +85,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md b/exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
rename to exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md
index 2e4d132aa7..206921ec6f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
+++ b/exchange/exchange-ps/exchange/Enable-ServiceEmailChannel.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-serviceemailchannel
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-ServiceEmailChannel
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-serviceemailchannel
-schema: 2.0.0
-title: Enable-ServiceEmailChannel
+ms.reviewer:
---
# Enable-ServiceEmailChannel
@@ -60,9 +59,6 @@ This example enables the .NET service channel for the user Tony Smith.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the user for which you want to enable the .NET service channel. The user specified must be a valid user in Active Directory who has an Exchange mailbox.
You can use any value that uniquely identifies the mailbox. For example:
@@ -82,6 +78,7 @@ You can use any value that uniquely identifies the mailbox. For example:
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -91,9 +88,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -103,6 +97,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -112,15 +107,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,15 +123,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md b/exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md
rename to exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md
index 98ea3d22e8..84502bb3b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md
+++ b/exchange/exchange-ps/exchange/Enable-SmtpDaneInbound.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-smtpdaneinbound
applicable: Exchange Online
+title: Enable-SmtpDaneInbound
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-smtpdaneinbound
-schema: 2.0.0
-title: Enable-SmtpDaneInbound
+ms.reviewer:
---
# Enable-SmtpDaneInbound
@@ -45,15 +44,13 @@ This example enables SMTP DANE for mail sent to contoso.com.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Online
-
The DomainName parameter specifies the accepted domain in the Exchange Online organization where you want to enable SMTP DANE (for example, contoso.com). Use the Get-AcceptedDomain cmdlet to see the accepted domains in the organization.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
@@ -63,15 +60,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -81,15 +76,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md b/exchange/exchange-ps/exchange/Enable-SweepRule.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
rename to exchange/exchange-ps/exchange/Enable-SweepRule.md
index db15150448..a5d16d3d5f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
+++ b/exchange/exchange-ps/exchange/Enable-SweepRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-sweeprule
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Enable-SweepRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-sweeprule
-schema: 2.0.0
-title: Enable-SweepRule
+ms.reviewer:
---
# Enable-SweepRule
@@ -52,9 +51,6 @@ This example enables all Sweep rules in the specified mailbox.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the Sweep rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- RuleId property (for example, x2hlsdpGmUifjFgxxGIOJw==).
@@ -65,6 +61,7 @@ The Identity parameter specifies the Sweep rule that you want to enable. You can
Type: SweepRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -86,6 +80,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -106,6 +98,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that contains the rule you want to enable. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -135,6 +125,7 @@ The Mailbox parameter specifies the mailbox that contains the rule you want to e
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -144,15 +135,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md b/exchange/exchange-ps/exchange/Enable-TransportAgent.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
rename to exchange/exchange-ps/exchange/Enable-TransportAgent.md
index 1c9fd5b5c9..1985292cfa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
+++ b/exchange/exchange-ps/exchange/Enable-TransportAgent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-transportagent
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Enable-TransportAgent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-transportagent
-schema: 2.0.0
-title: Enable-TransportAgent
+ms.reviewer:
---
# Enable-TransportAgent
@@ -45,15 +44,13 @@ This example enables a fictitious application named Test App in the Transport se
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the display name of the transport agent to be enabled. The length of the name can't exceed 64 characters.
```yaml
Type: TransportAgentObjectId
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -63,9 +60,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -75,6 +69,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -84,9 +79,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -95,6 +87,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -104,9 +97,6 @@ Accept wildcard characters: False
```
### -TransportService
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
- Hub for the Transport service on Mailbox servers.
@@ -119,6 +109,7 @@ The TransportService parameter specifies the transport service that you want to
Type: TransportService
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -128,15 +119,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md b/exchange/exchange-ps/exchange/Enable-TransportRule.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
rename to exchange/exchange-ps/exchange/Enable-TransportRule.md
index fad19405e6..4f9a620693 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
+++ b/exchange/exchange-ps/exchange/Enable-TransportRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-transportrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Enable-TransportRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-transportrule
-schema: 2.0.0
-title: Enable-TransportRule
+ms.reviewer:
---
# Enable-TransportRule
@@ -54,9 +53,6 @@ This example enables the transport rule named "Require approval of messages to c
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -67,6 +63,7 @@ The Identity parameter specifies the rule that you want to enable. You can use a
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -76,9 +73,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -88,6 +82,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -97,9 +92,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -110,6 +102,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -119,9 +112,6 @@ Accept wildcard characters: False
```
### -Mode
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Mode parameter specifies how the rule operates after it's enabled. Valid values are:
- Audit: The actions that the rule would have taken are written to the message tracking log, but no any action is taken on the message that would impact delivery.
@@ -134,6 +124,7 @@ The value that has already been set in the rule will be persevered, unless -Mode
Type: RuleMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -143,15 +134,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md b/exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md
rename to exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md
index fdf6d70163..b5a6029718 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md
+++ b/exchange/exchange-ps/exchange/Enable-UMAutoAttendant.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-umautoattendant
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Enable-UMAutoAttendant
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-umautoattendant
-schema: 2.0.0
-title: Enable-UMAutoAttendant
+ms.reviewer:
---
# Enable-UMAutoAttendant
@@ -46,15 +45,13 @@ This example enables the UM auto attendant MyUMAutoAttendant.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for the UM auto attendant being enabled.
```yaml
Type: UMAutoAttendantIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -64,9 +61,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -76,6 +70,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -85,15 +80,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -103,15 +96,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md
rename to exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md
index 1d442c6278..871ebf54fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/exchange/Enable-UMCallAnsweringRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-umcallansweringrule
applicable: Exchange Server 2013, Exchange Server 2016
+title: Enable-UMCallAnsweringRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-umcallansweringrule
-schema: 2.0.0
-title: Enable-UMCallAnsweringRule
+ms.reviewer:
---
# Enable-UMCallAnsweringRule
@@ -63,15 +62,13 @@ This example enables the call answering rule MyUMCallAnsweringRule in the mailbo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the UM call answering rule in a UM-enabled mailbox that's to be enabled.
```yaml
Type: UMCallAnsweringRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -81,9 +78,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -93,6 +87,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -102,15 +97,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -120,9 +113,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Mailbox parameter specifies the UM-enabled mailbox that contains the UM call answering rule. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -142,6 +132,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -151,15 +142,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md b/exchange/exchange-ps/exchange/Enable-UMIPGateway.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md
rename to exchange/exchange-ps/exchange/Enable-UMIPGateway.md
index a26ffb5377..2b49427750 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md
+++ b/exchange/exchange-ps/exchange/Enable-UMIPGateway.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-umipgateway
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Enable-UMIPGateway
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-umipgateway
-schema: 2.0.0
-title: Enable-UMIPGateway
+ms.reviewer:
---
# Enable-UMIPGateway
@@ -48,15 +47,13 @@ This example enables the UM IP gateway MyUMIPGateway.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for the UM IP gateway being enabled. This parameter is the directory object ID for the UM IP gateway.
```yaml
Type: UMIPGatewayIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -66,9 +63,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -78,6 +72,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -87,15 +82,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -105,15 +98,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md b/exchange/exchange-ps/exchange/Enable-UMMailbox.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md
rename to exchange/exchange-ps/exchange/Enable-UMMailbox.md
index 67cdd97fb3..64d7a8d5d7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md
+++ b/exchange/exchange-ps/exchange/Enable-UMMailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-ummailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Enable-UMMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-ummailbox
-schema: 2.0.0
-title: Enable-UMMailbox
+ms.reviewer:
---
# Enable-UMMailbox
@@ -84,9 +83,6 @@ This example enables Unified Messaging on a SIP-enabled mailbox for tonysmith@co
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the mailbox that you want to enable for Unified Messaging. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -104,6 +100,7 @@ The Identity parameter specifies the mailbox that you want to enable for Unified
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -113,9 +110,6 @@ Accept wildcard characters: False
```
### -UMMailboxPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMMailboxPolicy parameter specifies the UM mailbox policy that you want to associate with the mailbox. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -124,8 +118,9 @@ The UMMailboxPolicy parameter specifies the UM mailbox policy that you want to a
```yaml
Type: MailboxPolicyIdParameter
-Parameter Sets: Identity, CloudVoiceMail
+Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -134,10 +129,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -AutomaticSpeechRecognitionEnabled
+```yaml
+Type: MailboxPolicyIdParameter
+Parameter Sets: CloudVoiceMail
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -AutomaticSpeechRecognitionEnabled
The AutomaticSpeechRecognitionEnabled parameter specifies whether to enable Automatic Speech Recognition (ASR) for the UM mailbox. Valid values are:
- $true: ASR is enabled for the mailbox. This is the default value. ASR is available only if the user's specified preferred language is installed.
@@ -147,6 +152,7 @@ The AutomaticSpeechRecognitionEnabled parameter specifies whether to enable Auto
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -156,9 +162,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -168,6 +171,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -177,15 +181,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -195,15 +197,13 @@ Accept wildcard characters: False
```
### -EnableCloudVoiceMail
-
-> Applicable: Exchange Server 2016
-
The EnableCloudVoiceMail switch specifies whether to enable the mailbox for UM in Skype for Business Online. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: CloudVoiceMail
Aliases:
+Applicable: Exchange Server 2016
Required: True
Position: Named
@@ -213,9 +213,6 @@ Accept wildcard characters: False
```
### -Extensions
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Extensions parameter specifies the extension number for the user. Either a single extension number or an array of telephone number extensions can be specified. The user's extension must be unique to the UM dial plan.
If you don't use this parameter, the command attempts to use a default telephone number value for the user. If you're using a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) or E.164 dial plan, you also need to use the SIPResourceIdentifier parameter.
@@ -224,6 +221,7 @@ If you don't use this parameter, the command attempts to use a default telephone
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -233,9 +231,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -247,6 +242,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -256,15 +252,13 @@ Accept wildcard characters: False
```
### -NotifyEmail
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The NotifyEmail parameter specifies the email address where the Unified Messaging welcome message is sent. By default, the message is sent to the user's SMTP email address.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -274,15 +268,13 @@ Accept wildcard characters: False
```
### -PilotNumber
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The PilotNumber parameter specifies the subscriber access number users can dial to gain access to their mailboxes. The default value is the subscriber access number that's specified on the UM dial plan.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -292,9 +284,6 @@ Accept wildcard characters: False
```
### -PIN
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The PIN parameter specifies the value for the initial PIN that's used for the UM mailbox. The PIN is checked against the UM mailbox policy rules. The PIN value must be from 4 through 24 numeric characters.
If you don't use this parameter, a system-generated PIN is sent to the user. By default, the PIN generated by the system contains six numeric characters.
@@ -303,6 +292,7 @@ If you don't use this parameter, a system-generated PIN is sent to the user. By
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -312,9 +302,6 @@ Accept wildcard characters: False
```
### -PINExpired
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The PINExpired parameter specifies whether the PIN is treated as expired. If the PIN isn't supplied, the PIN is treated as expired and users are prompted to reset their PIN the next time they log on.
- $true: The user is required to reset their PIN the next time they log on.
@@ -324,6 +311,7 @@ The PINExpired parameter specifies whether the PIN is treated as expired. If the
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -333,9 +321,6 @@ Accept wildcard characters: False
```
### -SendWelcomeMail
-
-> Applicable: Exchange Server 2016
-
The SendWelcomeMail parameter specifies whether you want to send a welcome message after the mailbox has been enabled for UM. Valid values are:
- $true: Send the welcome to UM message.
@@ -345,6 +330,7 @@ The SendWelcomeMail parameter specifies whether you want to send a welcome messa
Type: Boolean
Parameter Sets: CloudVoiceMail
Aliases:
+Applicable: Exchange Server 2016
Required: False
Position: Named
@@ -354,15 +340,13 @@ Accept wildcard characters: False
```
### -SIPResourceIdentifier
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The SIPResourceIdentifier parameter specifies the SIP address or E.164 address for the user. This property is compared to the URI type defined on the UM dial plan.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -372,9 +356,6 @@ Accept wildcard characters: False
```
### -ValidateOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. You don't need to specify a value with this switch.
No changes are made when the ValidateOnly switch is used.
@@ -383,6 +364,7 @@ No changes are made when the ValidateOnly switch is used.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -392,15 +374,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md b/exchange/exchange-ps/exchange/Enable-UMServer.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md
rename to exchange/exchange-ps/exchange/Enable-UMServer.md
index 8ee6d80f46..01417d0e76 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md
+++ b/exchange/exchange-ps/exchange/Enable-UMServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-umserver
applicable: Exchange Server 2010
+title: Enable-UMServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-umserver
-schema: 2.0.0
-title: Enable-UMServer
+ms.reviewer:
---
# Enable-UMServer
@@ -48,15 +47,13 @@ This example enables Unified Messaging on the Unified Messaging server named MyU
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the identifier for the Unified Messaging server being enabled. This is the directory object ID for the UM server.
```yaml
Type: UMServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: 1
@@ -66,9 +63,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -78,6 +72,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -87,15 +82,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -105,15 +98,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md b/exchange/exchange-ps/exchange/Enable-UMService.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md
rename to exchange/exchange-ps/exchange/Enable-UMService.md
index 3207726463..d0441b4357 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md
+++ b/exchange/exchange-ps/exchange/Enable-UMService.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/enable-umservice
applicable: Exchange Server 2013, Exchange Server 2016
+title: Enable-UMService
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/enable-umservice
-schema: 2.0.0
-title: Enable-UMService
+ms.reviewer:
---
# Enable-UMService
@@ -50,9 +49,6 @@ This example enables Unified Messaging on the UM server MyUMServer.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the Exchange 2010 UM server that you want to enable. You can use any value that uniquely identifies the UM server. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the Exchange 2010 UM server that you want to en
Type: UMServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: True
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -85,6 +79,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -94,15 +89,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -112,15 +105,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md b/exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md
rename to exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md
index 3868bcd8ea..8da13825b6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md
+++ b/exchange/exchange-ps/exchange/Execute-AzureADLabelSync.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/execute-azureadlabelsync
applicable: Security & Compliance
+title: Execute-AzureADLabelSync
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/execute-azureadlabelsync
-schema: 2.0.0
-title: Execute-AzureADLabelSync
+ms.reviewer:
---
# Execute-AzureADLabelSync
diff --git a/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md b/exchange/exchange-ps/exchange/Expedite-Delicensing.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md
rename to exchange/exchange-ps/exchange/Expedite-Delicensing.md
index f490e9a900..f5c2af5041 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md
+++ b/exchange/exchange-ps/exchange/Expedite-Delicensing.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/expedite-delicensing
applicable: Exchange Online
+title: Expedite-Delicensing
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/expedite-delicensing
-schema: 2.0.0
-title: Expedite-Delicensing
+ms.reviewer:
---
# Expedite-Delicensing
@@ -41,9 +40,6 @@ This example ends the delay for the mailbox license removal request on the speci
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox with a pending mailbox license removal request.
You can use any value that uniquely identifies the mailbox. For example:
@@ -60,6 +56,7 @@ You can use any value that uniquely identifies the mailbox. For example:
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md b/exchange/exchange-ps/exchange/Export-ActiveSyncLog.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
rename to exchange/exchange-ps/exchange/Export-ActiveSyncLog.md
index 044fde6d46..2af091f5e0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
+++ b/exchange/exchange-ps/exchange/Export-ActiveSyncLog.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-activesynclog
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Export-ActiveSyncLog
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-activesynclog
-schema: 2.0.0
-title: Export-ActiveSyncLog
+ms.reviewer:
---
# Export-ActiveSyncLog
@@ -65,15 +64,13 @@ This example exports the Exchange ActiveSync log for the date range 02/01/18 to
## PARAMETERS
### -Filename
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Filename parameter specifies the name of the input file.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -83,9 +80,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -95,6 +89,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -104,15 +99,13 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The EndDate parameter specifies the end date of the date range of the report.
```yaml
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -122,9 +115,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -133,6 +123,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -142,15 +133,13 @@ Accept wildcard characters: False
```
### -OutputPath
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OutputPath parameter specifies the name and location for the output file.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -160,15 +149,13 @@ Accept wildcard characters: False
```
### -OutputPrefix
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OutputPrefix parameter specifies a prefix to append to the name of the output file.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -178,15 +165,13 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The StartDate parameter specifies the start date of the date range for the report.
```yaml
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -196,9 +181,6 @@ Accept wildcard characters: False
```
### -UseGMT
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The UseGMT switch specifies that Coordinated Universal Time (Greenwich Mean Time) is used for the time in the report output. You don't need to specify a value with this switch.
If you don't use this switch, local time is used.
@@ -207,6 +189,7 @@ If you don't use this switch, local time is used.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -216,15 +199,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md b/exchange/exchange-ps/exchange/Export-ActivityExplorerData.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md
rename to exchange/exchange-ps/exchange/Export-ActivityExplorerData.md
index 9da4987e32..78b9dd23dd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md
+++ b/exchange/exchange-ps/exchange/Export-ActivityExplorerData.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata
applicable: Security & Compliance
+title: Export-ActivityExplorerData
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata
-schema: 2.0.0
-title: Export-ActivityExplorerData
+ms.reviewer:
---
# Export-ActivityExplorerData
@@ -220,9 +219,6 @@ This example exports up to 100 records for the specified date range in JSON form
## PARAMETERS
### -EndTime
-
-> Applicable: Security & Compliance
-
The EndTime parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -231,6 +227,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -240,9 +237,6 @@ Accept wildcard characters: False
```
### -OutputFormat
-
-> Applicable: Security & Compliance
-
The OutputFormat parameter specifies the output format. Valid values are:
- Csv
@@ -253,6 +247,7 @@ Type: String
Parameter Sets: (All)
Aliases:
Accepted values: csv, json
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -262,9 +257,6 @@ Accept wildcard characters: False
```
### -StartTime
-
-> Applicable: Security & Compliance
-
The StartTime parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -273,6 +265,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -282,9 +275,6 @@ Accept wildcard characters: False
```
### -Filter1
-
-> Applicable: Security & Compliance
-
The Filter1 parameter filters the data to export. This parameter takes a minimum of two values as input: a filter name and at least one filter value. For example, `@("Activity", "LabelApplied")` returns records with the activity value `LabelApplied`.
If you specify multiple filter values for the same parameter, OR behavior is used. For example, `@("Activity", "LabelApplied", "LabelRemoved")` returns records with the activity values `LabelApplied` or `LabelRemoved`.
@@ -297,6 +287,7 @@ If you use this parameter with other filter parameters, AND behavior is used acr
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -306,9 +297,6 @@ Accept wildcard characters: False
```
### -Filter2
-
-> Applicable: Security & Compliance
-
The Filter2 parameter filters the data to export. This parameter has the same syntax requirements as the Filter1 parameter, the same OR behavior for multiple values in the same parameter, and the same AND behavior for multiple filter parameters.
Use this parameter only if you're also using the Filter1 parameter in the same command.
@@ -317,6 +305,7 @@ Use this parameter only if you're also using the Filter1 parameter in the same c
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -326,9 +315,6 @@ Accept wildcard characters: False
```
### -Filter3
-
-> Applicable: Security & Compliance
-
The Filter3 parameter filters the data to export. This parameter has the same syntax requirements as the Filter1 parameter, the same OR behavior for multiple values in the same parameter, and the same AND behavior for multiple filter parameters.
Use this parameter only if you're also using the Filter2 and Filter1 parameters in the same command.
@@ -337,6 +323,7 @@ Use this parameter only if you're also using the Filter2 and Filter1 parameters
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -346,9 +333,6 @@ Accept wildcard characters: False
```
### -Filter4
-
-> Applicable: Security & Compliance
-
The Filter4 parameter filters the data to export. This parameter has the same syntax requirements as the Filter1 parameter, the same OR behavior for multiple values in the same parameter, and the same AND behavior for multiple filter parameters.
Use this parameter only if you're also using the Filter3, Filter2, and Filter1 parameters in the same command.
@@ -357,6 +341,7 @@ Use this parameter only if you're also using the Filter3, Filter2, and Filter1 p
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -366,9 +351,6 @@ Accept wildcard characters: False
```
### -Filter5
-
-> Applicable: Security & Compliance
-
The Filter5 parameter filters the data to export. This parameter has the same syntax requirements as the Filter1 parameter, the same OR behavior for multiple values in the same parameter, and the same AND behavior for multiple filter parameters.
Use this parameter only if you're also using the Filter4, Filter3, Filter2, and Filter1 parameters in the same command.
@@ -377,6 +359,7 @@ Use this parameter only if you're also using the Filter4, Filter3, Filter2, and
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -386,15 +369,13 @@ Accept wildcard characters: False
```
### -PageCookie
-
-> Applicable: Security & Compliance
-
The PageCookie parameter specifies whether to get more data when the value of the LastPage property in the command output is False. If you don't use the PageSize parameter, a maximum of 100 records are returned. If you use the PageSize parameter, a maximum of 5000 records can be returned. To get more records than what as returned in the current command, use the value of the Watermark property from the output of the current command as the value for the PageCookie parameter in a new command with the same date range and filters. The PageCookie value is valid for 120 seconds to fetch the next set of records for same query.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -404,15 +385,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 100. Consider using a smaller PageSize value to avoid PageCookie expiry when exporting large datasets.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md b/exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
rename to exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md
index b0ec8af14a..01b6148ebe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
+++ b/exchange/exchange-ps/exchange/Export-AutoDiscoverConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-autodiscoverconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Export-AutoDiscoverConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-autodiscoverconfig
-schema: 2.0.0
-title: Export-AutoDiscoverConfig
+ms.reviewer:
---
# Export-AutoDiscoverConfig
@@ -57,9 +56,6 @@ This example specifies that Exchange is deployed in more than one Active Directo
## PARAMETERS
### -TargetForestDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TargetForestDomainController parameter specifies the forest or domain controller that you want to export the Autodiscover configuration to.
If the target domain controller requires signing, you'll get the error: "A more secure authentication method is required for this server". Domain controllers that require signing aren't supported.
@@ -68,6 +64,7 @@ If the target domain controller requires signing, you'll get the error: "A more
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -77,9 +74,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -89,6 +83,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -DeleteConfig
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DeleteConfig parameter causes the command to delete your configuration settings on the service connection point object.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -116,15 +109,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -134,9 +125,6 @@ Accept wildcard characters: False
```
### -MultipleExchangeDeployments
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MultipleExchangeDeployments parameter specifies whether multiple Exchange deployments exist. Valid values are:
- $true: Exchange is deployed in more than one Active Directory forest, and the forests are connected. The list of authoritative accepted domains for the source forest is written to the Autodiscover service connection point object. Outlook clients use this object to select the most appropriate forest to search for the Autodiscover service.
@@ -146,6 +134,7 @@ The MultipleExchangeDeployments parameter specifies whether multiple Exchange de
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -155,15 +144,13 @@ Accept wildcard characters: False
```
### -PreferredSourceFqdn
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PreferredSourceFqdn parameter specifies the FQDN of the Active Directory domain for the Autodiscover pointer service connection point object.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -173,9 +160,6 @@ Accept wildcard characters: False
```
### -SourceForestCredential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SourceForestCredential parameter specifies the credentials to use when connecting to the source forest.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -184,6 +168,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -193,9 +178,6 @@ Accept wildcard characters: False
```
### -TargetForestCredential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TargetForestCredential parameter specifies the credentials to use to connect to the target forest.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -204,6 +186,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -213,15 +196,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ContentExplorerData.md b/exchange/exchange-ps/exchange/Export-ContentExplorerData.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Export-ContentExplorerData.md
rename to exchange/exchange-ps/exchange/Export-ContentExplorerData.md
index 9f40d2f4b2..547c01be2a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ContentExplorerData.md
+++ b/exchange/exchange-ps/exchange/Export-ContentExplorerData.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-contentexplorerdata
applicable: Security & Compliance
+title: Export-ContentExplorerData
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-contentexplorerdata
-schema: 2.0.0
-title: Export-ContentExplorerData
+ms.reviewer:
---
# Export-ContentExplorerData
@@ -81,9 +80,6 @@ This example exports records for the specified sensitive info type for all workl
## PARAMETERS
### -TagType
-
-> Applicable: Security & Compliance
-
The TagType parameter specifies the type of label to export file details from. Valid values are:
- Retention
@@ -95,6 +91,7 @@ The TagType parameter specifies the type of label to export file details from. V
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 5
@@ -104,9 +101,6 @@ Accept wildcard characters: False
```
### -Aggregate
-
-> Applicable: Security & Compliance
-
**Note:** This parameter is currently in Private Preview, isn't available in all organizations, and is subject to change.
The Aggregate parameter switch returns the folder level aggregated numbers instead of returning details at the item level. You don't need to specify a value with this switch.
@@ -123,6 +117,7 @@ When you use this switch with the TagName, TagType, and Workload parameters, the
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -132,9 +127,6 @@ Accept wildcard characters: False
```
### -ConfidenceLevel
-
-> Applicable: Security & Compliance
-
The ConfidenceLevel parameter specifies the confidence level of the match for the file details to export. Valid values are:
- low
@@ -146,6 +138,7 @@ Type: String
Parameter Sets: (All)
Aliases:
Accepted values: high, medium, low
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -155,15 +148,13 @@ Accept wildcard characters: False
```
### -PageCookie
-
-> Applicable: Security & Compliance
-
The PageCookie parameter specifies whether to get more data when the value of the MorePagesAvailable property in the command output is True. If you don't use the PageSize parameter, a maximum of 100 records are returned. If you use the PageSize parameter, a maximum of 10000 records can be returned.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -173,9 +164,6 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Security & Compliance
-
The PageSize parameter specifies the maximum number of records to return in a single query. Valid input for this parameter is an integer between 1 and 10000. The default value is 100.
**Note**: In empty folders or folders with few files, this parameter can cause the command to run for a long time as it tries to get the PageSize count of the results. To prevent this issue, the command returns data from 5 folders or the number of records specified by the PageSize parameter, whichever completes first. For example, if there are 10 folders with 1 record each, the command returns 5 records of the top 5 folders. In the next execution using page cookie, it returns 5 records from the remaining 5 folders, even if the PageSize value is 10.
@@ -184,6 +172,7 @@ The PageSize parameter specifies the maximum number of records to return in a si
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 2
@@ -193,9 +182,6 @@ Accept wildcard characters: False
```
### -SiteUrl
-
-> Applicable: Security & Compliance
-
The SiteUrl parameter specifies the site URL to export file details from.
You use this parameter for SharePoint and OneDrive workloads.
@@ -204,6 +190,7 @@ You use this parameter for SharePoint and OneDrive workloads.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 3
@@ -213,15 +200,13 @@ Accept wildcard characters: False
```
### -TagName
-
-> Applicable: Security & Compliance
-
The TagName parameter specifies the name of the label to export file details from. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 4
@@ -231,9 +216,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Security & Compliance
-
The UserPrincipalName parameter specifies the user account in UPN format to export message details from. An example UPN value is erika@contoso.onmicrosoft.com.
You use this parameter for Exchange and Microsoft Teams workloads.
@@ -242,6 +224,7 @@ You use this parameter for Exchange and Microsoft Teams workloads.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 6
@@ -251,9 +234,6 @@ Accept wildcard characters: False
```
### -Workload
-
-> Applicable: Security & Compliance
-
The Workload parameter specifies the location to export file details from. Valid values are:
- EXO or Exchange
@@ -265,6 +245,7 @@ The Workload parameter specifies the location to export file details from. Valid
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 7
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md b/exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
rename to exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md
index fd15f00128..0c2de21c86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
+++ b/exchange/exchange-ps/exchange/Export-DlpPolicyCollection.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-dlppolicycollection
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Export-DlpPolicyCollection
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-dlppolicycollection
-schema: 2.0.0
-title: Export-DlpPolicyCollection
+ms.reviewer:
---
# Export-DlpPolicyCollection
@@ -50,15 +49,13 @@ This example exports all the elements of the existing DLP policies to the file C
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the DLP policy you want to export. You can use any value that uniquely identifies the DLP policy. For example, you can specify the name, GUID or distinguished name (DN) of the DLP policy.
```yaml
Type: DlpPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -80,6 +74,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -89,15 +84,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -107,15 +100,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Export-ExchangeCertificate.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
rename to exchange/exchange-ps/exchange/Export-ExchangeCertificate.md
index 0d42ee0899..ec431d5516 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
+++ b/exchange/exchange-ps/exchange/Export-ExchangeCertificate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-exchangecertificate
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Export-ExchangeCertificate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-exchangecertificate
-schema: 2.0.0
-title: Export-ExchangeCertificate
+ms.reviewer:
---
# Export-ExchangeCertificate
@@ -109,9 +108,6 @@ This example exports the same pending certificate request from Example 3. This m
## PARAMETERS
### -Thumbprint
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Thumbprint parameter specifies the certificate or certificate request that you want to export. You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet.
The Thumbprint parameter, not the Identity parameter, is the positional parameter for this cmdlet. Therefore, when you specify a thumbprint value by itself, the command uses that value for the Thumbprint parameter.
@@ -120,6 +116,7 @@ The Thumbprint parameter, not the Identity parameter, is the positional paramete
Type: String
Parameter Sets: Thumbprint
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -129,9 +126,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the certificate or certificate request that you want to export. Valid values are:
- `ServerNameOrFQDN\Thumbprint`
@@ -147,6 +141,7 @@ The Thumbprint parameter, not the Identity parameter, is the positional paramete
Type: ExchangeCertificateIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -156,9 +151,6 @@ Accept wildcard characters: False
```
### -BinaryEncoded
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BinaryEncoded switch encodes the exported certificate or certificate request file by using Distinguished Encoding Rules (DER). You don't need to specify a value with this switch.
Typically, you use this switch when you export a certificate, because you can store the certificate and its private key or chain of trust in a single binary file when you also use the Password parameter. If you don't use this switch, the exported certificate file is Base64 encoded, and you'll need to export any intermediate or root certificates in the chain of trust separately.
@@ -167,6 +159,7 @@ Typically, you use this switch when you export a certificate, because you can st
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -176,9 +169,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -188,6 +178,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -197,9 +188,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -208,6 +196,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -217,9 +206,6 @@ Accept wildcard characters: False
```
### -FileName
-
-> Applicable: Exchange Server 2013
-
**Note**: This parameter was removed from Exchange 2016 and Exchange 2019 by the [2022 H1 Cumulative Updates](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-2022-h1-cumulative-updates-for-exchange-server/ba-p/3285026) because it accepts UNC path values. To export the certificate or certificate request to a file without using the FileName parameter, use the methods described in Example 2 and Example 4.
This parameter is available only in Exchange 2013.
@@ -230,6 +216,7 @@ The FileName parameter specifies the name and path of the exported certificate o
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013
Required: False
Position: Named
@@ -239,9 +226,6 @@ Accept wildcard characters: False
```
### -Password
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Password parameter specifies the password for the private key or chain of trust in the exported certificate file. To import the exported certificate file on another server, you need to know the password.
You can use the following methods as a value for this parameter:
@@ -254,6 +238,7 @@ You can use the following methods as a value for this parameter:
Type: SecureString
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -263,9 +248,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -281,6 +263,7 @@ You can't use this parameter with the Identity parameter, but you can use it wit
Type: ServerIdParameter
Parameter Sets: Thumbprint
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -290,15 +273,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-FilePlanProperty.md b/exchange/exchange-ps/exchange/Export-FilePlanProperty.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Export-FilePlanProperty.md
rename to exchange/exchange-ps/exchange/Export-FilePlanProperty.md
index 597a7de70f..91b4a41f26 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-FilePlanProperty.md
+++ b/exchange/exchange-ps/exchange/Export-FilePlanProperty.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-fileplanproperty
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/export-fileplanproperty
+applicable: Security & Compliance
title: Export-FilePlanProperty
+schema: 2.0.0
---
# Export-FilePlanProperty
@@ -38,9 +36,6 @@ The example exports the file plan properties.
## PARAMETERS
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -50,6 +45,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -59,15 +55,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -77,15 +71,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md b/exchange/exchange-ps/exchange/Export-JournalRuleCollection.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
rename to exchange/exchange-ps/exchange/Export-JournalRuleCollection.md
index 88844ce4ba..0b68ce68f7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
+++ b/exchange/exchange-ps/exchange/Export-JournalRuleCollection.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-journalrulecollection
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Export-JournalRuleCollection
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-journalrulecollection
-schema: 2.0.0
-title: Export-JournalRuleCollection
+ms.reviewer:
---
# Export-JournalRuleCollection
@@ -58,15 +57,13 @@ In Exchange Server 2010, this example exports legacy journal rules that were cre
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of a journal rule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -76,9 +73,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -88,6 +82,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -ExportLegacyRules
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The ExportLegacyRules switch specifies whether to export Exchange 2007 journal rules. You don't need to specify a value with this switch.
@@ -126,6 +116,7 @@ The ExportLegacyRules switch specifies whether to export Exchange 2007 journal r
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -135,15 +126,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md b/exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
rename to exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md
index fac4b1dd30..dada5fa300 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
+++ b/exchange/exchange-ps/exchange/Export-MailboxDiagnosticLogs.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-mailboxdiagnosticlogs
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Export-MailboxDiagnosticLogs
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-mailboxdiagnosticlogs
-schema: 2.0.0
-title: Export-MailboxDiagnosticLogs
+ms.reviewer:
---
# Export-MailboxDiagnosticLogs
@@ -72,9 +71,6 @@ This example retrieves the calendar permissions diagnostic log for the mailbox n
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies that mailbox that contains the diagnostics logs that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -92,6 +88,7 @@ The Identity parameter specifies that mailbox that contains the diagnostics logs
Type: GeneralMailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -101,9 +98,6 @@ Accept wildcard characters: False
```
### -ComponentName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ComponentName parameter specifies the component that you want to retrieve the diagnostic logs for. Valid values depend on the type and location of the mailbox (on-premises Exchange or Exchange Online). Valid values include:
- AcceptCalendarSharingInvite
@@ -133,6 +127,7 @@ The ComponentName parameter specifies the component that you want to retrieve th
Type: String
Parameter Sets: MailboxLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -142,15 +137,13 @@ Accept wildcard characters: False
```
### -ExtendedProperties
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExtendedProperties switch specifies whether to retrieve all of the well-known properties from the mailbox table that are useful for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: ExtendedProperties
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -160,9 +153,6 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Archive switch retrieves the diagnostics logs of the archive mailbox instead of the primary mailbox. You don't need to specify a value with this switch.
@@ -171,6 +161,7 @@ The Archive switch retrieves the diagnostics logs of the archive mailbox instead
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -180,9 +171,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -192,6 +180,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -201,9 +190,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -214,6 +200,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -223,9 +210,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -234,6 +218,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -243,9 +228,6 @@ Accept wildcard characters: False
```
### -IncludeInactiveMailboxes
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeInactiveMailboxes switch specifies whether to include inactive mailboxes in the results. You don't need to specify a value with this switch.
@@ -256,6 +238,7 @@ An inactive mailbox is a mailbox that's placed on Litigation Hold or In-Place Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -265,9 +248,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -280,6 +260,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -289,15 +270,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -307,15 +286,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md b/exchange/exchange-ps/exchange/Export-Message.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Export-Message.md
rename to exchange/exchange-ps/exchange/Export-Message.md
index 4046ba538f..28b6f435c6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
+++ b/exchange/exchange-ps/exchange/Export-Message.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-message
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Export-Message
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-message
-schema: 2.0.0
-title: Export-Message
+ms.reviewer:
---
# Export-Message
@@ -64,15 +63,13 @@ This example retrieves all messages from the specified queue. The query results
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the message. Valid input for this parameter uses the syntax Server\\Queue\\MessageInteger or Queue\\MessageInteger or MessageInteger, for example, Mailbox01\\contoso.com\\5 or 10. For details about message identity, see [Message identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity).
```yaml
Type: MessageIdentity
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -94,6 +88,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -103,15 +98,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md b/exchange/exchange-ps/exchange/Export-MigrationReport.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
rename to exchange/exchange-ps/exchange/Export-MigrationReport.md
index 98abe6ceae..4610a82482 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
+++ b/exchange/exchange-ps/exchange/Export-MigrationReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-migrationreport
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Export-MigrationReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-migrationreport
-schema: 2.0.0
-title: Export-MigrationReport
+ms.reviewer:
---
# Export-MigrationReport
@@ -56,15 +55,13 @@ There are no examples for using this cmdlet because the values used for the requ
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MigrationReportIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -74,15 +71,13 @@ Accept wildcard characters: False
```
### -CsvStream
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Stream
Parameter Sets: StreamBased
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -RowCount
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Int32
Parameter Sets: Paged
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -110,15 +103,13 @@ Accept wildcard characters: False
```
### -StartingRowIndex
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Int32
Parameter Sets: Paged
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -128,9 +119,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -140,6 +128,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -149,9 +138,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -160,6 +146,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -169,9 +156,6 @@ Accept wildcard characters: False
```
### -Partition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -180,6 +164,7 @@ This parameter is reserved for internal Microsoft use.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -189,15 +174,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md b/exchange/exchange-ps/exchange/Export-QuarantineMessage.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md
rename to exchange/exchange-ps/exchange/Export-QuarantineMessage.md
index e18eff76d6..f20bb9e7c2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md
+++ b/exchange/exchange-ps/exchange/Export-QuarantineMessage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-quarantinemessage
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Export-QuarantineMessage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-quarantinemessage
-schema: 2.0.0
-title: Export-QuarantineMessage
+ms.reviewer:
---
# Export-QuarantineMessage
@@ -89,9 +88,6 @@ This example exports the specified message with attachments that was quarantined
## PARAMETERS
### -Identities
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identities parameter identifies quarantined messages for bulk operations. You identify the messages by using the syntax: `value1,value2...valueN`. Each value is a unique quarantined message identifier in the format `GUID1\GUID2` (for example `c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7`).
You can find the Identity value for a quarantined message by using the Get-QuarantineMessage cmdlet.
@@ -102,6 +98,7 @@ When you use this parameter, the Identity parameter is required, but the value i
Type: QuarantineMessageIdentity[]
Parameter Sets: Identities
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -111,17 +108,15 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the quarantined message that you want to export. The value is a unique quarantined message identifier in the format `GUID1\GUID2` (for example `c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7`).
You can find the Identity value for a quarantined message by using the Get-QuarantineMessage cmdlet.
```yaml
Type: QuarantineMessageIdentity
-Parameter Sets: Identities, IdentityOnly
+Parameter Sets: Identities
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -130,10 +125,20 @@ Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```
-### -CompressOutput
+```yaml
+Type: QuarantineMessageIdentity
+Parameter Sets: IdentityOnly
+Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-> Applicable: Security & Compliance, Exchange Online Protection
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: True (ByPropertyName)
+Accept wildcard characters: False
+```
+### -CompressOutput
The CompressOutput switch exports the message as a compressed .zip file. You don't need to specify a value with this switch.
For exported messages, including messages with attachments, the .zip file contains a folder that's named after the first GUID value in the Identity. The folder contains the .eml message that's named after the second GUID value in the Identity.
@@ -142,6 +147,7 @@ For exported messages, including messages with attachments, the .zip file contai
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -151,9 +157,6 @@ Accept wildcard characters: False
```
### -EntityType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EntityType parameter filters the results by EntityType. Valid values are:
- Email
@@ -165,6 +168,7 @@ The EntityType parameter filters the results by EntityType. Valid values are:
Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -174,9 +178,6 @@ Accept wildcard characters: False
```
### -ForceConversionToMime
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The ForceConversionToMime switch converts exported plain text messages to MIME formatting. You don't need to specify a value with this switch.
This switch has no effect if the message is already encoded as Base64.
@@ -185,6 +186,7 @@ This switch has no effect if the message is already encoded as Base64.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -194,9 +196,6 @@ Accept wildcard characters: False
```
### -Password
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Password parameter specifies the password that's required to open the exported message.
You can use the following methods as a value for this parameter:
@@ -211,6 +210,7 @@ To enter the password in plain text, use the PasswordV2 parameter.
Type: SecureString
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -220,15 +220,13 @@ Accept wildcard characters: False
```
### -PasswordV2
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The PasswordV2 parameter specifies the plain text value of the password that's required to open the exported message. Enclose the value in quotation marks (for example, `''`).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -238,15 +236,13 @@ Accept wildcard characters: False
```
### -ReasonForExport
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The ReasonForExport parameter specifies why the message was exported. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -256,15 +252,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md b/exchange/exchange-ps/exchange/Export-RecipientDataProperty.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
rename to exchange/exchange-ps/exchange/Export-RecipientDataProperty.md
index be24b3e0be..79ca27c8bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
+++ b/exchange/exchange-ps/exchange/Export-RecipientDataProperty.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-recipientdataproperty
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Export-RecipientDataProperty
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-recipientdataproperty
-schema: 2.0.0
-title: Export-RecipientDataProperty
+ms.reviewer:
---
# Export-RecipientDataProperty
@@ -67,9 +66,6 @@ This example exports Ayla Kol's picture file to the local computer.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox or mail contact from which you want to export the recipient data. You can use any value that uniquely identifies the user. For example:
- Name
@@ -83,6 +79,7 @@ The Identity parameter specifies the mailbox or mail contact from which you want
Type: MailboxUserContactIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -92,9 +89,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -104,6 +98,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,15 +108,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,9 +124,6 @@ Accept wildcard characters: False
```
### -Picture
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Picture switch specifies that you're exporting the user's picture. You don't need to specify a value with this switch.
The user's picture is exported as a JPEG file.
@@ -144,6 +134,7 @@ You can't use this switch with the SpokenName switch.
Type: SwitchParameter
Parameter Sets: ExportPicture
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -153,9 +144,6 @@ Accept wildcard characters: False
```
### -SpokenName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SpokenName switch specifies that you're exporting the user's spoken name. You don't need to specify a value with this switch.
The user's spoken name is exported as a WMA 9 file.
@@ -166,6 +154,7 @@ You can't use this switch with the Picture switch.
Type: SwitchParameter
Parameter Sets: ExportSpokenName
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -175,15 +164,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md b/exchange/exchange-ps/exchange/Export-TransportRuleCollection.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
rename to exchange/exchange-ps/exchange/Export-TransportRuleCollection.md
index 18d538f220..1996ade66b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
+++ b/exchange/exchange-ps/exchange/Export-TransportRuleCollection.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-transportrulecollection
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Export-TransportRuleCollection
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-transportrulecollection
-schema: 2.0.0
-title: Export-TransportRuleCollection
+ms.reviewer:
---
# Export-TransportRuleCollection
@@ -65,9 +64,6 @@ You need to run these commands in this example on an Exchange 2010 Hub Transport
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is functional only in Exchange Server 2010.
The Identity parameter specifies the transport rule that you want to export. You can use any value that uniquely identifies the rule. For example:
@@ -80,6 +76,7 @@ The Identity parameter specifies the transport rule that you want to export. You
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -89,9 +86,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -101,6 +95,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -123,6 +115,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -132,9 +125,6 @@ Accept wildcard characters: False
```
### -ExportLegacyRules
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The ExportLegacyRules switch is required to export transport rules from Exchange 2007. You don't need to specify a value with this switch.
@@ -143,6 +133,7 @@ The ExportLegacyRules switch is required to export transport rules from Exchange
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -152,9 +143,6 @@ Accept wildcard characters: False
```
### -Format
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The Format parameter specifics the format of the exported transport rule collection. Valid values are:
@@ -167,6 +155,7 @@ The Format parameter specifics the format of the exported transport rule collect
Type: RuleCollectionFormat
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -176,15 +165,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md b/exchange/exchange-ps/exchange/Export-UMCallDataRecord.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md
rename to exchange/exchange-ps/exchange/Export-UMCallDataRecord.md
index 0b1bb2fb95..29e7f3790d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md
+++ b/exchange/exchange-ps/exchange/Export-UMCallDataRecord.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-umcalldatarecord
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Export-UMCallDataRecord
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-umcalldatarecord
-schema: 2.0.0
-title: Export-UMCallDataRecord
+ms.reviewer:
---
# Export-UMCallDataRecord
@@ -57,15 +56,13 @@ This example exports all Unified Messaging call data records for February 1, 201
## PARAMETERS
### -ClientStream
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The ClientStream parameter specifies the .NET stream to use to output for the Unified Messaging call data records.
```yaml
Type: Stream
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -Date
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Date parameter specifies the date of Unified Messaging call data records to retrieve. If there are no call records for the date specified, the report will be empty.
```yaml
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -93,9 +88,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -105,6 +97,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -114,15 +107,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -132,15 +123,13 @@ Accept wildcard characters: False
```
### -UMDialPlan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMDialPlan parameter specifies the UM dial plan to export statistics for. If you don't specify a UM dial plan, statistics include all UM dial plans in the organization.
```yaml
Type: UMDialPlanIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -150,15 +139,13 @@ Accept wildcard characters: False
```
### -UMIPGateway
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMIPGateway parameter specifies the UM IP gateway to export statistics for. If you don't specify a gateway, statistics include all UM IP gateways in the selected UM dial plan, or if a UM dial plan isn't selected, statistics include all UM IP gateways in the organization.
```yaml
Type: UMIPGatewayIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -168,15 +155,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md b/exchange/exchange-ps/exchange/Export-UMPrompt.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md
rename to exchange/exchange-ps/exchange/Export-UMPrompt.md
index 99782c9c33..02e8841d44 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md
+++ b/exchange/exchange-ps/exchange/Export-UMPrompt.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/export-umprompt
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Export-UMPrompt
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/export-umprompt
-schema: 2.0.0
-title: Export-UMPrompt
+ms.reviewer:
---
# Export-UMPrompt
@@ -69,15 +68,13 @@ This example exports a custom greeting for the UM auto attendant MyUMAutoAttenda
## PARAMETERS
### -PromptFileName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The PromptFileName parameter specifies the name of the custom prompt to export.
```yaml
Type: String
Parameter Sets: AACustomGreeting, DPCustomGreeting
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -87,15 +84,13 @@ Accept wildcard characters: False
```
### -UMAutoAttendant
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMAutoAttendant parameter specifies the UM auto attendant ID. This parameter specifies the directory object identifier for the UM auto attendant.
```yaml
Type: UMAutoAttendantIdParameter
Parameter Sets: AACustomGreeting
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -105,15 +100,13 @@ Accept wildcard characters: False
```
### -UMDialPlan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMDialPlan parameter specifies the UM dial plan ID. This parameter specifies the directory object identifier for the UM dial plan.
```yaml
Type: UMDialPlanIdParameter
Parameter Sets: DPCustomGreeting
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -123,9 +116,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -135,6 +125,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -144,15 +135,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -162,15 +151,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md b/exchange/exchange-ps/exchange/Get-ADPermission.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
rename to exchange/exchange-ps/exchange/Get-ADPermission.md
index d946553a7a..773f0467b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
+++ b/exchange/exchange-ps/exchange/Get-ADPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-adpermission
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ADPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-adpermission
-schema: 2.0.0
-title: Get-ADPermission
+ms.reviewer:
---
# Get-ADPermission
@@ -61,15 +60,13 @@ This example returns the permissions that have been granted to the user Chris on
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the object for which you're retrieving permissions. You can retrieve the permissions for any Active Directory object using its distinguished name (DN). If the object is an Exchange object, you might be able to use the object's name. If the DN or the object's name contains spaces, enclose the value in quotation marks (").
```yaml
Type: ADRawEntryIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -90,6 +84,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -99,9 +94,6 @@ Accept wildcard characters: False
```
### -Owner
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Owner switch returns the owner of the Active Directory object. You don't need to specify a value with this switch.
You can't use this switch with the User parameter.
@@ -110,6 +102,7 @@ You can't use this switch with the User parameter.
Type: SwitchParameter
Parameter Sets: Owner
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -119,9 +112,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The user parameter filters the results who has permissions on the Active Directory object. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -152,6 +142,7 @@ You can't use this parameter with the Owner parameter.
Type: SecurityPrincipalIdParameter
Parameter Sets: AccessRights
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md b/exchange/exchange-ps/exchange/Get-ADServerSettings.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
rename to exchange/exchange-ps/exchange/Get-ADServerSettings.md
index 60f17efd20..e44f8bd977 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
+++ b/exchange/exchange-ps/exchange/Get-ADServerSettings.md
@@ -1,28 +1,27 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-adserversettings
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ADServerSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-adserversettings
-schema: 2.0.0
-title: Get-ADServerSettings
+ms.reviewer:
---
-# Get-ADServerSettings
+# Get-AdServerSettings
## SYNOPSIS
This cmdlet is available only in on-premises Exchange.
-Use the Get-ADServerSettings cmdlet to view the Active Directory Domain Services (AD DS) environment settings in the current Exchange Management Shell session. The Get-ADServerSettings cmdlet replaces the AdminSessionADSettings session variable that was used in Exchange Server 2007.
+Use the Get-AdServerSettings cmdlet to view the Active Directory Domain Services (AD DS) environment settings in the current Exchange Management Shell session. The Get-AdServerSettings cmdlet replaces the AdminSessionADSettings session variable that was used in Exchange Server 2007.
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
## SYNTAX
```
-Get-ADServerSettings []
+Get-AdServerSettings []
```
## DESCRIPTION
@@ -32,7 +31,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
### Example 1
```powershell
-Get-ADServerSettings | Format-List
+Get-AdServerSettings | Format-List
```
This example displays the session settings for the current session.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md b/exchange/exchange-ps/exchange/Get-ADSite.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
rename to exchange/exchange-ps/exchange/Get-ADSite.md
index fd05d2e031..507afd4a61 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
+++ b/exchange/exchange-ps/exchange/Get-ADSite.md
@@ -1,28 +1,27 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-adsite
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ADSite
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-adsite
-schema: 2.0.0
-title: Get-ADSite
+ms.reviewer:
---
-# Get-ADSite
+# Get-AdSite
## SYNOPSIS
This cmdlet is available only in on-premises Exchange.
-Use the Get-ADSite cmdlet to display configuration information about one or more Active Directory sites.
+Use the Get-AdSite cmdlet to display configuration information about one or more Active Directory sites.
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
## SYNTAX
```
-Get-ADSite [[-Identity] ]
+Get-AdSite [[-Identity] ]
[-DomainController ]
[]
```
@@ -36,7 +35,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
### Example 1
```powershell
-Get-ADSite Default-First-Site-Name
+Get-AdSite Default-First-Site-Name
```
This example displays the configuration details for the Active Directory site named Default-First-Site-Name.
@@ -44,15 +43,13 @@ This example displays the configuration details for the Active Directory site na
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the Active Directory site for which you want to view configuration details. The identity can be expressed as a GUID or the Active Directory site name. If the Active Directory site name includes spaces, enclose the name in quotation marks (").
```yaml
Type: AdSiteIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -62,9 +59,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -73,6 +67,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md
rename to exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md
index 1ff7c3140b..714d4981eb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md
+++ b/exchange/exchange-ps/exchange/Get-ATPBuiltInProtectionRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-atpbuiltinprotectionrule
applicable: Exchange Online
+title: Get-ATPBuiltInProtectionRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-atpbuiltinprotectionrule
-schema: 2.0.0
-title: Get-ATPBuiltInProtectionRule
+ms.reviewer:
---
# Get-ATPBuiltInProtectionRule
@@ -42,9 +41,6 @@ This example shows the rule for the Built-in protection preset security policy.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -57,6 +53,7 @@ The name of the only rule is ATP Built-In Protection Rule.
Type: DehydrateableRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -66,9 +63,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online
-
The State parameter filters the results by the state of the rule. Valid values are:
- Disabled
@@ -81,6 +75,7 @@ Type: RuleState
Parameter Sets: (All)
Aliases:
Accepted values: Enabled, Disabled
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md
index 1463a2e760..f0a24d140f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/Get-ATPProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-atpprotectionpolicyrule
applicable: Exchange Online
+title: Get-ATPProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-atpprotectionpolicyrule
-schema: 2.0.0
-title: Get-ATPProtectionPolicyRule
+ms.reviewer:
---
# Get-ATPProtectionPolicyRule
@@ -51,9 +50,6 @@ This example returns detailed information about the rule named Strict Preset Sec
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -66,6 +62,7 @@ By default, the available rules (if they exist) are named Standard Preset Securi
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online
-
The State parameter filters the results by the state of the rule. Valid values are:
- Enabled
@@ -88,6 +82,7 @@ Type: RuleState
Parameter Sets: (All)
Aliases:
Accepted values: Enabled, Disabled
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md b/exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md
rename to exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md
index 75b267a41d..754759eea3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md
+++ b/exchange/exchange-ps/exchange/Get-ATPTotalTrafficReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-atptotaltrafficreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-ATPTotalTrafficReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-atptotaltrafficreport
-schema: 2.0.0
-title: Get-ATPTotalTrafficReport
+ms.reviewer:
---
# Get-ATPTotalTrafficReport
@@ -70,9 +69,6 @@ This example returns data for the last 5 days.
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -81,6 +77,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -90,15 +87,13 @@ Accept wildcard characters: False
```
### -AggregateBy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AggregateBy parameter specifies the reporting period. Valid values are Hour, Day or Summary. The default value is Day.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -108,9 +103,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -122,6 +114,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -131,15 +124,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -149,9 +140,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -160,6 +148,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -169,15 +158,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -187,15 +174,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -205,15 +190,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -223,9 +206,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -234,6 +214,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -243,9 +224,6 @@ Accept wildcard characters: False
```
### -SummarizeBy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SummarizeBy parameter returns totals based on the values you specify. If your report filters data using any of the values accepted by this parameter, you can use the SummarizeBy parameter to summarize the results based on those values. To decrease the number of rows returned in the report, consider using the SummarizeBy parameter. Summarizing reduces the amount of data that's retrieved for the report, and delivers the report faster. For example, instead of seeing each instance of a specific value of EventType on an individual row in the report, you can use the SummarizeBy parameter to see the total number of instances of that value of EventType on one row in the report.
For this cmdlet, valid values are:
@@ -261,6 +239,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md b/exchange/exchange-ps/exchange/Get-AcceptedDomain.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
rename to exchange/exchange-ps/exchange/Get-AcceptedDomain.md
index 9ba5ea4926..7a46a55884 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
+++ b/exchange/exchange-ps/exchange/Get-AcceptedDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-accepteddomain
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-AcceptedDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-accepteddomain
-schema: 2.0.0
-title: Get-AcceptedDomain
+ms.reviewer:
---
# Get-AcceptedDomain
@@ -50,15 +49,13 @@ This example lists all the authoritative accepted domains in your organization.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies a string value for the accepted domain. Enter either the GUID or the name of the accepted domain.
```yaml
Type: AcceptedDomainIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -81,6 +75,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -90,9 +85,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -101,6 +93,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md b/exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md
rename to exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md
index b2043007fa..c42017f450 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md
+++ b/exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-accesstocustomerdatarequest
applicable: Exchange Online, Exchange Online Protection
+title: Get-AccessToCustomerDataRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-accesstocustomerdatarequest
-schema: 2.0.0
-title: Get-AccessToCustomerDataRequest
+ms.reviewer:
---
# Get-AccessToCustomerDataRequest
@@ -59,9 +58,6 @@ This example returns detailed information the Customer Lockbox request EXSR12345
## PARAMETERS
### -ApprovalStatus
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ApprovalStatus parameter filters the results by approval status. Valid values are:
- Approved
@@ -73,6 +69,7 @@ The ApprovalStatus parameter filters the results by approval status. Valid value
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -CreatedAfter
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The CreatedAfter parameter filters the results by the creation date in Coordinated Universal Time (UTC).
To specify a date/time value for this parameter, use either of the following options:
@@ -96,6 +90,7 @@ To specify a date/time value for this parameter, use either of the following opt
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -105,15 +100,13 @@ Accept wildcard characters: False
```
### -RequestId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RequestId parameter filters the results by reference number (for example, EXSR123456).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
rename to exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md
index ddefef7cd4..76afb95c32 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDevice.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdevice
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-ActiveSyncDevice
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-activesyncdevice
-schema: 2.0.0
-title: Get-ActiveSyncDevice
+ms.reviewer:
---
# Get-ActiveSyncDevice
@@ -78,9 +77,6 @@ This example returns the owner names of all Outlook Mobile apps that synch via H
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the ActiveSync device that you want to view. You can use any value that uniquely identifies the device. For example:
- GUID
@@ -91,6 +87,7 @@ The Identity parameter specifies the ActiveSync device that you want to view. Yo
Type: ActiveSyncDeviceIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -100,9 +97,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that has the associated ActiveSync device that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -120,6 +114,7 @@ The Mailbox parameter specifies the mailbox that has the associated ActiveSync d
Type: MailboxIdParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -129,9 +124,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -140,6 +132,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -149,9 +142,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -188,6 +178,7 @@ You can filter by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -197,9 +188,6 @@ Accept wildcard characters: False
```
### -Monitoring
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Monitoring switch is required to return monitoring mailboxes in the results. You don't need to specify a value with this switch.
@@ -210,6 +198,7 @@ Monitoring mailboxes are associated with managed availability and the Exchange H
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -219,9 +208,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -233,6 +219,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -242,15 +229,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -260,9 +245,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -289,6 +271,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
rename to exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md
index d5102b012a..d3a5a05c35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAccessRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdeviceaccessrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-ActiveSyncDeviceAccessRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-activesyncdeviceaccessrule
-schema: 2.0.0
-title: Get-ActiveSyncDeviceAccessRule
+ms.reviewer:
---
# Get-ActiveSyncDeviceAccessRule
@@ -51,15 +50,13 @@ This example lists all device access rules set up on the server.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the unique identifier for the device access rule.
```yaml
Type: ActiveSyncDeviceAccessRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -80,6 +74,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
rename to exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md
index bee07e3451..0bb8724eba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
+++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceAutoblockThreshold.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdeviceautoblockthreshold
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ActiveSyncDeviceAutoblockThreshold
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-activesyncdeviceautoblockthreshold
-schema: 2.0.0
-title: Get-ActiveSyncDeviceAutoblockThreshold
+ms.reviewer:
---
# Get-ActiveSyncDeviceAutoblockThreshold
@@ -44,15 +43,13 @@ This example retrieves the threshold settings for the Autoblock threshold rule f
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of the Autoblock threshold rule.
```yaml
Type: ActiveSyncDeviceAutoblockThresholdIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -62,15 +59,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
rename to exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md
index 6a373b8d58..56664b5b8c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
+++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceClass.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdeviceclass
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-ActiveSyncDeviceClass
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-activesyncdeviceclass
-schema: 2.0.0
-title: Get-ActiveSyncDeviceClass
+ms.reviewer:
---
# Get-ActiveSyncDeviceClass
@@ -53,9 +52,6 @@ This example lists all device types within the organization along with a count o
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the ActiveSync device class that you want to view. You can use any value that uniquely identifies the ActiveSync device class. For example:
- Name
@@ -66,6 +62,7 @@ The Identity parameter specifies the ActiveSync device class that you want to vi
Type: ActiveSyncDeviceClassIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -86,6 +80,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -119,6 +111,7 @@ You can filter by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -128,9 +121,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -145,6 +135,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
rename to exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md
index c79c8576e2..df60827dd4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-ActiveSyncDeviceStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncdevicestatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-ActiveSyncDeviceStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-activesyncdevicestatistics
-schema: 2.0.0
-title: Get-ActiveSyncDeviceStatistics
+ms.reviewer:
---
# Get-ActiveSyncDeviceStatistics
@@ -78,15 +77,13 @@ This example retrieves the statistics for the mobile phone configured to synchro
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the user's device ID. If the Mailbox parameter is specified, the Identity parameter is disabled.
```yaml
Type: ActiveSyncDeviceIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -96,9 +93,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the user mailbox for which you want to retrieve the mobile phone statistics. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -116,6 +110,7 @@ The Mailbox parameter specifies the user mailbox for which you want to retrieve
Type: MailboxIdParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -125,9 +120,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -136,6 +128,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -145,15 +138,13 @@ Accept wildcard characters: False
```
### -GetMailboxLog
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The GetMailboxLog switch specifies whether to send the mobile device statistics to the email addresses that are specified by the NotificationEmailAddresses parameter. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -163,9 +154,6 @@ Accept wildcard characters: False
```
### -NotificationEmailAddresses
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The NotificationEmailAddresses parameter specifies a comma-separated list of email addresses to receive the mobile device statistics when you use the GetMailboxLog switch.
This parameter is meaningful only if you also use the GetMailboxLog switch in the same command.
@@ -174,6 +162,7 @@ This parameter is meaningful only if you also use the GetMailboxLog switch in th
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -183,15 +172,13 @@ Accept wildcard characters: False
```
### -ShowRecoveryPassword
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ShowRecoveryPassword parameter specifies whether to return the recovery password for the mobile phone as one of the displayed statistics. If this parameter is set to $true, the command returns the recovery password for the mobile phone as one of the displayed statistics.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
rename to exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md
index 13cdaabfc9..c43f7a04a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-ActiveSyncMailboxPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncmailboxpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-ActiveSyncMailboxPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-activesyncmailboxpolicy
-schema: 2.0.0
-title: Get-ActiveSyncMailboxPolicy
+ms.reviewer:
---
# Get-ActiveSyncMailboxPolicy
@@ -60,15 +59,13 @@ This example returns the policy settings for the Mobile Device mailbox policy na
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the policy name.
```yaml
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -89,6 +83,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
rename to exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md
index c6cd6f96fa..554ac124b7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
+++ b/exchange/exchange-ps/exchange/Get-ActiveSyncOrganizationSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncorganizationsettings
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-ActiveSyncOrganizationSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-activesyncorganizationsettings
-schema: 2.0.0
-title: Get-ActiveSyncOrganizationSettings
+ms.reviewer:
---
# Get-ActiveSyncOrganizationSettings
@@ -42,15 +41,13 @@ This example retrieves the ActiveSync organization settings.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the ActiveSync organization settings object that you want to view. The default name of this object is Mobile Mailbox Settings.
```yaml
Type: ActiveSyncOrganizationSettingsIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -60,9 +57,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -71,6 +65,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
rename to exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md
index e86d0275ad..84a7bede86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/Get-ActiveSyncVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-activesyncvirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ActiveSyncVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-activesyncvirtualdirectory
-schema: 2.0.0
-title: Get-ActiveSyncVirtualDirectory
+ms.reviewer:
---
# Get-ActiveSyncVirtualDirectory
@@ -70,9 +69,6 @@ This example returns a summary list of all Exchange ActiveSync virtual directori
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the ActiveSync virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -87,6 +83,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -96,9 +93,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -112,6 +106,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -121,9 +116,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -132,6 +124,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,15 +134,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -159,9 +150,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
By default, this cmdlet shows information about virtual directories in the Client Access services on Mailbox servers. Client connections are proxied from the Client Access services on Mailbox servers to the backend services on Mailbox servers. Clients don't connect directly to the backend services.
@@ -172,6 +160,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdSiteLink.md b/exchange/exchange-ps/exchange/Get-AdSiteLink.md
similarity index 86%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AdSiteLink.md
rename to exchange/exchange-ps/exchange/Get-AdSiteLink.md
index ed22b0467f..11565da45f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdSiteLink.md
+++ b/exchange/exchange-ps/exchange/Get-AdSiteLink.md
@@ -1,28 +1,27 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-adsitelink
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-AdSiteLink
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-adsitelink
-schema: 2.0.0
-title: Get-ADSiteLink
+ms.reviewer:
---
-# Get-ADSiteLink
+# Get-AdSiteLink
## SYNOPSIS
This cmdlet is available only in on-premises Exchange.
-Use the Get-ADSiteLink cmdlet to view configuration information about an Active Directory IP site link.
+Use the Get-AdSiteLink cmdlet to view configuration information about an Active Directory IP site link.
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
## SYNTAX
```
-Get-ADSiteLink [[-Identity] ]
+Get-AdSiteLink [[-Identity] ]
[-DomainController ]
[]
```
@@ -41,7 +40,7 @@ This example returns a list of all IP site links in your organization.
### Example 2
```powershell
-Get-ADSiteLink | Where {$_.ExchangeCost -ne $null}
+Get-AdSiteLink | Where {$_.ExchangeCost -ne $null}
```
This example returns a list of all IP site links in your organization that have a specific Exchange cost assigned.
@@ -49,15 +48,13 @@ This example returns a list of all IP site links in your organization that have
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name or GUID of the IP site link for which you want to view configuration information.
```yaml
Type: AdSiteLinkIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -78,6 +72,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdaptiveScope.md b/exchange/exchange-ps/exchange/Get-AdaptiveScope.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AdaptiveScope.md
rename to exchange/exchange-ps/exchange/Get-AdaptiveScope.md
index 1be2c8f35f..1444986464 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdaptiveScope.md
+++ b/exchange/exchange-ps/exchange/Get-AdaptiveScope.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-adaptivescope
applicable: Exchange Online, Security & Compliance
+title: Get-AdaptiveScope
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-adaptivescope
-schema: 2.0.0
-title: Get-AdaptiveScope
+ms.reviewer:
---
# Get-AdaptiveScope
@@ -49,9 +48,6 @@ This example returns detailed information about the adaptive scope named Project
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the adaptive scope that you want to view. You can use any value that uniquely identifies the adaptive scope. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the adaptive scope that you want to view. You c
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 0
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -AdministrativeUnits
-
-> Applicable: Exchange Online, Security & Compliance
-
{{ Fill AdministrativeUnits Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -89,15 +84,13 @@ Accept wildcard characters: False
```
### -LocationTypes
-
-> Applicable: Exchange Online, Security & Compliance
-
{{ Fill LocationTypes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md b/exchange/exchange-ps/exchange/Get-AddressBookPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
rename to exchange/exchange-ps/exchange/Get-AddressBookPolicy.md
index 48627a19bd..83e1de7f90 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-AddressBookPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-addressbookpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-AddressBookPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-addressbookpolicy
-schema: 2.0.0
-title: Get-AddressBookPolicy
+ms.reviewer:
---
# Get-AddressBookPolicy
@@ -58,15 +57,13 @@ This example returns information about all address book policies for which the o
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the address book policy.
```yaml
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -76,9 +73,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -87,6 +81,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md b/exchange/exchange-ps/exchange/Get-AddressList.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
rename to exchange/exchange-ps/exchange/Get-AddressList.md
index 7eacd33705..cf62cd285e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
+++ b/exchange/exchange-ps/exchange/Get-AddressList.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-addresslist
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-AddressList
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-addresslist
-schema: 2.0.0
-title: Get-AddressList
+ms.reviewer:
---
# Get-AddressList
@@ -68,9 +67,6 @@ This example returns detailed information for the address list named building4th
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the address list that you want to view. You can use any value that uniquely identifies the address list. For example:
- Name
@@ -84,6 +80,7 @@ You can't use this parameter with the Container or SearchText parameters.
Type: AddressListIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -93,9 +90,6 @@ Accept wildcard characters: False
```
### -Container
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Container parameter filters the results based on the location of the address list. Only address lists under the specified path are returned. Valid input for this parameter is the root "\\" (also known as All Address Lists) or an existing address list. You can use any value that uniquely identifies the address list. For example:
- Name
@@ -109,6 +103,7 @@ You can't use this parameter with the Identity or SearchText parameters.
Type: AddressListIdParameter
Parameter Sets: Container
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -118,9 +113,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -129,6 +121,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -138,9 +131,6 @@ Accept wildcard characters: False
```
### -SearchText
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SearchText parameter filters the results based on the name and display name of the address list. Only address lists whose names or display names that contain the specified text string are returned. If the value contains spaces, enclose the value in quotation marks (").
You can't use this parameter with the Container or Identity parameters.
@@ -149,6 +139,7 @@ You can't use this parameter with the Container or Identity parameters.
Type: String
Parameter Sets: SearchSet
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md b/exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md
rename to exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md
index c4273ec8f9..7faa2b133d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md
+++ b/exchange/exchange-ps/exchange/Get-AddressRewriteEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-addressrewriteentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-AddressRewriteEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-addressrewriteentry
-schema: 2.0.0
-title: Get-AddressRewriteEntry
+ms.reviewer:
---
# Get-AddressRewriteEntry
@@ -49,15 +48,13 @@ This example returns the detailed configuration of a single address rewrite entr
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the address rewrite entry to be retrieved. The Identity parameter accepts a GUID or the unique address rewrite name. You can omit the Identity parameter label.
```yaml
Type: AddressRewriteEntryIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -78,6 +72,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md b/exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
rename to exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md
index 98e1a44545..e9159a5432 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
+++ b/exchange/exchange-ps/exchange/Get-AdminAuditLogConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-adminauditlogconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-AdminAuditLogConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-adminauditlogconfig
-schema: 2.0.0
-title: Get-AdminAuditLogConfig
+ms.reviewer:
---
# Get-AdminAuditLogConfig
@@ -46,9 +45,6 @@ This example displays the administrator audit logging settings. The output of th
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -57,6 +53,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md b/exchange/exchange-ps/exchange/Get-AdministrativeUnit.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
rename to exchange/exchange-ps/exchange/Get-AdministrativeUnit.md
index d1db51fb3f..6a2753ab2d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
+++ b/exchange/exchange-ps/exchange/Get-AdministrativeUnit.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-administrativeunit
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-AdministrativeUnit
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-administrativeunit
-schema: 2.0.0
-title: Get-AdministrativeUnit
+ms.reviewer:
---
# Get-AdministrativeUnit
@@ -53,9 +52,6 @@ This example returns detailed information about the administrative unit with the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the administrative unit that you want to view. You can use any value that uniquely identifies the administrative unit. For example:
- Display name (this value is the same in Microsoft Graph PowerShell)
@@ -68,6 +64,7 @@ The Identity parameter specifies the administrative unit that you want to view.
Type: AdministrativeUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -77,9 +74,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -89,6 +83,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -98,9 +93,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -109,6 +101,7 @@ This parameter is reserved for internal Microsoft use.
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -118,15 +111,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md b/exchange/exchange-ps/exchange/Get-AgentLog.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
rename to exchange/exchange-ps/exchange/Get-AgentLog.md
index 7cc4bd9fa0..90b89266d4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
+++ b/exchange/exchange-ps/exchange/Get-AgentLog.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-agentlog
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-AgentLog
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-agentlog
-schema: 2.0.0
-title: Get-AgentLog
+ms.reviewer:
---
# Get-AgentLog
@@ -44,9 +43,6 @@ This example returns a report that has statistics collected between 09:00 (9 A.M
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -55,6 +51,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -64,15 +61,13 @@ Accept wildcard characters: False
```
### -Location
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Location parameter specifies the directory that contains the log files that you can use to build usage reports. The default path is %ExchangeInstallPath%TransportRoles\\Logs\\AgentLog. You need to enclose the file path in quotation marks (").
```yaml
Type: LocalLongFullPath
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -82,9 +77,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -93,6 +85,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -102,9 +95,6 @@ Accept wildcard characters: False
```
### -TransportService
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
- Hub for the Transport service on Mailbox servers.
@@ -117,6 +107,7 @@ The TransportService parameter specifies the transport service that you want to
Type: TransportService
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md b/exchange/exchange-ps/exchange/Get-AggregateZapReport.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md
rename to exchange/exchange-ps/exchange/Get-AggregateZapReport.md
index fe08151188..fd62052590 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md
+++ b/exchange/exchange-ps/exchange/Get-AggregateZapReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-aggregatezapreport
applicable: Exchange Online
+title: Get-AggregateZapReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-aggregatezapreport
-schema: 2.0.0
-title: Get-AggregateZapReport
+ms.reviewer:
---
# Get-AggregateZapReport
@@ -58,9 +57,6 @@ This example retrieves information for the specified date range.
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only. If you enter the date, enclose the value in quotation marks ("), for example, "09/01/2018".
@@ -71,6 +67,7 @@ If you use the EndDate parameter, you also need to use the StartDate parameter.
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -80,15 +77,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 2
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 3
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018".
@@ -129,6 +119,7 @@ If you use this parameter, you also need to use the StartDate parameter.
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 4
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md
rename to exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md
index 86ea27c33c..332d193a34 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-AntiPhishPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-antiphishpolicy
applicable: Exchange Online, Exchange Online Protection
+title: Get-AntiPhishPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-antiphishpolicy
-schema: 2.0.0
-title: Get-AntiPhishPolicy
+ms.reviewer:
---
# Get-AntiPhishPolicy
@@ -51,9 +50,6 @@ This example shows detailed information about the antiphish policy named Office
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the antiphish policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the antiphish policy that you want to view. You
Type: AntiPhishPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 0
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -Advanced
-
-> Applicable: Exchange Online
-
The Advanced switch filters the properties that are returned to the advanced settings in the policy. For example:
- PhishThresholdLevel
@@ -89,6 +83,7 @@ Advanced settings are available only in anti-phishing policies in Microsoft Defe
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -98,9 +93,6 @@ Accept wildcard characters: False
```
### -Impersonation
-
-> Applicable: Exchange Online
-
The Impersonation switch filters the properties that are returned to the impersonation settings in the policy. For example:
- EnableMailboxIntelligence
@@ -131,6 +123,7 @@ Impersonation settings are available only in anti-phishing policies in Microsoft
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -140,9 +133,6 @@ Accept wildcard characters: False
```
### -Spoof
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Spoof switch filters the properties that are returned to the spoof settings in the policy. For example:
- EnableAntiSpoofEnforcement
@@ -154,6 +144,7 @@ You don't need to specify a value with this switch.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md b/exchange/exchange-ps/exchange/Get-AntiPhishRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md
rename to exchange/exchange-ps/exchange/Get-AntiPhishRule.md
index d21b4063d9..9593dd004c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md
+++ b/exchange/exchange-ps/exchange/Get-AntiPhishRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-antiphishrule
applicable: Exchange Online, Exchange Online Protection
+title: Get-AntiPhishRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-antiphishrule
-schema: 2.0.0
-title: Get-AntiPhishRule
+ms.reviewer:
---
# Get-AntiPhishRule
@@ -49,9 +48,6 @@ This example returns detailed information about the antiphish rule named Researc
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the antiphish rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the antiphish rule that you want to view. You c
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 0
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The State parameter filters the results by the state of the rule. Valid values are Enabled and Disabled.
```yaml
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-App.md b/exchange/exchange-ps/exchange/Get-App.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-App.md
rename to exchange/exchange-ps/exchange/Get-App.md
index a1ade6001f..4d63102688 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-App.md
+++ b/exchange/exchange-ps/exchange/Get-App.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-app
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-App
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-app
-schema: 2.0.0
-title: Get-App
+ms.reviewer:
---
# Get-App
@@ -61,15 +60,13 @@ This example displays the summary list of apps installed by administrators for t
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID of the app that you want to view. To find the GUID value of an app, run the command Get-App | Format-Table -Auto DisplayName,AppId.
```yaml
Type: AppIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -90,6 +84,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -99,9 +94,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the identity of the mailbox where the apps are installed. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -123,6 +115,7 @@ You can't use this parameter with the Identity parameter.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -132,15 +125,13 @@ Accept wildcard characters: False
```
### -OrganizationApp
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OrganizationApp switch includes apps that are installed for the organization (not bound to a specific user) in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -150,9 +141,6 @@ Accept wildcard characters: False
```
### -PrivateCatalog
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The PrivateCatalog switch includes private catalog add-ins in the results. You don't need to specify a value with this switch.
You need to use this switch with the OrganizationApp switch.
@@ -161,6 +149,7 @@ You need to use this switch with the OrganizationApp switch.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md
rename to exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md
index a945fa35af..1feb6b2100 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-AppRetentionCompliancePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-appretentioncompliancepolicy
applicable: Security & Compliance
+title: Get-AppRetentionCompliancePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-appretentioncompliancepolicy
-schema: 2.0.0
-title: Get-AppRetentionCompliancePolicy
+ms.reviewer:
---
# Get-AppRetentionCompliancePolicy
@@ -53,9 +52,6 @@ This example returns detailed information for the app retention compliance polic
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the app retention compliance policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -66,6 +62,7 @@ The Identity parameter specifies the app retention compliance policy that you wa
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -DistributionDetail
-
-> Applicable: Security & Compliance
-
The DistributionDetail switch returns detailed policy distribution information in the DistributionResults property. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -93,15 +88,13 @@ Accept wildcard characters: False
```
### -ErrorPolicyOnly
-
-> Applicable: Security & Compliance
-
{{ Fill ErrorPolicyOnly Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -111,9 +104,6 @@ Accept wildcard characters: False
```
### -RetentionRuleTypes
-
-> Applicable: Security & Compliance
-
The RetentionRuleTypes switch specifies whether to return the value of the RetentionRuleTypes property in the results. You don't need to specify a value with this switch.
To see the RetentionRuleTypes property, you need to pipe the command to a formatting cmdlet. For example, `Get-AppRetentionCompliancePolicy -RetentionRuleTypes | Format-Table -Auto Name,RetentionRuleTypes`. If you don't use the RetentionRuleTypes switch, the value appears blank.
@@ -122,6 +112,7 @@ To see the RetentionRuleTypes property, you need to pipe the command to a format
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionComplianceRule.md b/exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionComplianceRule.md
rename to exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md
index ceca879adc..b61fb71ac0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionComplianceRule.md
+++ b/exchange/exchange-ps/exchange/Get-AppRetentionComplianceRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-appretentioncompliancerule
applicable: Security & Compliance
+title: Get-AppRetentionComplianceRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-appretentioncompliancerule
-schema: 2.0.0
-title: Get-AppRetentionComplianceRule
+ms.reviewer:
---
# Get-AppRetentionComplianceRule
@@ -47,9 +46,6 @@ This example returns detailed information for the app retention compliance rule
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the app retention compliance rule that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -60,6 +56,7 @@ The Identity parameter specifies the app retention compliance rule that you want
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter filters the app retention compliance rule results by the associated app retention compliance policy. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -82,6 +76,7 @@ The Policy parameter filters the app retention compliance rule results by the as
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md
rename to exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md
index 83a5b541f3..60e3070aa4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-ApplicationAccessPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-applicationaccesspolicy
applicable: Exchange Online, Exchange Online Protection
+title: Get-ApplicationAccessPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-applicationaccesspolicy
-schema: 2.0.0
-title: Get-ApplicationAccessPolicy
+ms.reviewer:
---
# Get-ApplicationAccessPolicy
@@ -50,15 +49,13 @@ This example returns detailed information for the specified application access p
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the application access policy that you want to view. To find the Identity value for the policy, run the command Get-ApplicationAccessPolicy | Format-List Identity,Description,ScopeName,AccessRight,AppID.
```yaml
Type: ApplicationAccessPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md b/exchange/exchange-ps/exchange/Get-ArcConfig.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md
rename to exchange/exchange-ps/exchange/Get-ArcConfig.md
index 49101ba1b4..84df4c911e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md
+++ b/exchange/exchange-ps/exchange/Get-ArcConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-arcconfig
applicable: Exchange Online
+title: Get-ArcConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-arcconfig
-schema: 2.0.0
-title: Get-ArcConfig
+ms.reviewer:
---
# Get-ArcConfig
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md b/exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md
rename to exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md
index 6af619e308..31818f3779 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md
+++ b/exchange/exchange-ps/exchange/Get-AtpPolicyForO365.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-atppolicyforo365
applicable: Exchange Online
+title: Get-AtpPolicyForO365
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-atppolicyforo365
-schema: 2.0.0
-title: Get-AtpPolicyForO365
+ms.reviewer:
---
# Get-AtpPolicyForO365
@@ -51,15 +50,13 @@ This example returns detailed information about the default policy.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the policy that you want to modify. There's only one policy named Default.
```yaml
Type: AtpPolicyForO365IdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md b/exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md
rename to exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md
index eef7c64274..f9144d58cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md
+++ b/exchange/exchange-ps/exchange/Get-AttachmentFilterEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-attachmentfilterentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-AttachmentFilterEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-attachmentfilterentry
-schema: 2.0.0
-title: Get-AttachmentFilterEntry
+ms.reviewer:
---
# Get-AttachmentFilterEntry
@@ -28,7 +27,7 @@ Get-AttachmentFilterEntry [[-Identity] ]
```
## DESCRIPTION
-On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://learn.microsoft.com/powershell/module/exchangepowershell/set-attachmentfilterlistconfig).
+On Edge Transport servers, the Attachment Filtering agent blocks attachments in messages based on the content type and the file name of the attachment. The configuration of the Attachment Filtering agent determines how messages that contain the specified attachments are processed. For more information about how to configure the Attachment Filtering agent, see [Set-AttachmentFilterListConfig](https://learn.microsoft.com/powershell/module/exchange/set-attachmentfilterlistconfig).
On Edge Transport servers, you need to be a member of the local Administrators group to run this cmdlet.
@@ -58,9 +57,6 @@ This example returns only the attachment filter entries that filter attachments
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies which attachment filter entry the command retrieves. The Identity parameter accepts values in the format Type:Name, where Type is one of the following values:
- ContentType: This value matches the attachment filter entry against the MIME content type.
@@ -70,6 +66,7 @@ The Identity parameter specifies which attachment filter entry the command retri
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -90,6 +84,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md b/exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md
rename to exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md
index f58a7b6e34..f05c82c01c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md
+++ b/exchange/exchange-ps/exchange/Get-AttachmentFilterListConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-attachmentfilterlistconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-AttachmentFilterListConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-attachmentfilterlistconfig
-schema: 2.0.0
-title: Get-AttachmentFilterListConfig
+ms.reviewer:
---
# Get-AttachmentFilterListConfig
@@ -43,9 +42,6 @@ This example returns detailed information about the Attachment Filtering agent c
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -54,6 +50,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuditConfig.md b/exchange/exchange-ps/exchange/Get-AuditConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AuditConfig.md
rename to exchange/exchange-ps/exchange/Get-AuditConfig.md
index 764e429abb..65476171dc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuditConfig.md
+++ b/exchange/exchange-ps/exchange/Get-AuditConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-auditconfig
applicable: Security & Compliance
+title: Get-AuditConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-auditconfig
-schema: 2.0.0
-title: Get-AuditConfig
+ms.reviewer:
---
# Get-AuditConfig
@@ -41,15 +40,13 @@ This example shows the auditing configuration in the Microsoft Purview complianc
## PARAMETERS
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md b/exchange/exchange-ps/exchange/Get-AuditLogSearch.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
rename to exchange/exchange-ps/exchange/Get-AuditLogSearch.md
index eb76ab1d68..a77201fca0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
+++ b/exchange/exchange-ps/exchange/Get-AuditLogSearch.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-auditlogsearch
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-AuditLogSearch
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-auditlogsearch
-schema: 2.0.0
-title: Get-AuditLogSearch
+ms.reviewer:
---
# Get-AuditLogSearch
@@ -54,15 +53,13 @@ This example returns a list of current administrator audit log searches.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the GUID for an audit log search. You can run the command Get-AuditLogSearch | Format-List Identity to display the GUIDs for all current audit log searches.
```yaml
Type: AuditLogSearchIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -CreatedAfter
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The CreatedAfter parameter filters the results to audit log searches that were created after the specified date.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -83,6 +77,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -92,9 +87,6 @@ Accept wildcard characters: False
```
### -CreatedBefore
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The CreatedBefore parameter filters the results to audit log searches that were created before the specified date.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -103,6 +95,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -112,15 +105,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -130,15 +121,13 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Type parameter specifies the type of audit log searches to return. Use the value Admin to return administrator audit log searches or use mailbox to return mailbox audit log searches. If the Type parameter isn't used, the cmdlet returns both administrator and mailbox audit log searches.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md b/exchange/exchange-ps/exchange/Get-AuthConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
rename to exchange/exchange-ps/exchange/Get-AuthConfig.md
index 0274db23b5..7acbfbce8c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
+++ b/exchange/exchange-ps/exchange/Get-AuthConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-authconfig
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-AuthConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-authconfig
-schema: 2.0.0
-title: Get-AuthConfig
+ms.reviewer:
---
# Get-AuthConfig
@@ -41,15 +40,13 @@ This example retrieves the authorization configuration for the Exchange organiza
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md b/exchange/exchange-ps/exchange/Get-AuthRedirect.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
rename to exchange/exchange-ps/exchange/Get-AuthRedirect.md
index 51703adc07..a1e538e22c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
+++ b/exchange/exchange-ps/exchange/Get-AuthRedirect.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-authredirect
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-AuthRedirect
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-authredirect
-schema: 2.0.0
-title: Get-AuthRedirect
+ms.reviewer:
---
# Get-AuthRedirect
@@ -51,15 +50,13 @@ This example shows detailed information about the OAuth redirection object named
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the existing OAuth redirection object that you want to view. The object name uses the syntax `AuthRedirect-Bearer-GUID`.
```yaml
Type: AuthRedirectIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md b/exchange/exchange-ps/exchange/Get-AuthServer.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
rename to exchange/exchange-ps/exchange/Get-AuthServer.md
index 169457a4a0..ecf577d5a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
+++ b/exchange/exchange-ps/exchange/Get-AuthServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-authserver
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-AuthServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-authserver
-schema: 2.0.0
-title: Get-AuthServer
+ms.reviewer:
---
# Get-AuthServer
@@ -51,9 +50,6 @@ This example retrieves detailed information for the authorization server named W
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the authorization server object that you want to view. You can use any value that uniquely identifies the authorization server. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the authorization server object that you want t
Type: AuthServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -84,6 +78,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
rename to exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md
index 3de4c64a22..b79c7d9b3c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-authenticationpolicy
applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-AuthenticationPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-authenticationpolicy
-schema: 2.0.0
-title: Get-AuthenticationPolicy
+ms.reviewer:
---
# Get-AuthenticationPolicy
@@ -56,9 +55,6 @@ In Exchange Online, this example specifies whether legacy Exchange tokens for Ou
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the authentication policy you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -69,6 +65,7 @@ The Identity parameter specifies the authentication policy you want to view. You
Type: AuthPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 0
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -AllowLegacyExchangeTokens
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowLegacyExchangeTokens switch specifies whether legacy Exchange tokens are allowed for Outlook add-ins in your organization. You don't need to specify a value with this switch.
@@ -96,6 +90,7 @@ Legacy Exchange tokens include Exchange user identity and callback tokens.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -105,9 +100,6 @@ Accept wildcard characters: False
```
### -TenantId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
{{ Fill TenantId Description }}
@@ -116,6 +108,7 @@ This parameter is available only in the cloud-based service.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md
rename to exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md
index 5f3b883571..b60b6db4da 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-autosensitivitylabelpolicy
applicable: Security & Compliance
+title: Get-AutoSensitivityLabelPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-autosensitivitylabelpolicy
-schema: 2.0.0
-title: Get-AutoSensitivityLabelPolicy
+ms.reviewer:
---
# Get-AutoSensitivityLabelPolicy
@@ -45,9 +44,6 @@ This example returns detailed information about the autosensitivity label policy
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the auto-labeling policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -58,6 +54,7 @@ The Identity parameter specifies the auto-labeling policy that you want to view.
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -67,15 +64,13 @@ Accept wildcard characters: False
```
### -DistributionDetail
-
-> Applicable: Security & Compliance
-
The DistributionDetail switch returns detailed policy distribution information in the DistributionResults property. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -85,9 +80,6 @@ Accept wildcard characters: False
```
### -ForceValidate
-
-> Applicable: Security & Compliance
-
The ForceValidate parameter specifies whether to include details related to the AdminUnits of users, groups, or sites in the policy. Valid values are:
- $true: Various properties in the policy include details of the AdminUnits that are associated with current set of selected users, groups, or sites.
@@ -97,6 +89,7 @@ The ForceValidate parameter specifies whether to include details related to the
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -106,9 +99,6 @@ Accept wildcard characters: False
```
### -IncludeProgressFeedback
-
-> Applicable: Security & Compliance
-
IncludeProgressFeedback specifies whether to include the labeling progress of files in SharePoint or OneDrive. You don't need to specify a value with this switch.
If you use this switch, the command shows the progress of files to be labeled, files labeled in the last 7 days, and total files labeled for enabled auto-labeling policies.
@@ -117,6 +107,7 @@ If you use this switch, the command shows the progress of files to be labeled, f
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -126,9 +117,6 @@ Accept wildcard characters: False
```
### -IncludeTestModeResults
-
-> Applicable: Security & Compliance
-
The IncludeTestModeResults parameter specifies whether to include the status of test mode in the policy details. Valid values are:
- $true: Include the status of test mode in the policy details.
@@ -138,6 +126,7 @@ The IncludeTestModeResults parameter specifies whether to include the status of
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md b/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md
rename to exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md
index 1c816823d5..ebaea6d9d6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md
+++ b/exchange/exchange-ps/exchange/Get-AutoSensitivityLabelRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-autosensitivitylabelrule
applicable: Security & Compliance
+title: Get-AutoSensitivityLabelRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-autosensitivitylabelrule
-schema: 2.0.0
-title: Get-AutoSensitivityLabelRule
+ms.reviewer:
---
# Get-AutoSensitivityLabelRule
@@ -47,9 +46,6 @@ This example displays summary information for all autolabeling rules in the Micr
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the auto-labeling policy rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -60,6 +56,7 @@ The Identity parameter specifies the auto-labeling policy rule that you want to
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -87,15 +82,13 @@ Accept wildcard characters: False
```
### -ForceValidate
-
-> Applicable: Security & Compliance
-
{{ Fill ForceValidate Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -105,9 +98,6 @@ Accept wildcard characters: False
```
### -IncludeExecutionRuleGuids
-
-> Applicable: Security & Compliance
-
The IncludeExecutionRuleGuids parameter specifies whether to include the execution rule GUID in the rule details. Valid values are:
- $true: Include the execution rule GUID in the rule details.
@@ -117,6 +107,7 @@ The IncludeExecutionRuleGuids parameter specifies whether to include the executi
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -126,9 +117,6 @@ Accept wildcard characters: False
```
### -IncludeExecutionRuleInformation
-
-> Applicable: Security & Compliance
-
The IncludeExecutionRuleInformation parameter specifies whether to include the execution rule information in the rule details. Valid values are:
- $true: Include the execution rule information in the rule details.
@@ -138,6 +126,7 @@ The IncludeExecutionRuleInformation parameter specifies whether to include the e
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -147,9 +136,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter filters the auto-labeling policy rule results by the associated auto-labeling policy. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -160,6 +146,7 @@ The Policy parameter filters the auto-labeling policy rule results by the associ
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -169,15 +156,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
rename to exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md
index e37a13db48..e8c693c9bf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/Get-AutodiscoverVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-autodiscovervirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-AutodiscoverVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-autodiscovervirtualdirectory
-schema: 2.0.0
-title: Get-AutodiscoverVirtualDirectory
+ms.reviewer:
---
# Get-AutodiscoverVirtualDirectory
@@ -68,9 +67,6 @@ This example returns a summary list of all Autodiscover virtual directories in t
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Autodiscover virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -85,6 +81,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -94,9 +91,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -110,6 +104,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -119,9 +114,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -130,6 +122,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -139,15 +132,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -157,9 +148,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
By default, this cmdlet shows information about virtual directories in the Client Access services on Mailbox servers. Client connections are proxied from the Client Access services on Mailbox servers to the backend services on Mailbox servers. Clients don't connect directly to the backend services.
@@ -170,6 +158,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md b/exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
rename to exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md
index ee7c097c2e..bfde6fcc4c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/exchange/Get-AvailabilityAddressSpace.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-availabilityaddressspace
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-AvailabilityAddressSpace
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-availabilityaddressspace
-schema: 2.0.0
-title: Get-AvailabilityAddressSpace
+ms.reviewer:
---
# Get-AvailabilityAddressSpace
@@ -51,9 +50,6 @@ This example returns details information for the availability address space obje
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the availability address space that you want to view. You can use any value that uniquely identifies the object. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the availability address space that you want to
Type: AvailabilityAddressSpaceIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -84,6 +78,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md b/exchange/exchange-ps/exchange/Get-AvailabilityConfig.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
rename to exchange/exchange-ps/exchange/Get-AvailabilityConfig.md
index 92f1bd5067..7932aaed30 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
+++ b/exchange/exchange-ps/exchange/Get-AvailabilityConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-availabilityconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-AvailabilityConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-availabilityconfig
-schema: 2.0.0
-title: Get-AvailabilityConfig
+ms.reviewer:
---
# Get-AvailabilityConfig
@@ -47,15 +46,13 @@ In Exchange Online, this examples returns the tenant IDs that free/busy informat
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the availability configuration that you want to view. You don't need to use this parameter, because there's only one availability configuration object named Availability Configuration in any organization.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -76,6 +70,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md b/exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md
rename to exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md
index 3bcdbbc750..b73d3f29f3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md
+++ b/exchange/exchange-ps/exchange/Get-AvailabilityReportOutage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-availabilityreportoutage
applicable: Exchange Server 2010
+title: Get-AvailabilityReportOutage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-availabilityreportoutage
-schema: 2.0.0
-title: Get-AvailabilityReportOutage
+ms.reviewer:
---
# Get-AvailabilityReportOutage
@@ -51,15 +50,13 @@ This example returns all outages reported for Microsoft Outlook services at all
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the outage.
```yaml
Type: AvailabilityReportOutageIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: 1
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -ReportDate
-
-> Applicable: Exchange Server 2010
-
The ReportDate parameter specifies the date to query for the outage report.
```yaml
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -87,15 +82,13 @@ Accept wildcard characters: False
```
### -ReportingDatabase
-
-> Applicable: Exchange Server 2010
-
The ReportingDatabase specifies the name of the database on the reporting server.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -105,15 +98,13 @@ Accept wildcard characters: False
```
### -ReportingServer
-
-> Applicable: Exchange Server 2010
-
The ReportingServer parameter specifies the name of the reporting database server to connect to.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md b/exchange/exchange-ps/exchange/Get-BlockedConnector.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md
rename to exchange/exchange-ps/exchange/Get-BlockedConnector.md
index 9004e6d029..c6701d3230 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md
+++ b/exchange/exchange-ps/exchange/Get-BlockedConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-blockedconnector
applicable: Exchange Online, Exchange Online Protection
+title: Get-BlockedConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-blockedconnector
-schema: 2.0.0
-title: Get-BlockedConnector
+ms.reviewer:
---
# Get-BlockedConnector
@@ -47,15 +46,13 @@ This example returns detailed information for the specified blocked connector.
## PARAMETERS
### -ConnectorId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ConnectorId parameter specifies the blocked connector that you want to view. The value is a GUID (for example, 159eb7c4-75d7-43e2-95fe-ced44b3e0a56).
```yaml
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md b/exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md
rename to exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md
index 92c889fdec..4a14ad443b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md
+++ b/exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-blockedsenderaddress
applicable: Exchange Online, Exchange Online Protection
+title: Get-BlockedSenderAddress
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-blockedsenderaddress
-schema: 2.0.0
-title: Get-BlockedSenderAddress
+ms.reviewer:
---
# Get-BlockedSenderAddress
@@ -48,15 +47,13 @@ This example returns information about the blocked sender laura@contoso.com.
## PARAMETERS
### -SenderAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SenderAddress parameter filters the results by the email address of the blocked user.
```yaml
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md b/exchange/exchange-ps/exchange/Get-CASMailbox.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
rename to exchange/exchange-ps/exchange/Get-CASMailbox.md
index a742383485..00439ed122 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
+++ b/exchange/exchange-ps/exchange/Get-CASMailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-casmailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-CASMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-casmailbox
-schema: 2.0.0
-title: Get-CASMailbox
+ms.reviewer:
---
# Get-CASMailbox
@@ -107,9 +106,6 @@ In Exchange Online, this example filters the cmdlet output to only include share
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -127,6 +123,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -136,9 +133,6 @@ Accept wildcard characters: False
```
### -ActiveSyncDebugLogging
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ActiveSyncDebugLogging switch shows the actual value of the ActiveSyncDebugLogging property for the mailbox. You don't need to specify a value with this switch.
If you don't use this switch, the value always appears as $false.
@@ -149,6 +143,7 @@ To see this value, you need to use a formatting cmdlet. For example, `Get-CasMai
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -158,15 +153,13 @@ Accept wildcard characters: False
```
### -ActiveSyncSuppressReadReceipt
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -176,9 +169,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -191,6 +181,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -200,9 +191,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
This parameter requires the creation and passing of a credential object. This credential object is created by using the Get-Credential cmdlet. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -211,6 +199,7 @@ This parameter requires the creation and passing of a credential object. This cr
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -220,9 +209,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -231,6 +217,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -240,9 +227,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -258,6 +242,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -267,9 +252,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -281,6 +263,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -290,9 +273,6 @@ Accept wildcard characters: False
```
### -Monitoring
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Monitoring switch is required to return monitoring mailboxes in the results. You don't need to specify a value with this switch.
@@ -303,6 +283,7 @@ Monitoring mailboxes are associated with managed availability and the Exchange H
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -312,9 +293,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -326,6 +304,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -335,9 +314,6 @@ Accept wildcard characters: False
```
### -ProtocolSettings
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ProtocolSettings switch returns the server names, TCP ports and encryption methods for the following settings:
- ExternalImapSettings
@@ -355,6 +331,7 @@ To see these values, you need to use a formatting cmdlet. For example, `Get-CasM
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -364,9 +341,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -379,6 +353,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -388,15 +363,13 @@ Accept wildcard characters: False
```
### -ReadIsOptimizedForAccessibility
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReadIsOptimizedForAccessibility switch specifies whether to read the value of the IsOptimizedForAccessibility property on the mailbox (whether the mailbox is configured to use the light version of Outlook on the web). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -406,9 +379,6 @@ Accept wildcard characters: False
```
### -RecalculateHasActiveSyncDevicePartnership
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RecalculateHasActiveSyncDevicePartnership switch recalculates the value of the HasActiveSyncDevicePartnership property on the mailbox. You don't need to specify a value with this switch.
The value is automatically updated if it's found to be incorrect.
@@ -417,6 +387,7 @@ The value is automatically updated if it's found to be incorrect.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -426,9 +397,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are:
@@ -450,6 +418,7 @@ You can specify multiple values separated by commas.
Type: RecipientTypeDetails[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -459,15 +428,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -477,9 +444,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -494,6 +458,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md b/exchange/exchange-ps/exchange/Get-CASMailboxPlan.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
rename to exchange/exchange-ps/exchange/Get-CASMailboxPlan.md
index 6f9a965d48..c825898743 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
+++ b/exchange/exchange-ps/exchange/Get-CASMailboxPlan.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-casmailboxplan
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-CASMailboxPlan
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-casmailboxplan
-schema: 2.0.0
-title: Get-CASMailboxPlan
+ms.reviewer:
---
# Get-CASMailboxPlan
@@ -56,9 +55,6 @@ This example returns detailed information about the specified CAS mailbox plan.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the CAS mailbox plan that you want to view. You can use any value that uniquely identifies the CAS mailbox plan. For example:
- Name
@@ -71,6 +67,7 @@ The display name and name of the CAS mailbox plan is the same as the correspondi
Type: MailboxPlanIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -80,9 +77,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Online
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -91,6 +85,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -100,15 +95,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -118,9 +111,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -136,6 +126,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -145,9 +136,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -156,6 +144,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -165,15 +154,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -183,9 +170,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -201,6 +185,7 @@ The results are sorted in ascending order.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticAnalysis.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
rename to exchange/exchange-ps/exchange/Get-CalendarDiagnosticAnalysis.md
index ed3b0dc62d..497c465e12 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
+++ b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticAnalysis.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-calendardiagnosticanalysis
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-CalendarDiagnosticAnalysis
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendardiagnosticanalysis
-schema: 2.0.0
-title: Get-CalendarDiagnosticAnalysis
+ms.reviewer:
---
# Get-CalendarDiagnosticAnalysis
@@ -100,9 +99,6 @@ For basic analysis of the items, don't include the DetailLevel parameter, or use
## PARAMETERS
### -CalendarLogs
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The CalendarLogs parameter specifies the calendar item that you want to analyze. You identify the calendar item by storing the output of the Get-CalendarDiagnosticLog cmdlet to a variable and using that variable for the value of this parameter.
For example, to analyze the meeting with the subject "November Budget Meeting" in Shannon Steele's mailbox, run the command `$Budget = Get-CalendarDiagnosticLog -Identity "Shannon Steele" -Subject "November Budget Meeting" -ExactMatch` and then use the value `$Budget` for this parameter.
@@ -115,6 +111,7 @@ You can't use this parameter with the LogLocation parameter.
Type: CalendarLog[]
Parameter Sets: DefaultSet
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -124,9 +121,6 @@ Accept wildcard characters: False
```
### -LogLocation
-
-> Applicable: Exchange Server 2013, Exchange Online
-
**Note**: This parameter was removed from Exchange 2016 and Exchange 2019 by the [2022 H1 Cumulative Updates](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-2022-h1-cumulative-updates-for-exchange-server/ba-p/3285026) because it accepts UNC path values. To specify the calendar items to analyze, use the CalendarLogs parameter.
This parameter is functional only in Exchange 2013.
@@ -141,6 +135,7 @@ You can't use this parameter with the CalendarLogs parameter.
Type: String[]
Parameter Sets: LocationSet
Aliases:
+Applicable: Exchange Server 2013, Exchange Online
Required: True
Position: Named
@@ -150,9 +145,6 @@ Accept wildcard characters: False
```
### -DetailLevel
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DetailLevel parameter specifies the level of detail you want to see in the analysis output. Valid values are:
- Basic: This is the default value. The calendar item properties that are returned are listed in the Detailed Description.
@@ -162,6 +154,7 @@ The DetailLevel parameter specifies the level of detail you want to see in the a
Type: AnalysisDetailLevel
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -171,9 +164,6 @@ Accept wildcard characters: False
```
### -GlobalObjectId
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The GlobalObjectId parameter specifies the identity of the calendar item you want to analyze. In Exchange 2013, you can use this parameter with the LogLocation parameter to specify the calendar item if the location contains multiple exported .msg files.
The GlobalObjectId property of the meeting uses the same format as the CleanGlobalObjectId property (for example, 040000008200E00074C5B7101A82E008000000009421DCCD5046CD0100000000000000001000000010B0349F6B17454685E17D9F9512E71F) and the value of the two properties is likely the same. However, the value of GlobalObjectId might not stay the same for all instances of the same meeting in multiple calendars (for example, different attendees invited to different instances of the same recurring meeting).
@@ -182,6 +172,7 @@ The GlobalObjectId property of the meeting uses the same format as the CleanGlob
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -191,9 +182,6 @@ Accept wildcard characters: False
```
### -OutputAs
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OutputAs parameter specifies the output format of the command. Valid values are:
- CSV (This is the default value)
@@ -204,6 +192,7 @@ The OutputAs parameter specifies the output format of the command. Valid values
Type: OutputType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md
similarity index 86%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
rename to exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md
index 5de9699698..38b63df96c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
+++ b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticLog.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-calendardiagnosticlog
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-CalendarDiagnosticLog
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendardiagnosticlog
-schema: 2.0.0
-title: Get-CalendarDiagnosticLog
+ms.reviewer:
---
# Get-CalendarDiagnosticLog
@@ -71,7 +70,7 @@ The output of this cmdlet contains the following information:
- NormalizedSubject: The Subject field of the calendar item.
- CleanGlobalObjectId: The identifier that's constant throughout the lifetime of the calendar item. For example, 040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55.
-After you run the Get-CalendarDiagnosticLog cmdlet, you can analyze the calendar data using the Get-CalendarDiagnosticAnalysis cmdlet. For more information, see [Get-CalendarDiagnosticAnalysis](https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendardiagnosticanalysis).
+After you run the Get-CalendarDiagnosticLog cmdlet, you can analyze the calendar data using the Get-CalendarDiagnosticAnalysis cmdlet. For more information, see [Get-CalendarDiagnosticAnalysis](https://learn.microsoft.com/powershell/module/exchange/get-calendardiagnosticanalysis).
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
@@ -114,9 +113,6 @@ In **Exchange 2013**, this example exports all calendar items in the Calendar Di
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that contains the calendar items. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -134,6 +130,7 @@ The Identity parameter specifies the mailbox that contains the calendar items. Y
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -143,9 +140,6 @@ Accept wildcard characters: False
```
### -LogLocation
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Online
-
**Note**: This parameter was removed from Exchange 2016 and Exchange 2019 by the [2022 H1 Cumulative Updates](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-2022-h1-cumulative-updates-for-exchange-server/ba-p/3285026) because it accepts UNC path values. Usage of this cmdlet is now restricted to the local server.
This parameter is functional only in Exchange 2010 and Exchange 2013.
@@ -160,8 +154,9 @@ In on-premises Exchange organizations, you can use the Get-CalendarDiagnosticAna
```yaml
Type: String
-Parameter Sets: ExportToMsg, MeetingId, MeetingSubject
+Parameter Sets: ExportToMsg
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Online
Required: True
Position: Named
@@ -170,10 +165,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -MeetingID
+```yaml
+Type: String
+Parameter Sets: MeetingId, MeetingSubject
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Online
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -MeetingID
The MeetingID parameter filters the results by the globally unique identifier of the calendar item. The value is the CleanGlobalObjectId property of the calendar item that's available in the output of this cmdlet, or by using other MAPI examination tools. An example value is 040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55. This value is constant throughout the lifetime of the calendar item.
To find this value, it's easiest to first search for the calendar item by using the Subject, StartDate and EndDate parameters. After you find the calendar item that you want, you can use its CleanGlobalObjectId value for the MeetingID parameter in future commands.
@@ -182,8 +187,9 @@ Don't use this parameter with the Subject parameter, because the value of the Me
```yaml
Type: String
-Parameter Sets: MeetingId, ExportToMsg
+Parameter Sets: MeetingId
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -192,18 +198,29 @@ Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```
-### -Subject
+```yaml
+Type: String
+Parameter Sets: ExportToMsg
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: True (ByPropertyName)
+Accept wildcard characters: False
+```
+### -Subject
The Subject parameter identifies the calendar items by the specified text in the Subject field. The text values that you specify aren't case sensitive. If the value contains spaces, enclose the value in quotation marks ("). You can control whether to use exact matching by using the ExactMatch parameter.
Don't use this parameter with the MeetingID parameter, because the value of the MeetingID parameter takes precedence.
```yaml
Type: String
-Parameter Sets: MeetingSubject, ExportToMsg
+Parameter Sets: MeetingSubject
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -212,10 +229,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -Credential
+```yaml
+Type: String
+Parameter Sets: ExportToMsg
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -Credential
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -226,6 +253,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -235,9 +263,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -246,6 +271,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -255,9 +281,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -266,6 +289,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: ExportToMsg
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -275,15 +299,13 @@ Accept wildcard characters: False
```
### -EntryId
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The EntryId parameter filters the results by entry ID. You can specify multiple values separated by commas.
```yaml
Type: String
Parameter Sets: ExportToMsg
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -293,9 +315,6 @@ Accept wildcard characters: False
```
### -ExactMatch
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExactMatch parameter specifies whether to use an exact match or a partial match for text values that you specify for the Subject parameter. Valid values are:
- $true: The subject search uses an exact match and searches all calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" anywhere in the subject, but not "budgeting".
@@ -311,6 +330,7 @@ The value of this parameter is ignored when you use the MeetingId parameter.
Type: Boolean
Parameter Sets: ExportToMsg
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -320,9 +340,6 @@ Accept wildcard characters: False
```
### -ItemClass
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ItemClass parameter filters the results by the specified MessageClass property value of the calendar item (for example, IPM.Appointment). You can specify multiple values separated by commas.
You can only use this parameter with the MeetingID parameter.
@@ -331,6 +348,7 @@ You can only use this parameter with the MeetingID parameter.
Type: String[]
Parameter Sets: ExportToMsg
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -340,15 +358,13 @@ Accept wildcard characters: False
```
### -ItemIds
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ItemIds parameter filters the results by item ID. You can specify multiple values separated by commas.
```yaml
Type: String[]
Parameter Sets: ExportToMsg
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -358,15 +374,13 @@ Accept wildcard characters: False
```
### -Latest
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Latest switch specifies whether to return calendar log data for only the most recent calendar item. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: ExportToMsg
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -376,9 +390,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -391,6 +402,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -400,15 +412,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter determines the number of results returned by the cmdlet. The maximum value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -418,9 +428,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -429,6 +436,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: ExportToMsg
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md
rename to exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md
index 27ba38654a..e01ded63d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md
+++ b/exchange/exchange-ps/exchange/Get-CalendarDiagnosticObjects.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-calendardiagnosticobjects
applicable: Exchange Online
+title: Get-CalendarDiagnosticObjects
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendardiagnosticobjects
-schema: 2.0.0
-title: Get-CalendarDiagnosticObjects
+ms.reviewer:
---
# Get-CalendarDiagnosticObjects
@@ -94,9 +93,6 @@ This example returns diagnostic information for meetings with the subject Team L
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox or Microsoft 365 Group whose calendar you want to view. You can use any value that uniquely identifies the mailbox or Microsoft 365 Group. For example:
- Name
@@ -114,6 +110,7 @@ The Identity parameter specifies the mailbox or Microsoft 365 Group whose calend
Type: UnifiedGroupOrUserMailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -123,15 +120,13 @@ Accept wildcard characters: False
```
### -AnalyzeExceptionWithOriginalStartDate
-
-> Applicable: Exchange Online
-
{{ Fill AnalyzeExceptionWithOriginalStartDate Description }}
```yaml
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -141,15 +136,13 @@ Accept wildcard characters: False
```
### -AutoRequeryOnMeetingId
-
-> Applicable: Exchange Online
-
{{ Fill AutoRequeryOnMeetingId Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -159,15 +152,13 @@ Accept wildcard characters: False
```
### -ConfigurationName
-
-> Applicable: Exchange Online
-
{{ Fill ConfigurationName Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -177,9 +168,6 @@ Accept wildcard characters: False
```
### -CustomPropertyNames
-
-> Applicable: Exchange Online
-
The CustomPropertyNames parameter returns the specified calendar item custom property in the results. For valid values, see [Values for the CustomPropertyNames parameter in Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/values-for-custompropertynames-parameter).
You can specify multiple values separated by commas.
@@ -188,6 +176,7 @@ You can specify multiple values separated by commas.
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -197,9 +186,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range for the OriginalLastModifiedTime property (when the meeting was last modified, not created).
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -208,6 +194,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -217,15 +204,13 @@ Accept wildcard characters: False
```
### -EntryId
-
-> Applicable: Exchange Online
-
The EntryID parameter filters the results by the specified EntryID property value, which corresponds to the MAPI property PR\_ENTRYID.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -235,15 +220,13 @@ Accept wildcard characters: False
```
### -EwsId
-
-> Applicable: Exchange Online
-
{{ Fill EwsId Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -253,9 +236,6 @@ Accept wildcard characters: False
```
### -ExactMatch
-
-> Applicable: Exchange Online
-
The ExactMatch parameter specifies whether to use an exact match or a partial match for text values that you specify for the Subject parameter. Valid values are:
- $true: The subject search uses an exact match and searches all calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" anywhere in the subject, but not "budgeting".
@@ -271,6 +251,7 @@ The value of this parameter is ignored when you use the MeetingId parameter.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -280,15 +261,13 @@ Accept wildcard characters: False
```
### -ItemClass
-
-> Applicable: Exchange Online
-
The ItemClass parameter filters the results by the specified MessageClass property value of the calendar item (for example, IPM.Appointment). You can specify multiple values separated by commas.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -298,15 +277,13 @@ Accept wildcard characters: False
```
### -ItemIds
-
-> Applicable: Exchange Online
-
The ItemIds parameter filters the results by item ID. You can specify multiple values separated by commas.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -316,15 +293,13 @@ Accept wildcard characters: False
```
### -MaxResults
-
-> Applicable: Exchange Online
-
{{ Fill MaxResults Description }}
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -334,15 +309,13 @@ Accept wildcard characters: False
```
### -MeetingId
-
-> Applicable: Exchange Online
-
The MeetingId parameter filters the results by the globally unique identifier of the calendar item. The value is the CleanGlobalObjectId property of the calendar item that's available in the output of this cmdlet, or by using other MAPI examination tools. An example value is 040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55. This value is constant throughout the lifetime of the calendar item.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -352,15 +325,13 @@ Accept wildcard characters: False
```
### -ODataId
-
-> Applicable: Exchange Online
-
{{ Fill ODataId Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -370,15 +341,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter determines the number of results returned by the cmdlet. The maximum value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -388,9 +357,6 @@ Accept wildcard characters: False
```
### -ShouldBindToItem
-
-> Applicable: Exchange Online
-
The ShouldBindToItem parameter specifies whether to truncate large streamable property values (for example, AppointmentRecurrenceBlob). Valid values are:
- $true: The values of large streamable properties aren't truncated, so the full value is returned.
@@ -400,6 +366,7 @@ The ShouldBindToItem parameter specifies whether to truncate large streamable pr
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -409,15 +376,13 @@ Accept wildcard characters: False
```
### -ShouldDecodeEnums
-
-> Applicable: Exchange Online
-
{{ Fill ShouldDecodeEnums Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -427,15 +392,13 @@ Accept wildcard characters: False
```
### -ShouldFetchAttendeeCollection
-
-> Applicable: Exchange Online
-
{{ Fill ShouldFetchAttendeeCollection Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -445,9 +408,6 @@ Accept wildcard characters: False
```
### -ShouldFetchRecurrenceExceptions
-
-> Applicable: Exchange Online
-
The ShouldFetchRecurrenceExceptions parameter specifies whether to include exceptions to recurring meetings. Valid values are:
- $true: Include exceptions to recurring meetings. When you use this value, you also need to use the ItemIds parameter.
@@ -457,6 +417,7 @@ The ShouldFetchRecurrenceExceptions parameter specifies whether to include excep
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -466,9 +427,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The StartDate parameter specifies the start date of the date range for the OriginalLastModifiedTime property (when the meeting was last modified, not created).
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -477,6 +435,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -486,15 +445,13 @@ Accept wildcard characters: False
```
### -Subject
-
-> Applicable: Exchange Online
-
The Subject parameter identifies the calendar items by the specified text in the Subject field. The text values that you specify aren't case sensitive. If the value contains spaces, enclose the value in quotation marks. You can control whether to use exact matching by using the ExactMatch parameter
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md b/exchange/exchange-ps/exchange/Get-CalendarNotification.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
rename to exchange/exchange-ps/exchange/Get-CalendarNotification.md
index 1f56a01412..014d7e719e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
+++ b/exchange/exchange-ps/exchange/Get-CalendarNotification.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-calendarnotification
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-CalendarNotification
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendarnotification
-schema: 2.0.0
-title: Get-CalendarNotification
+ms.reviewer:
---
# Get-CalendarNotification
@@ -49,9 +48,6 @@ This example returns the calendar text message notification settings for Tony's
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -69,6 +65,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -89,6 +83,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -129,6 +119,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -138,15 +129,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md b/exchange/exchange-ps/exchange/Get-CalendarProcessing.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
rename to exchange/exchange-ps/exchange/Get-CalendarProcessing.md
index 87199882e2..a38f7b7958 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
+++ b/exchange/exchange-ps/exchange/Get-CalendarProcessing.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-calendarprocessing
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-CalendarProcessing
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendarprocessing
-schema: 2.0.0
-title: Get-CalendarProcessing
+ms.reviewer:
---
# Get-CalendarProcessing
@@ -30,7 +29,7 @@ Get-CalendarProcessing [-Identity]
```
## DESCRIPTION
-For details about the properties that are returned in the output of this cmdlet, see [Set-CalendarProcessing](https://learn.microsoft.com/powershell/module/exchangepowershell/set-calendarprocessing).
+For details about the properties that are returned in the output of this cmdlet, see [Set-CalendarProcessing](https://learn.microsoft.com/powershell/module/exchange/set-calendarprocessing).
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
@@ -46,9 +45,6 @@ This example shows the calendar processing options for the resource mailbox Room
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the resource mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -66,6 +62,7 @@ The Identity parameter specifies the resource mailbox that you want to view. You
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -86,6 +80,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -110,6 +102,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -119,15 +112,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md
rename to exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md
index 6f2f8b1488..54654c842b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-CaseHoldPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-caseholdpolicy
applicable: Security & Compliance
+title: Get-CaseHoldPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-caseholdpolicy
-schema: 2.0.0
-title: Get-CaseHoldPolicy
+ms.reviewer:
---
# Get-CaseHoldPolicy
@@ -52,9 +51,6 @@ This example displays detailed information for the policy named "Regulation 123
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the case hold policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -65,6 +61,7 @@ The Identity parameter specifies the case hold policy that you want to view. You
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -Case
-
-> Applicable: Security & Compliance
-
The Case parameter specifies the case hold policy that you want to view by using the eDiscovery case that's associated with the policy. You can use the following values to identify the eDiscovery case:
- Name
@@ -88,6 +82,7 @@ You can find these values by running the command: Get-ComplianceCase | Format-Ta
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -97,9 +92,6 @@ Accept wildcard characters: False
```
### -DistributionDetail
-
-> Applicable: Security & Compliance
-
The DistributionDetail switch returns detailed policy distribution information on the case hold policy. You don't need to specify a value with this switch.
If you don't use this switch, the command won't return information about the current deployment status, and the DistributionStatus property will only show as "Pending".
@@ -117,6 +109,7 @@ The following properties are affected by this switch:
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -126,15 +119,13 @@ Accept wildcard characters: False
```
### -IncludeBindings
-
-> Applicable: Security & Compliance
-
PARAMVALUE: SwitchParameter
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -144,15 +135,13 @@ Accept wildcard characters: False
```
### -IncludeBindingsOnly
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeBindingsOnly Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldRule.md b/exchange/exchange-ps/exchange/Get-CaseHoldRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldRule.md
rename to exchange/exchange-ps/exchange/Get-CaseHoldRule.md
index 4a8be64d10..632e20fe65 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldRule.md
+++ b/exchange/exchange-ps/exchange/Get-CaseHoldRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-caseholdrule
applicable: Security & Compliance
+title: Get-CaseHoldRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-caseholdrule
-schema: 2.0.0
-title: Get-CaseHoldRule
+ms.reviewer:
---
# Get-CaseHoldRule
@@ -46,9 +45,6 @@ This example displays detailed information for the case hold rule named "30 Day
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the case hold rule you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -59,6 +55,7 @@ The Identity parameter specifies the case hold rule you want to view. You can us
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter filters the case hold rule results by the associated case hold policy. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -83,6 +77,7 @@ You can use this parameter with the Identity parameter in the same command.
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md b/exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
rename to exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md
index eb41942aba..b246435ac5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/exchange/Get-ClassificationRuleCollection.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-classificationrulecollection
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-ClassificationRuleCollection
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-classificationrulecollection
-schema: 2.0.0
-title: Get-ClassificationRuleCollection
+ms.reviewer:
---
# Get-ClassificationRuleCollection
@@ -51,15 +50,13 @@ This example returns detailed information about the classification rule collecti
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the classification rule collection you want to view. You can use any value that uniquely identifies the classification rule collection. For example, you can specify the name, rule collection name or distinguished name (DN) of the classification rule collection.
```yaml
Type: ClassificationRuleCollectionIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -80,6 +74,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md b/exchange/exchange-ps/exchange/Get-ClientAccessArray.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
rename to exchange/exchange-ps/exchange/Get-ClientAccessArray.md
index 61d0861444..c879bde532 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
+++ b/exchange/exchange-ps/exchange/Get-ClientAccessArray.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-clientaccessarray
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ClientAccessArray
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-clientaccessarray
-schema: 2.0.0
-title: Get-ClientAccessArray
+ms.reviewer:
---
# Get-ClientAccessArray
@@ -57,9 +56,6 @@ This example returns detailed information for the Client Access array named CASA
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Client Access array that you want to view. You can use these values:
- Name (if the value doesn't contain spaces)
@@ -72,6 +68,7 @@ The Identity parameter specifies the Client Access array that you want to view.
Type: ClientAccessArrayIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -81,15 +78,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -99,9 +94,6 @@ Accept wildcard characters: False
```
### -Site
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Site parameter filters the results by Active Directory site. You can use any value that uniquely identifies the site. For example:
- Name
@@ -113,6 +105,7 @@ The Site parameter filters the results by Active Directory site. You can use any
Type: AdSiteIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md b/exchange/exchange-ps/exchange/Get-ClientAccessRule.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
rename to exchange/exchange-ps/exchange/Get-ClientAccessRule.md
index ce2deaa5e2..0e40aa0d98 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
+++ b/exchange/exchange-ps/exchange/Get-ClientAccessRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-clientaccessrule
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-ClientAccessRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-clientaccessrule
-schema: 2.0.0
-title: Get-ClientAccessRule
+ms.reviewer:
---
# Get-ClientAccessRule
@@ -56,9 +55,6 @@ This example retrieves details about the client access rule named "Block Client
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the client access rule that you want to view. You can use any value that uniquely identifies the client access rule. For example:
- Name
@@ -69,6 +65,7 @@ The Identity parameter specifies the client access rule that you want to view. Y
Type: ClientAccessRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -90,6 +84,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -99,9 +94,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is functional only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -110,6 +102,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -119,15 +112,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md b/exchange/exchange-ps/exchange/Get-ClientAccessServer.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
rename to exchange/exchange-ps/exchange/Get-ClientAccessServer.md
index ae619fa9f7..c3cb98eccc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
+++ b/exchange/exchange-ps/exchange/Get-ClientAccessServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-clientaccessserver
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ClientAccessServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-clientaccessserver
-schema: 2.0.0
-title: Get-ClientAccessServer
+ms.reviewer:
---
# Get-ClientAccessServer
@@ -53,9 +52,6 @@ This example returns detailed information for the server mail.contoso.com.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the server with the Client Access server role installed that you want to view.
You can use any value that uniquely identifies the server. For example:
@@ -69,6 +65,7 @@ You can use any value that uniquely identifies the server. For example:
Type: ClientAccessServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -78,15 +75,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -96,9 +91,6 @@ Accept wildcard characters: False
```
### -IncludeAlternateServiceAccountCredentialPassword
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeAlternateServiceAccountCredentialPassword switch specifies whether to include the password of the alternate service account in the results. You don't need to specify a value with this switch.
The password is visible in the AlternateServiceAccountConfiguration property. To see this property, use the Format-List cmdlet. For example, `Get-ClientAccessServer | Format-List AlternateServiceAccountConfiguration`.
@@ -107,6 +99,7 @@ The password is visible in the AlternateServiceAccountConfiguration property. To
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -IncludeAlternateServiceAccountCredentialStatus
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeAlternateServiceAccountCredentialStatus parameter specifies whether to include the status of the alternate service account in the results. You don't need to specify a value with this switch.
The status is visible in the AlternateServiceAccountConfiguration property. To see this property, use the Format-List cmdlet. For example, `Get-ClientAccessServer | Format-List AlternateServiceAccountConfiguration`.
@@ -127,6 +117,7 @@ The status is visible in the AlternateServiceAccountConfiguration property. To s
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md b/exchange/exchange-ps/exchange/Get-ClientAccessService.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
rename to exchange/exchange-ps/exchange/Get-ClientAccessService.md
index 75380355de..1f3d8c72e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
+++ b/exchange/exchange-ps/exchange/Get-ClientAccessService.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-clientaccessservice
applicable: Exchange Server 2016, Exchange Server 2019
+title: Get-ClientAccessService
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-clientaccessservice
-schema: 2.0.0
-title: Get-ClientAccessService
+ms.reviewer:
---
# Get-ClientAccessService
@@ -51,9 +50,6 @@ This example returns detailed information for the server mail.contoso.com.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the server with the Client Access server role installed that you want to view.
You can use any value that uniquely identifies the server. For example:
@@ -67,6 +63,7 @@ You can use any value that uniquely identifies the server. For example:
Type: ClientAccessServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -76,15 +73,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -94,9 +89,6 @@ Accept wildcard characters: False
```
### -IncludeAlternateServiceAccountCredentialPassword
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The IncludeAlternateServiceAccountCredentialPassword switch specifies whether to include the password of the alternate service account in the results. You don't need to specify a value with this switch.
The password is visible in the AlternateServiceAccountConfiguration property. To see this property, use the Format-List cmdlet. For example, `Get-ClientAccessService | Format-List AlternateServiceAccountConfiguration`.
@@ -105,6 +97,7 @@ The password is visible in the AlternateServiceAccountConfiguration property. To
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -114,9 +107,6 @@ Accept wildcard characters: False
```
### -IncludeAlternateServiceAccountCredentialStatus
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The IncludeAlternateServiceAccountCredentialStatus parameter specifies whether to include the status of the alternate service account in the results. You don't need to specify a value with this switch.
The status is visible in the AlternateServiceAccountConfiguration property. To see this property, use the Format-List cmdlet. For example, `Get-ClientAccessService | Format-List AlternateServiceAccountConfiguration`.
@@ -125,6 +115,7 @@ The status is visible in the AlternateServiceAccountConfiguration property. To s
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md b/exchange/exchange-ps/exchange/Get-Clutter.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md
rename to exchange/exchange-ps/exchange/Get-Clutter.md
index 7ecfb68037..abd9f70458 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md
+++ b/exchange/exchange-ps/exchange/Get-Clutter.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.Management-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-clutter
applicable: Exchange Online, Exchange Online Protection
+title: Get-Clutter
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-clutter
-schema: 2.0.0
-title: Get-Clutter
+ms.reviewer:
---
# Get-Clutter
@@ -42,9 +41,6 @@ This example returns the Clutter settings for the user Constancia Pena.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the mailbox that you want to modify. You can us
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online, Exchange Online Protection
-
{{ Fill UseCustomRouting Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md b/exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
rename to exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md
index bf76f861a0..b863d66f12 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/exchange/Get-CmdletExtensionAgent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-cmdletextensionagent
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-CmdletExtensionAgent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-cmdletextensionagent
-schema: 2.0.0
-title: Get-CmdletExtensionAgent
+ms.reviewer:
---
# Get-CmdletExtensionAgent
@@ -60,9 +59,6 @@ This example displays detailed information for the Exchange cmdlet extension age
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of the cmdlet extension agent that you want to view. You can use any value that uniquely identifies the agent. For example:
- Name
@@ -73,6 +69,7 @@ The Identity parameter specifies the name of the cmdlet extension agent that you
Type: CmdletExtensionAgentIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -82,15 +79,13 @@ Accept wildcard characters: False
```
### -Assembly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Assembly parameter filters the results by the specified Assembly property value. The value for the built-in Exchange cmdlet extension agents is Microsoft.Exchange.ProvisioningAgent.dll.
```yaml
Type: String
Parameter Sets: Filters
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -100,15 +95,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -118,9 +111,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Enabled parameter filters the results by enabled or disabled cmdlet extension agents. Valid values are:
- $true: Only enabled agents are included in the results.
@@ -132,6 +122,7 @@ If you don't use this parameter, enabled and disabled agents are included in the
Type: Boolean
Parameter Sets: Filters
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md b/exchange/exchange-ps/exchange/Get-ComplianceCase.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md
rename to exchange/exchange-ps/exchange/Get-ComplianceCase.md
index d0e22b0d1d..74d35075bf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceCase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancecase
applicable: Security & Compliance
+title: Get-ComplianceCase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compliancecase
-schema: 2.0.0
-title: Get-ComplianceCase
+ms.reviewer:
---
# Get-ComplianceCase
@@ -66,9 +65,6 @@ This example returns a summary list of all DSR cases that the custom role group
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the compliance case that you want to view. You can use any value that uniquely identifies the case. For example:
- Name
@@ -78,6 +74,7 @@ The Identity parameter specifies the compliance case that you want to view. You
Type: ComplianceCaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -87,9 +84,6 @@ Accept wildcard characters: False
```
### -CaseType
-
-> Applicable: Security & Compliance
-
The CaseType parameter specifies the type of compliance case that you want to view. Valid values are:
- AdvancedEdiscovery: eDiscovery Premium cases are used to manage legal or other types of investigations. In the Microsoft Purview compliance portal, eDiscovery Premium cases are displayed under **eDiscovery** \> **Premium**.
@@ -106,6 +100,7 @@ The CaseType parameter specifies the type of compliance case that you want to vi
Type: ComplianceCaseType
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -115,15 +110,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -133,9 +126,6 @@ Accept wildcard characters: False
```
### -RecentOnly
-
-> Applicable: Security & Compliance
-
The RecentOnly switch returns a list of the most recently modified cases of the specified case type. You don't need to specify a value with this switch.
This switch is used to display data in the "Recent cases" widget in the Microsoft Purview compliance portal for some features that use compliance case objects.
@@ -144,6 +134,7 @@ This switch is used to display data in the "Recent cases" widget in the Microsof
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -153,15 +144,13 @@ Accept wildcard characters: False
```
### -RoleGroup
-
-> Applicable: Security & Compliance
-
The RoleGroup parameter returns a list of compliance cases that the specified role group is a member of. If you don't include the CaseType parameter, the cmdlet returns a list of eDiscovery Standard cases that the role group is a member of.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCaseMember.md b/exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCaseMember.md
rename to exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md
index b99c26448e..5588971c20 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCaseMember.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceCaseMember.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancecasemember
applicable: Security & Compliance
+title: Get-ComplianceCaseMember
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compliancecasemember
-schema: 2.0.0
-title: Get-ComplianceCaseMember
+ms.reviewer:
---
# Get-ComplianceCaseMember
@@ -53,15 +52,13 @@ This examples shows the members of the eDiscovery case named Fabrikam Litigation
## PARAMETERS
### -Case
-
-> Applicable: Security & Compliance
-
The Case parameter specifies the name of the eDiscovery case that you want to view. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -89,15 +84,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Security & Compliance
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -107,15 +100,13 @@ Accept wildcard characters: False
```
### -ShowCaseAdmin
-
-> Applicable: Security & Compliance
-
The ShowCaseAdmin switch specifies whether to return the eDiscovery case admin in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEvent.md b/exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEvent.md
rename to exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md
index 06939dc393..4688db4274 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEvent.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceRetentionEvent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-complianceretentionevent
applicable: Security & Compliance
+title: Get-ComplianceRetentionEvent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-complianceretentionevent
-schema: 2.0.0
-title: Get-ComplianceRetentionEvent
+ms.reviewer:
---
# Get-ComplianceRetentionEvent
@@ -52,9 +51,6 @@ This example returns detailed information about the compliance retention event n
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the compliance retention event that you want to view. You can use any value that uniquely identifies the event. For example:
- Name
@@ -65,6 +61,7 @@ The Identity parameter specifies the compliance retention event that you want to
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -74,15 +71,13 @@ Accept wildcard characters: False
```
### -BeginDateTime
-
-> Applicable: Security & Compliance
-
{{ Fill BeginDateTime Description }}
```yaml
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -110,15 +103,13 @@ Accept wildcard characters: False
```
### -EndDateTime
-
-> Applicable: Security & Compliance
-
{{ Fill EndDateTime Description }}
```yaml
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -128,15 +119,13 @@ Accept wildcard characters: False
```
### -PreviewOnly
-
-> Applicable: Security & Compliance
-
{{ Fill PreviewOnly Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md
rename to exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md
index eaa1c7f19c..413b3c7aa3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceRetentionEventType.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-complianceretentioneventtype
applicable: Security & Compliance
+title: Get-ComplianceRetentionEventType
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-complianceretentioneventtype
-schema: 2.0.0
-title: Get-ComplianceRetentionEventType
+ms.reviewer:
---
# Get-ComplianceRetentionEventType
@@ -49,9 +48,6 @@ This example returns detailed information for the retention event type named Fab
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the retention event type that you want to view. You can use any value that uniquely identifies the retention event type. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the retention event type that you want to view.
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -LoadTag
-
-> Applicable: Security & Compliance
-
The LoadTag switch specifies whether to show the compliance tags that are associated with the retention event types. You don't need to specify a value with this switch.
If you don't use this switch, the ComplianceTag property will always appear empty in the results.
@@ -82,6 +76,7 @@ If you don't use this switch, the ComplianceTag property will always appear empt
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md b/exchange/exchange-ps/exchange/Get-ComplianceSearch.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
rename to exchange/exchange-ps/exchange/Get-ComplianceSearch.md
index 92d5c4ff7f..95ca1983f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceSearch.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancesearch
applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+title: Get-ComplianceSearch
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compliancesearch
-schema: 2.0.0
-title: Get-ComplianceSearch
+ms.reviewer:
---
# Get-ComplianceSearch
@@ -55,9 +54,6 @@ This examples show details of the compliance search named Case 1234.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Identity parameter specifies the compliance search that you want to view.
You can use any value that uniquely identifies the compliance search. For example:
@@ -85,6 +81,7 @@ To view these properties, you need to use the Identity parameter in the command.
Type: ComplianceSearchIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: 1
@@ -94,9 +91,6 @@ Accept wildcard characters: False
```
### -Case
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The Case parameter filters the results by the name of an eDiscovery Standard case that the compliance search is associated with. If the value contains spaces, enclose the value in quotation marks.
@@ -107,6 +101,7 @@ You can't use this parameter to view compliance searches associated with eDiscov
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -116,9 +111,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -127,6 +119,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -136,15 +129,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
rename to exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md
index bb1a32696a..a0ca0a62b5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceSearchAction.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancesearchaction
applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+title: Get-ComplianceSearchAction
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compliancesearchaction
-schema: 2.0.0
-title: Get-ComplianceSearchAction
+ms.reviewer:
---
# Get-ComplianceSearchAction
@@ -97,9 +96,6 @@ This example shows details about the compliance search action named "Case 1234_P
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Identity parameter specifies the compliance search action that you want to view. You can use any value that uniquely identifies the compliance search action. For example:
- Name: The compliance search action name uses the syntax `"Compliance Search Name_Action"`. For example, `"Case 1234_Preview"`.
@@ -119,6 +115,7 @@ When you use the Identity parameter, more details are returned in the results. F
Type: ComplianceSearchActionIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: 1
@@ -128,9 +125,6 @@ Accept wildcard characters: False
```
### -Case
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The Case parameter filters the results by the name of the specified case. If the value contains spaces, enclose the value in quotation marks.
@@ -139,6 +133,7 @@ The Case parameter filters the results by the name of the specified case. If the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -148,15 +143,13 @@ Accept wildcard characters: False
```
### -Details
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Details switch specifies whether to include detailed information in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -166,9 +159,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
This parameter is functional only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -177,6 +167,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -186,9 +177,6 @@ Accept wildcard characters: False
```
### -Export
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
The Export switch filters the results by Export compliance search actions. You don't need to specify a value with this switch.
@@ -199,6 +187,7 @@ You can't use this switch with the Identity, Preview, or Purge parameters.
Type: SwitchParameter
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -208,15 +197,13 @@ Accept wildcard characters: False
```
### -IncludeCredential
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The IncludeCredential switch specifies whether to include the credential in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -226,9 +213,6 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -237,6 +221,7 @@ This parameter is reserved for internal Microsoft use.
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -246,9 +231,6 @@ Accept wildcard characters: False
```
### -Preview
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Preview switch filters the results by Preview compliance search actions. You don't need to specify a value with this switch.
You can't use this switch with the Export, Identity, or Purge parameters.
@@ -257,6 +239,7 @@ You can't use this switch with the Export, Identity, or Purge parameters.
Type: SwitchParameter
Parameter Sets: Preview
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -266,9 +249,6 @@ Accept wildcard characters: False
```
### -Purge
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: In Security & Compliance PowerShell, this parameter is available only in the Search and Purge role. By default, this role is assigned only to the Organization Management and Data Investigator role groups.
The Purge switch filters the results by Purge compliance search actions. You don't need to specify a value with this switch.
@@ -279,6 +259,7 @@ You can't use this switch with the Export, Identity, or Preview parameters.
Type: SwitchParameter
Parameter Sets: Purge
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -288,15 +269,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md
rename to exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md
index 1bf2a33a12..0c3ff1f88a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceSecurityFilter.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancesecurityfilter
applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+title: Get-ComplianceSecurityFilter
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compliancesecurityfilter
-schema: 2.0.0
-title: Get-ComplianceSecurityFilter
+ms.reviewer:
---
# Get-ComplianceSecurityFilter
@@ -54,9 +53,6 @@ This example returns detailed information about the compliance security filter n
## PARAMETERS
### -Action
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Action parameter filters the results by the type of search action that a filter is applied to. Valid values are:
- Export: The filter is applied when exporting search results, or preparing them for analysis in eDiscovery Premium.
@@ -69,6 +65,7 @@ The Action parameter filters the results by the type of search action that a fil
Type: ComplianceSecurityFilterActionType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -90,6 +84,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -99,15 +94,13 @@ Accept wildcard characters: False
```
### -FilterName
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The FilterName parameter specifies the name of the compliance security filter that you want to view. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -117,9 +110,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The User parameter filters the results by the user who gets a filter applied to their searches. Valid values are:
- The alias or email address of a user.
@@ -130,6 +120,7 @@ The User parameter filters the results by the user who gets a filter applied to
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -139,15 +130,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTag.md b/exchange/exchange-ps/exchange/Get-ComplianceTag.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTag.md
rename to exchange/exchange-ps/exchange/Get-ComplianceTag.md
index 6f58f8329b..2c704b8488 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTag.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceTag.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancetag
applicable: Exchange Online, Security & Compliance
+title: Get-ComplianceTag
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compliancetag
-schema: 2.0.0
-title: Get-ComplianceTag
+ms.reviewer:
---
# Get-ComplianceTag
@@ -50,9 +49,6 @@ This example returns detailed information about the label named HR Content.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the label that you want to view. You can use any value that uniquely identifies the tag. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the label that you want to view. You can use an
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -72,15 +69,13 @@ Accept wildcard characters: False
```
### -IncludingLabelState
-
-> Applicable: Exchange Online, Security & Compliance
-
{{ Fill IncludingLabelState Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -90,15 +85,13 @@ Accept wildcard characters: False
```
### -PriorityCleanup
-
-> Applicable: Security & Compliance
-
{{ Fill PriorityCleanup Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTagStorage.md b/exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTagStorage.md
rename to exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md
index 668ad3eb8a..c3aa8eaca3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceTagStorage.md
+++ b/exchange/exchange-ps/exchange/Get-ComplianceTagStorage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compliancetagstorage
applicable: Exchange Online, Security & Compliance
+title: Get-ComplianceTagStorage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compliancetagstorage
-schema: 2.0.0
-title: Get-ComplianceTagStorage
+ms.reviewer:
---
# Get-ComplianceTagStorage
@@ -42,9 +41,6 @@ This example confirms that you've created the label policy in your organization.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the label policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name (GUID value)
@@ -57,6 +53,7 @@ However, there can be only one label policy in your organization.
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -66,15 +63,13 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md b/exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md
rename to exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md
index 5f7e8ed48b..d26e9e5e0d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md
+++ b/exchange/exchange-ps/exchange/Get-CompromisedUserAggregateReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compromiseduseraggregatereport
applicable: Exchange Online, Exchange Online Protection
+title: Get-CompromisedUserAggregateReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compromiseduseraggregatereport
-schema: 2.0.0
-title: Get-CompromisedUserAggregateReport
+ms.reviewer:
---
# Get-CompromisedUserAggregateReport
@@ -52,9 +51,6 @@ This example returns all restricted user accounts for the specified date range.
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Action parameter filters the results by the compromised user status. Valid values are:
- Restricted
@@ -66,6 +62,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -86,6 +80,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -113,15 +106,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -131,9 +122,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -142,6 +130,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md b/exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md
rename to exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md
index 5b8fba0918..07d5d63148 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md
+++ b/exchange/exchange-ps/exchange/Get-CompromisedUserDetailReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-compromiseduserdetailreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-CompromisedUserDetailReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-compromiseduserdetailreport
-schema: 2.0.0
-title: Get-CompromisedUserDetailReport
+ms.reviewer:
---
# Get-CompromisedUserDetailReport
@@ -52,9 +51,6 @@ This example returns all suspicious user accounts for the specified date range.
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Action parameter filters the results by the compromised user status. Valid values are:
- Restricted
@@ -66,6 +62,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -86,6 +80,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -113,15 +106,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -131,9 +122,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -144,6 +132,7 @@ A value for this parameter can't be older than 30 days.
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md b/exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md
rename to exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md
index 3d946278f6..ff118bc38d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md
+++ b/exchange/exchange-ps/exchange/Get-ConfigAnalyzerPolicyRecommendation.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-configanalyzerpolicyrecommendation
applicable: Exchange Online
+title: Get-ConfigAnalyzerPolicyRecommendation
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-configanalyzerpolicyrecommendation
-schema: 2.0.0
-title: Get-ConfigAnalyzerPolicyRecommendation
+ms.reviewer:
---
# Get-ConfigAnalyzerPolicyRecommendation
@@ -63,15 +62,13 @@ This example runs a comparison using the Strict preset security policy settings
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: ConfigAnalyzerPolicyRecommendationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -81,9 +78,6 @@ Accept wildcard characters: False
```
### -RecommendedPolicyType
-
-> Applicable: Exchange Online
-
The RecommendedPolicyType parameter specifies the preset security policy that you want to use as a baseline. Valid values are:
- Standard
@@ -93,6 +87,7 @@ The RecommendedPolicyType parameter specifies the preset security policy that yo
Type: RecommendedPolicyType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -102,9 +97,6 @@ Accept wildcard characters: False
```
### -IsAppliedToDisabled
-
-> Applicable: Exchange Online
-
The IsAppliedToDisabled switch filters the results by policies that aren't applied to anyone (the AppliedTo property is blank). You don't need to specify a value with this switch.
If you don't use this switch, the results include policies that are applied to users and policies that aren't applied to anyone.
@@ -113,6 +105,7 @@ If you don't use this switch, the results include policies that are applied to u
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ConnectionInformation.md b/exchange/exchange-ps/exchange/Get-ConnectionInformation.md
similarity index 97%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ConnectionInformation.md
rename to exchange/exchange-ps/exchange/Get-ConnectionInformation.md
index 0f80193cf7..97f9d3efd2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ConnectionInformation.md
+++ b/exchange/exchange-ps/exchange/Get-ConnectionInformation.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.ExoPowershellGalleryModule.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-connectioninformation
applicable: Exchange Online
+title: Get-ConnectionInformation
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.ExoPowershellGalleryModule.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-connectioninformation
-schema: 2.0.0
-title: Get-ConnectionInformation
+ms.reviewer:
---
# Get-ConnectionInformation
@@ -87,9 +87,6 @@ This example returns a list of active REST-based connections that are using the
## PARAMETERS
### -ConnectionId
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.2.0 or later of the module.
The ConnectionId parameter filters the connections by ConnectionId. ConnectionId is a GUID value in the output of the Get-ConnectionInformation cmdlet that uniquely identifies a connection, even if you have multiple connections open. You can specify multiple ConnectionId values separated by commas.
@@ -100,6 +97,7 @@ Don't use this parameter with the ModulePrefix parameter.
Type: String[]
Parameter Sets: ConnectionId
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -109,9 +107,6 @@ Accept wildcard characters: False
```
### -ModulePrefix
-
-> Applicable: Exchange Online
-
**Note**: This parameter is available in version 3.2.0 or later of the module.
The ModulePrefix parameter filters the connections by ModulePrefix. When you use the Prefix parameter with the Connect-ExchangeOnline cmdlet, the specified text is added to the names of all Exchange Online cmdlets (for example, Get-InboundConnector becomes Get-ContosoInboundConnector). The ModulePrefix value is visible in the output of the Get-ConnectionInformation cmdlet. You can specify multiple ModulePrefix values separated by commas.
@@ -124,6 +119,7 @@ Don't use this parameter with the ConnectionId parameter.
Type: String[]
Parameter Sets: ModulePrefix
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md b/exchange/exchange-ps/exchange/Get-Contact.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
rename to exchange/exchange-ps/exchange/Get-Contact.md
index 1fc5354a8a..389fa44712 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
+++ b/exchange/exchange-ps/exchange/Get-Contact.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-contact
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-Contact
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-contact
-schema: 2.0.0
-title: Get-Contact
+ms.reviewer:
---
# Get-Contact
@@ -80,9 +79,6 @@ This example uses the Anr parameter to retrieve all mail-enabled contacts whose
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the contact that you want to view. You can use any value that uniquely identifies the contact. For example:
- Name
@@ -94,6 +90,7 @@ The Identity parameter specifies the contact that you want to view. You can use
Type: ContactIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -103,9 +100,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -118,6 +112,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -127,9 +122,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -140,6 +132,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -149,9 +142,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -160,6 +150,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -169,9 +160,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -187,6 +175,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -196,9 +185,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -212,6 +198,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -221,9 +208,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -235,6 +219,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -244,9 +229,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -259,6 +241,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -268,9 +251,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RecipientTypeDetails parameter filters the results by the specified contact subtype. Valid values are:
- Contact
@@ -283,6 +263,7 @@ You can specify multiple values separated by commas.
Type: RecipientTypeDetails[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -292,15 +273,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -310,9 +289,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -330,6 +306,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md b/exchange/exchange-ps/exchange/Get-ContentFilterConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
rename to exchange/exchange-ps/exchange/Get-ContentFilterConfig.md
index 6a8e1dbce8..8de0cb720d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
+++ b/exchange/exchange-ps/exchange/Get-ContentFilterConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-contentfilterconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ContentFilterConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-contentfilterconfig
-schema: 2.0.0
-title: Get-ContentFilterConfig
+ms.reviewer:
---
# Get-ContentFilterConfig
@@ -41,9 +40,6 @@ This example returns detailed information about the content filter configuration
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -52,6 +48,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md b/exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
rename to exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md
index 9b20ec8f22..1b1f47b29b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/exchange/Get-ContentFilterPhrase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-contentfilterphrase
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ContentFilterPhrase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-contentfilterphrase
-schema: 2.0.0
-title: Get-ContentFilterPhrase
+ms.reviewer:
---
# Get-ContentFilterPhrase
@@ -64,9 +63,6 @@ This example returns all custom words and phrases that contain the words free of
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies a custom word or phrase to display. You must enclose the value of the Identity parameter in quotation marks (").
The Identity and Phrase parameters are interchangeable.
@@ -75,6 +71,7 @@ The Identity and Phrase parameters are interchangeable.
Type: ContentFilterPhraseIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -84,9 +81,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -95,6 +89,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -104,9 +99,6 @@ Accept wildcard characters: False
```
### -Phrase
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Phrase parameter specifies a custom word or phrase to display. You must enclose the value of the Phrase parameter in quotation marks (").
The Phrase and Identity parameters are interchangeable.
@@ -115,6 +107,7 @@ The Phrase and Identity parameters are interchangeable.
Type: ContentFilterPhraseIdParameter
Parameter Sets: Phrase
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md b/exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md
rename to exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md
index 0769430b82..2c884d0e2f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md
+++ b/exchange/exchange-ps/exchange/Get-ContentMalwareMdoAggregateReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-contentmalwaremdoaggregatereport
applicable: Exchange Online
+title: Get-ContentMalwareMdoAggregateReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-contentmalwaremdoaggregatereport
-schema: 2.0.0
-title: Get-ContentMalwareMdoAggregateReport
+ms.reviewer:
---
# Get-ContentMalwareMdoAggregateReport
@@ -56,9 +55,6 @@ This example returns the results for OneDrive detections for the specified date
## PARAMETERS
### -DetectionTechnology
-
-> Applicable: Exchange Online
-
The DetectionTechnology parameter filters the results by what classified the file as malware. Valid values are:
- AntiMalware
@@ -71,6 +67,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -80,9 +77,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2021 to specify September 1, 2021.
@@ -91,6 +85,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -100,15 +95,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -118,15 +111,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -136,9 +127,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2021 to specify September 1, 2021.
@@ -147,6 +135,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -156,9 +145,6 @@ Accept wildcard characters: False
```
### -Workload
-
-> Applicable: Exchange Online
-
The Workload parameter filters the results by where the detected file is located. Valid values are:
- OneDriveForBusiness
@@ -171,6 +157,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md b/exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md
rename to exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md
index ce69c30ab3..eb99b53c05 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md
+++ b/exchange/exchange-ps/exchange/Get-ContentMalwareMdoDetailReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-contentmalwaremdodetailreport
applicable: Exchange Online
+title: Get-ContentMalwareMdoDetailReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-contentmalwaremdodetailreport
-schema: 2.0.0
-title: Get-ContentMalwareMdoDetailReport
+ms.reviewer:
---
# Get-ContentMalwareMdoDetailReport
@@ -58,9 +57,6 @@ This example returns the results for detections by Safe Attachments for SharePoi
## PARAMETERS
### -DetectionTechnology
-
-> Applicable: Exchange Online
-
The DetectionTechnology parameter filters the results by what classified the file as malware. Valid values are:
- AntiMalware
@@ -73,6 +69,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2021 to specify September 1, 2021.
@@ -93,6 +87,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -102,15 +97,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -120,15 +113,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -138,9 +129,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2021 to specify September 1, 2021.
@@ -149,6 +137,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -158,9 +147,6 @@ Accept wildcard characters: False
```
### -Workload
-
-> Applicable: Exchange Online
-
The Workload parameter filters the results by where the detected file is located. Valid values are:
- OneDriveForBusiness
@@ -173,6 +159,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md b/exchange/exchange-ps/exchange/Get-DataClassification.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
rename to exchange/exchange-ps/exchange/Get-DataClassification.md
index 271b48a173..9bfe9cc832 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
+++ b/exchange/exchange-ps/exchange/Get-DataClassification.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dataclassification
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-DataClassification
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dataclassification
-schema: 2.0.0
-title: Get-DataClassification
+ms.reviewer:
---
# Get-DataClassification
@@ -15,7 +14,7 @@ title: Get-DataClassification
## SYNOPSIS
This cmdlet is functional only in on-premises Exchange.
-In Exchange Online, this cmdlet has been replaced by the [Get-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
+In Exchange Online, this cmdlet has been replaced by the [Get-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchange/get-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
Use the Get-DataClassification cmdlet to view the data classification rules in your organization. This cmdlet shows built-in data classification rules and rules that you created that use document fingerprints.
@@ -68,15 +67,13 @@ This example returns details of the built-in data classification rule named SWIF
## PARAMETERS
### -ClassificationRuleCollectionIdentity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ClassificationRuleCollectionIdentity parameter filters the results by the name of the data classification rule collection. The data classification rule collection that contains the built-in data classification rules is named Microsoft Rule Package. The data classification that contains new data classification rules that you create that use document fingerprints is named Fingerprint Classification Collection.
```yaml
Type: ClassificationRuleCollectionIdParameter
Parameter Sets: RuleCollectionIdentity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -86,9 +83,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the data classification rule that you want to view. You can use any value that uniquely identifies the data classification rule. For example:
- Name
@@ -99,6 +93,7 @@ The Identity parameter specifies the data classification rule that you want to v
Type: DataClassificationIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -108,15 +103,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md b/exchange/exchange-ps/exchange/Get-DataClassificationConfig.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md
rename to exchange/exchange-ps/exchange/Get-DataClassificationConfig.md
index 39e8fca684..03342c3e31 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md
+++ b/exchange/exchange-ps/exchange/Get-DataClassificationConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dataclassificationconfig
applicable: Exchange Online
+title: Get-DataClassificationConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dataclassificationconfig
-schema: 2.0.0
-title: Get-DataClassificationConfig
+ms.reviewer:
---
# Get-DataClassificationConfig
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md b/exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md
rename to exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md
index e21fd13b90..b58632caa0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-DataEncryptionPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dataencryptionpolicy
applicable: Exchange Online, Exchange Online Protection
+title: Get-DataEncryptionPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dataencryptionpolicy
-schema: 2.0.0
-title: Get-DataEncryptionPolicy
+ms.reviewer:
---
# Get-DataEncryptionPolicy
@@ -55,9 +54,6 @@ The example returns detailed information for the data encryption policy named Eu
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the data encryption policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -68,6 +64,7 @@ The Identity parameter specifies the data encryption policy that you want to vie
Type: DataEncryptionPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -77,9 +74,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -89,6 +83,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -116,15 +109,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataRetentionReport.md b/exchange/exchange-ps/exchange/Get-DataRetentionReport.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DataRetentionReport.md
rename to exchange/exchange-ps/exchange/Get-DataRetentionReport.md
index 00ddff31db..1f38d8c687 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataRetentionReport.md
+++ b/exchange/exchange-ps/exchange/Get-DataRetentionReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dataretentionreport
applicable: Exchange Online, Security & Compliance
+title: Get-DataRetentionReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dataretentionreport
-schema: 2.0.0
-title: Get-DataRetentionReport
+ms.reviewer:
---
# Get-DataRetentionReport
@@ -53,9 +52,6 @@ This example lists the data detections for April, 2018.
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -64,6 +60,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -91,15 +86,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -109,9 +102,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -122,6 +112,7 @@ The StartDate value can't be older than 92 days from today.
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
rename to exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md
index 4077072041..6f519626b5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-databaseavailabilitygroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-DatabaseAvailabilityGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-databaseavailabilitygroup
-schema: 2.0.0
-title: Get-DatabaseAvailabilityGroup
+ms.reviewer:
---
# Get-DatabaseAvailabilityGroup
@@ -60,15 +59,13 @@ This example displays the properties of the DAG DAG2. Because it includes the St
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of the DAG to query.
```yaml
Type: DatabaseAvailabilityGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -78,15 +75,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -96,15 +91,13 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Status parameter instructs the command to query Active Directory for additional information and to include real-time status information in the output. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
rename to exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md
index 20964115f3..deb02d5a8e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/exchange/Get-DatabaseAvailabilityGroupNetwork.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-databaseavailabilitygroupnetwork
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-DatabaseAvailabilityGroupNetwork
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-databaseavailabilitygroupnetwork
-schema: 2.0.0
-title: Get-DatabaseAvailabilityGroupNetwork
+ms.reviewer:
---
# Get-DatabaseAvailabilityGroupNetwork
@@ -76,15 +75,13 @@ This example gets complete configuration and status information for the network
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of a DAG or a DAG network.
```yaml
Type: DatabaseAvailabilityGroupNetworkIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -94,15 +91,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -112,9 +107,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Mailbox server in the DAG to retrieve health information for the DAG network from. You can use any value that uniquely identifies the server. For example:
- Name
@@ -126,6 +118,7 @@ The Server parameter specifies the Mailbox server in the DAG to retrieve health
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantBriefingConfig.md b/exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantBriefingConfig.md
rename to exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md
index a10b574eb4..13ed2a7226 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantBriefingConfig.md
+++ b/exchange/exchange-ps/exchange/Get-DefaultTenantBriefingConfig.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-defaulttenantbriefingconfig
applicable: Exchange Online
+title: Get-DefaultTenantBriefingConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-defaulttenantbriefingconfig
-schema: 2.0.0
-title: Get-DefaultTenantBriefingConfig
+ms.reviewer:
---
# Get-DefaultTenantBriefingConfig
@@ -55,15 +55,13 @@ This example returns the default Briefing email configuration for the organizati
## PARAMETERS
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantMyAnalyticsFeatureConfig.md b/exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantMyAnalyticsFeatureConfig.md
rename to exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md
index 7e45af76f7..76bb40fd28 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DefaultTenantMyAnalyticsFeatureConfig.md
+++ b/exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-defaulttenantmyanalyticsfeatureconfig
applicable: Exchange Online
+title: Get-DefaultTenantMyAnalyticsFeatureConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-defaulttenantmyanalyticsfeatureconfig
-schema: 2.0.0
-title: Get-DefaultTenantMyAnalyticsFeatureConfig
+ms.reviewer:
---
# Get-DefaultTenantMyAnalyticsFeatureConfig
@@ -51,15 +51,13 @@ This example returns the default opt-in or opt-out information for the various V
## PARAMETERS
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md b/exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
rename to exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md
index 5fe36fb545..363d35c76f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/exchange/Get-DeliveryAgentConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-deliveryagentconnector
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-DeliveryAgentConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-deliveryagentconnector
-schema: 2.0.0
-title: Get-DeliveryAgentConnector
+ms.reviewer:
---
# Get-DeliveryAgentConnector
@@ -51,15 +50,13 @@ This example retrieves a list of all delivery agent connectors in your organizat
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the GUID or name of the delivery agent connector.
```yaml
Type: DeliveryAgentConnectorIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -80,6 +74,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md b/exchange/exchange-ps/exchange/Get-DetailZapReport.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md
rename to exchange/exchange-ps/exchange/Get-DetailZapReport.md
index 0c93ed0d8a..e2332bf377 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md
+++ b/exchange/exchange-ps/exchange/Get-DetailZapReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-detailzapreport
applicable: Exchange Online
+title: Get-DetailZapReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-detailzapreport
-schema: 2.0.0
-title: Get-DetailZapReport
+ms.reviewer:
---
# Get-DetailZapReport
@@ -69,9 +68,6 @@ This example retrieves information for the specified date range.
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only. If you enter the date, enclose the value in quotation marks ("), for example, "09/01/2018".
@@ -82,6 +78,7 @@ If you use this parameter, you also need to use the StartDate parameter.
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -91,15 +88,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 2
@@ -109,15 +104,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 3
@@ -127,9 +120,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018".
@@ -140,6 +130,7 @@ If you use this parameter, you also need to use the StartDate parameter.
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 4
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md b/exchange/exchange-ps/exchange/Get-DetailsTemplate.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
rename to exchange/exchange-ps/exchange/Get-DetailsTemplate.md
index f04bcdd675..71900617a9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
+++ b/exchange/exchange-ps/exchange/Get-DetailsTemplate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-detailstemplate
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-DetailsTemplate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-detailstemplate
-schema: 2.0.0
-title: Get-DetailsTemplate
+ms.reviewer:
---
# Get-DetailsTemplate
@@ -60,9 +59,6 @@ This example retrieves all attributes for all User details template types in all
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the GUID of the details template or specifies the details template type and language separated by a backslash, for example, en-us\\User. Details template types are:
- User
@@ -76,6 +72,7 @@ The Identity parameter specifies the GUID of the details template or specifies t
Type: DetailsTemplateIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -85,9 +82,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -97,6 +91,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -106,15 +101,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -124,15 +117,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessPolicy.md
rename to exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md
index 1992dc68e8..a79926c166 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-deviceconditionalaccesspolicy
applicable: Exchange Online, Security & Compliance
+title: Get-DeviceConditionalAccessPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-deviceconditionalaccesspolicy
-schema: 2.0.0
-title: Get-DeviceConditionalAccessPolicy
+ms.reviewer:
---
# Get-DeviceConditionalAccessPolicy
@@ -57,9 +56,6 @@ This example shows details about the mobile device conditional access policy nam
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the mobile device conditional access policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -70,6 +66,7 @@ The Identity parameter specifies the mobile device conditional access policy tha
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessRule.md b/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessRule.md
rename to exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md
index 292589b539..65fe845674 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConditionalAccessRule.md
+++ b/exchange/exchange-ps/exchange/Get-DeviceConditionalAccessRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-deviceconditionalaccessrule
applicable: Exchange Online, Security & Compliance
+title: Get-DeviceConditionalAccessRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-deviceconditionalaccessrule
-schema: 2.0.0
-title: Get-DeviceConditionalAccessRule
+ms.reviewer:
---
# Get-DeviceConditionalAccessRule
@@ -59,15 +58,13 @@ This example shows details for the mobile device conditional access rule named S
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the mobile device conditional access rule that you want to view. The name of the rule uses the syntax `{}`. For example, `Secure Email{914f151c-394b-4da9-9422-f5a2f65dec30}`.
```yaml
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -77,15 +74,13 @@ Accept wildcard characters: False
```
### -CompareToWorkload
-
-> Applicable: Security & Compliance
-
The CompareToWorkload switch specifies whether to compare the mobile device conditional access rule to Intune rules. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationPolicy.md
rename to exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md
index 506cbd4331..34e6dc1ae0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-DeviceConfigurationPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-deviceconfigurationpolicy
applicable: Exchange Online, Security & Compliance
+title: Get-DeviceConfigurationPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-deviceconfigurationpolicy
-schema: 2.0.0
-title: Get-DeviceConfigurationPolicy
+ms.reviewer:
---
# Get-DeviceConfigurationPolicy
@@ -57,9 +56,6 @@ This example shows details about the mobile device configuration policy named En
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the mobile device configuration policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -70,6 +66,7 @@ The Identity parameter specifies the mobile device configuration policy that you
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationRule.md b/exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationRule.md
rename to exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md
index a0fadfef90..84afa08d75 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceConfigurationRule.md
+++ b/exchange/exchange-ps/exchange/Get-DeviceConfigurationRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-deviceconfigurationrule
applicable: Exchange Online, Security & Compliance
+title: Get-DeviceConfigurationRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-deviceconfigurationrule
-schema: 2.0.0
-title: Get-DeviceConfigurationRule
+ms.reviewer:
---
# Get-DeviceConfigurationRule
@@ -59,15 +58,13 @@ This example shows details about the mobile device configuration rule named Lega
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the mobile device configuration rule that you want to view. The name of the rule uses the syntax `{}`. For example, `Legal Team{58b50d1c-2b18-461c-8893-3e20c648b136}`.
```yaml
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -77,15 +74,13 @@ Accept wildcard characters: False
```
### -CompareToWorkload
-
-> Applicable: Security & Compliance
-
The CompareToWorkload switch specifies whether to compare the mobile device configuration rule to Intune rules. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DevicePolicy.md b/exchange/exchange-ps/exchange/Get-DevicePolicy.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DevicePolicy.md
rename to exchange/exchange-ps/exchange/Get-DevicePolicy.md
index 147936b675..f7cb5c1dce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DevicePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-DevicePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-devicepolicy
applicable: Exchange Online, Security & Compliance
+title: Get-DevicePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-devicepolicy
-schema: 2.0.0
-title: Get-DevicePolicy
+ms.reviewer:
---
# Get-DevicePolicy
@@ -57,9 +56,6 @@ This example shows details about the mobile device policy named Engineering Grou
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the mobile device policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -70,6 +66,7 @@ The Identity parameter specifies the mobile device policy that you want to view.
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantPolicy.md
rename to exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md
index cadb9db2ee..ce5c1c516e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-DeviceTenantPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-devicetenantpolicy
applicable: Exchange Online, Security & Compliance
+title: Get-DeviceTenantPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-devicetenantpolicy
-schema: 2.0.0
-title: Get-DeviceTenantPolicy
+ms.reviewer:
---
# Get-DeviceTenantPolicy
@@ -50,15 +49,13 @@ This example shows information for your organization's mobile device tenant poli
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the name of the mobile device tenant policy that you want to view, but there's only one in your organization. The name of the policy is a GUID value. For example, a6958701-c82c-4064-ac11-64e40e7f4032.
```yaml
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantRule.md b/exchange/exchange-ps/exchange/Get-DeviceTenantRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantRule.md
rename to exchange/exchange-ps/exchange/Get-DeviceTenantRule.md
index e97fbba444..3d61488bdc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeviceTenantRule.md
+++ b/exchange/exchange-ps/exchange/Get-DeviceTenantRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-devicetenantrule
applicable: Exchange Online, Security & Compliance
+title: Get-DeviceTenantRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-devicetenantrule
-schema: 2.0.0
-title: Get-DeviceTenantRule
+ms.reviewer:
---
# Get-DeviceTenantRule
@@ -51,15 +50,13 @@ This example shows information for your organization's mobile device tenant rule
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the name of the mobile device tenant rule that you want to view, but there's only one in your organization. The name of the rule is a GUID value. For example, 7577c5f3-05a4-4f55-a0a3-82aab5e98c84.
```yaml
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md b/exchange/exchange-ps/exchange/Get-DistributionGroup.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
rename to exchange/exchange-ps/exchange/Get-DistributionGroup.md
index 5603596725..d91f0fd648 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
+++ b/exchange/exchange-ps/exchange/Get-DistributionGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-distributiongroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-DistributionGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-distributiongroup
-schema: 2.0.0
-title: Get-DistributionGroup
+ms.reviewer:
---
# Get-DistributionGroup
@@ -113,9 +112,6 @@ This example returns all distribution groups and mail-enabled security groups wh
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the distribution group or mail-enabled security group that you want to view. You can use any values that uniquely identifies the group. For example:
- Name
@@ -129,6 +125,7 @@ The Identity parameter specifies the distribution group or mail-enabled security
Type: DistributionGroupIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -138,9 +135,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -153,6 +147,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -162,9 +157,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -173,6 +165,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -182,9 +175,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -193,6 +183,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -202,9 +193,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -220,6 +208,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -229,9 +218,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -245,6 +231,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -254,9 +241,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of AcceptMessagesOnlyFromDLMembers recipients in the AcceptMessagesOnlyFromDLMembersWithDisplayNames property. You don't need to specify a value with this switch.
@@ -267,6 +251,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -276,9 +261,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of AcceptMessagesOnlyFromSendersOrMembers recipients in the AcceptMessagesOnlyFromSendersOrMembersWithDisplayNames property. You don't need to specify a value with this switch.
@@ -289,6 +271,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -298,9 +281,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeAcceptMessagesOnlyFromWithDisplayNames switch specifies whether to return the SMTP addresses and display names of AcceptMessagesOnlyFrom recipients in the AcceptMessagesOnlyFromWithDisplayNames property. You don't need to specify a value with this switch.
@@ -311,6 +291,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -320,9 +301,6 @@ Accept wildcard characters: False
```
### -IncludeBypassModerationFromSendersOrMembersWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeBypassModerationFromSendersOrMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of BypassModerationFromSendersOrMembers recipients in the BypassModerationFromSendersOrMembersWithDisplayNames property. You don't need to specify a value with this switch.
@@ -333,6 +311,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -342,9 +321,6 @@ Accept wildcard characters: False
```
### -IncludeGrantSendOnBehalfToWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeGrantSendOnBehalfToWithDisplayNames switch specifies whether to return the SMTP addresses and display names of GrantSendOnBehalfTo recipients in the GrantSendOnBehalfToWithDisplayNames property. You don't need to specify a value with this switch.
@@ -355,6 +331,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -364,9 +341,6 @@ Accept wildcard characters: False
```
### -IncludeManagedByWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeManagedByWithDisplayNames switch specifies whether to return the SMTP addresses and display names of group owners in the ManagedByWithDisplayNames property. You don't need to specify a value with this switch.
@@ -377,6 +351,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -386,9 +361,6 @@ Accept wildcard characters: False
```
### -IncludeModeratedByWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeModeratedByWithDisplayNames switch specifies whether to return the SMTP addresses and display names of ModeratedBy recipients in the ModeratedByWithDisplayNames property. You don't need to specify a value with this switch.
@@ -399,6 +371,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -408,9 +381,6 @@ Accept wildcard characters: False
```
### -ManagedBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ManagedBy parameter filters the results by the owner of the group. You can use any value that uniquely identifies the owner. For example:
- Name
@@ -424,6 +394,7 @@ The ManagedBy parameter filters the results by the owner of the group. You can u
Type: GeneralRecipientIdParameter
Parameter Sets: ManagedBySet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -433,9 +404,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -447,6 +415,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -456,9 +425,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -471,6 +437,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -480,9 +447,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RecipientTypeDetails parameter filters the results by the specified distribution group subtype. Valid values are:
- MailNonUniversalGroup
@@ -496,6 +460,7 @@ You can specify multiple values separated by commas.
Type: RecipientTypeDetails[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -505,15 +470,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -523,9 +486,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -545,6 +505,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md b/exchange/exchange-ps/exchange/Get-DistributionGroupMember.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
rename to exchange/exchange-ps/exchange/Get-DistributionGroupMember.md
index 1d9b8bb4fd..3113e769e2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
+++ b/exchange/exchange-ps/exchange/Get-DistributionGroupMember.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-distributiongroupmember
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-DistributionGroupMember
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-distributiongroupmember
-schema: 2.0.0
-title: Get-DistributionGroupMember
+ms.reviewer:
---
# Get-DistributionGroupMember
@@ -75,9 +74,6 @@ In the cloud-based service, this example downloads a comma-separated value (CSV)
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the distribution group or mail-enabled security group. You can use any value that uniquely identifies the group. For example:
- Name
@@ -91,6 +87,7 @@ The Identity parameter specifies the distribution group or mail-enabled security
Type: DistributionGroupMemberIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -100,9 +97,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -111,6 +105,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -120,9 +115,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -131,6 +123,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -140,9 +133,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -156,6 +146,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -165,9 +156,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedObjects
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The IncludeSoftDeletedGroups switch specifies whether to include soft-deleted group members in the results. You don't need to specify a value with this switch.
@@ -178,6 +166,7 @@ Soft-deleted group members are deleted Microsoft 365 Groups or mailboxes that ar
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -187,9 +176,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -202,6 +188,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -211,15 +198,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md b/exchange/exchange-ps/exchange/Get-DkimSigningConfig.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md
rename to exchange/exchange-ps/exchange/Get-DkimSigningConfig.md
index f26a3f5385..9fe8d4bfd8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md
+++ b/exchange/exchange-ps/exchange/Get-DkimSigningConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dkimsigningconfig
applicable: Exchange Online, Exchange Online Protection
+title: Get-DkimSigningConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dkimsigningconfig
-schema: 2.0.0
-title: Get-DkimSigningConfig
+ms.reviewer:
---
# Get-DkimSigningConfig
@@ -50,9 +49,6 @@ This example shows detailed information for the DKIM signing policy for contoso.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the DKIM signing policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name: The domain name (for example, contoso.com).
@@ -63,6 +59,7 @@ The Identity parameter specifies the DKIM signing policy that you want to view.
Type: DkimSigningConfigIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpCompliancePolicy.md
rename to exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md
index 50f80e0531..f5a379ed1b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpCompliancePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpcompliancepolicy
applicable: Security & Compliance
+title: Get-DlpCompliancePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpcompliancepolicy
-schema: 2.0.0
-title: Get-DlpCompliancePolicy
+ms.reviewer:
---
# Get-DlpCompliancePolicy
@@ -70,9 +69,6 @@ This example gets all of the DLP policies in an environment and displays the dis
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the DLP policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -84,6 +80,7 @@ The Identity parameter specifies the DLP policy that you want to view. You can u
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -93,15 +90,13 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Security & Compliance
-
{{ Fill DisplayName Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -111,9 +106,6 @@ Accept wildcard characters: False
```
### -DistributionDetail
-
-> Applicable: Security & Compliance
-
The DistributionDetail switch returns detailed policy distribution information in the DistributionResults property. You don't need to specify a value with this switch.
**Tip**: The DistributionResults property is unreliable and prone to errors.
@@ -122,6 +114,7 @@ The DistributionDetail switch returns detailed policy distribution information i
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -131,15 +124,13 @@ Accept wildcard characters: False
```
### -ForceValidate
-
-> Applicable: Security & Compliance
-
{{ Fill ForceValidate Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -149,15 +140,13 @@ Accept wildcard characters: False
```
### -IncludeExtendedProperties
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeExtendedProperties Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -167,15 +156,13 @@ Accept wildcard characters: False
```
### -IncludeRulesMetadata
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeRulesMetadata Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -185,15 +172,13 @@ Accept wildcard characters: False
```
### -IRMUserRiskConfiguredAnyRule
-
-> Applicable: Security & Compliance
-
{{ Fill IRMUserRiskConfiguredAnyRule Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -203,15 +188,13 @@ Accept wildcard characters: False
```
### -IncludeSimulationResults
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeSimulationResults Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -221,15 +204,13 @@ Accept wildcard characters: False
```
### -Summary
-
-> Applicable: Security & Compliance
-
{{ Fill Summary Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpComplianceRule.md b/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpComplianceRule.md
rename to exchange/exchange-ps/exchange/Get-DlpComplianceRule.md
index 0903acec7c..3ec06ed550 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpComplianceRule.md
+++ b/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpcompliancerule
applicable: Security & Compliance
+title: Get-DlpComplianceRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpcompliancerule
-schema: 2.0.0
-title: Get-DlpComplianceRule
+ms.reviewer:
---
# Get-DlpComplianceRule
@@ -58,9 +57,6 @@ This example lists all the rules included in the DLP compliance policy named "PI
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the DLP rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -72,6 +68,7 @@ The Identity parameter specifies the DLP rule that you want to view. You can use
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -81,15 +78,13 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Security & Compliance
-
{{ Fill DisplayName Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -99,15 +94,13 @@ Accept wildcard characters: False
```
### -IncludeExecutionRuleGuids
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeExecutionRuleGuids Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -117,9 +110,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter specifies the DLP policy that contains the rules. Using this parameter returns all rules that are assigned to the specified policy. Valid input for this parameter is any value that uniquely identifies the policy. For example
- Name
@@ -131,6 +121,7 @@ The Policy parameter specifies the DLP policy that contains the rules. Using thi
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md b/exchange/exchange-ps/exchange/Get-DlpDetailReport.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md
rename to exchange/exchange-ps/exchange/Get-DlpDetailReport.md
index 9b5a04d968..ec4460246a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md
+++ b/exchange/exchange-ps/exchange/Get-DlpDetailReport.md
@@ -1,19 +1,18 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpdetailreport
applicable: Exchange Online, Security & Compliance
+title: Get-DlpDetailReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpdetailreport
-schema: 2.0.0
-title: Get-DlpDetailReport
+ms.reviewer:
---
# Get-DlpDetailReport
## SYNOPSIS
-**Note**: This cmdlet has been retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet.
+**Note**: This cmdlet has been retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet.
This cmdlet is available only in the cloud-based service.
@@ -59,7 +58,7 @@ The Get-DlpDetailReport cmdlet returns detailed information about specific DLP r
- Recipients
- AttachmentNames
-To see DLP detection data that's aggregated per day, use the [Get-DlpDetectionsReport](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpdetectionsreport) cmdlet.
+To see DLP detection data that's aggregated per day, use the [Get-DlpDetectionsReport](https://learn.microsoft.com/powershell/module/exchange/get-dlpdetectionsreport) cmdlet.
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
@@ -75,9 +74,6 @@ The following example lists the details of all the DLP policy activities defined
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Security & Compliance
-
The Action parameter filters the report by the action taken by DLP policies. Valid values are:
- BlockAccess
@@ -90,6 +86,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -99,9 +96,6 @@ Accept wildcard characters: False
```
### -Actor
-
-> Applicable: Exchange Online, Security & Compliance
-
The Actor parameter filters the report by the user who last modified the item. You can enter multiple users separated by commas.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -110,6 +104,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -119,9 +114,6 @@ Accept wildcard characters: False
```
### -DlpCompliancePolicy
-
-> Applicable: Exchange Online, Security & Compliance
-
The DlpCompliancePolicy parameter filters the report by the name of the DLP compliance policy. You can specify multiple policies separated by commas.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -130,6 +122,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -139,9 +132,6 @@ Accept wildcard characters: False
```
### -DlpComplianceRule
-
-> Applicable: Exchange Online, Security & Compliance
-
The DlpComplianceRule parameter filters the report by the name of the DLP compliance rule. You can specify multiple rules separated by commas.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -150,6 +140,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -159,9 +150,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -170,6 +158,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -179,9 +168,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Security & Compliance
-
The EventType parameter filters the report by the event type. Valid values are:
- DLPActionHits
@@ -200,6 +186,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -209,15 +196,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -227,15 +212,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -245,9 +228,6 @@ Accept wildcard characters: False
```
### -Source
-
-> Applicable: Exchange Online, Security & Compliance
-
The Source parameter filters the report by workload. Valid values are:
- EXCH: Exchange Online
@@ -260,6 +240,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -269,9 +250,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -280,6 +258,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md b/exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md
rename to exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md
index 2668fc6b73..be1c5ba605 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md
+++ b/exchange/exchange-ps/exchange/Get-DlpDetectionsReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpdetectionsreport
applicable: Exchange Online, Security & Compliance
+title: Get-DlpDetectionsReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpdetectionsreport
-schema: 2.0.0
-title: Get-DlpDetectionsReport
+ms.reviewer:
---
# Get-DlpDetectionsReport
@@ -15,7 +14,7 @@ title: Get-DlpDetectionsReport
## SYNOPSIS
This cmdlet is available only in the cloud-based service.
-**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet.
+**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet.
Use the Get-DlpDetectionsReport cmdlet to list a summary of data loss prevention (DLP) rule matches for Exchange Online, SharePoint and OneDrive in your cloud-based organization for the last 30 days.
@@ -67,9 +66,6 @@ This example lists the DLP activities for November, 2018.
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Security & Compliance
-
The Action parameter filters the report by the action taken by DLP policies. Valid values are:
- BlockAccess
@@ -82,6 +78,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -91,15 +88,13 @@ Accept wildcard characters: False
```
### -AggregateBy
-
-> Applicable: Exchange Online, Security & Compliance
-
The AggregateBy parameter specifies the reporting period. Valid values are Hour, Day, or Summary. The default value is Day.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -109,9 +104,6 @@ Accept wildcard characters: False
```
### -DlpCompliancePolicy
-
-> Applicable: Exchange Online, Security & Compliance
-
The DlpCompliancePolicy parameter filters the report by the name of the DLP compliance policy. You can specify multiple policies separated by commas.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -120,6 +112,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -129,9 +122,6 @@ Accept wildcard characters: False
```
### -DlpComplianceRule
-
-> Applicable: Exchange Online, Security & Compliance
-
The DlpComplianceRule parameter filters the report by the name of the DLP compliance rule. You can specify multiple rules separated by commas.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -140,6 +130,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -149,9 +140,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -160,6 +148,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -169,9 +158,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Security & Compliance
-
The EventType parameter filters the report by the event type. Valid values are:
- DataRetentions
@@ -197,6 +183,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -206,9 +193,6 @@ Accept wildcard characters: False
```
### -Expression
-
-> Applicable: Security & Compliance
-
This parameter is available only in Security & Compliance PowerShell
This parameter is reserved for internal Microsoft use.
@@ -217,6 +201,7 @@ This parameter is reserved for internal Microsoft use.
Type: Expression
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -226,15 +211,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -244,15 +227,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -262,9 +243,6 @@ Accept wildcard characters: False
```
### -Source
-
-> Applicable: Exchange Online, Security & Compliance
-
The Source parameter filters the report by workload. Valid values are:
- EXCH: Exchange Online
@@ -277,6 +255,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -286,9 +265,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -297,6 +273,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -306,9 +283,6 @@ Accept wildcard characters: False
```
### -SummarizeBy
-
-> Applicable: Exchange Online, Security & Compliance
-
The SummarizeBy parameter returns totals based on the values you specify. If your report filters data using any of the values accepted by this parameter, you can use the SummarizeBy parameter to summarize the results based on those values. To decrease the number of rows returned in the report, consider using the SummarizeBy parameter. Summarizing reduces the amount of data that's retrieved for the report and delivers the report faster. For example, instead of seeing each instance of a specific value of EventType on an individual row in the report, you can use the SummarizeBy parameter to see the total number of instances of that value of EventType on one row in the report.
For this cmdlet, valid values are:
@@ -323,6 +297,7 @@ You can specify multiple values separated by commas. The values that you specify
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpEdmSchema.md b/exchange/exchange-ps/exchange/Get-DlpEdmSchema.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpEdmSchema.md
rename to exchange/exchange-ps/exchange/Get-DlpEdmSchema.md
index 874113548b..d9052762b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpEdmSchema.md
+++ b/exchange/exchange-ps/exchange/Get-DlpEdmSchema.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpedmschema
applicable: Security & Compliance
+title: Get-DlpEdmSchema
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpedmschema
-schema: 2.0.0
-title: Get-DlpEdmSchema
+ms.reviewer:
---
# Get-DlpEdmSchema
@@ -48,9 +47,6 @@ This example returns detailed information for the DLP EDM schema named Schema fo
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the DLP EDM schema that you want to view. You can use any value that uniquely identifies the schema. For example:
- Name
@@ -60,6 +56,7 @@ The Identity parameter specifies the DLP EDM schema that you want to view. You c
Type: EdmStorageIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md b/exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md
rename to exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md
index b5aa6eac36..59707c5464 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md
+++ b/exchange/exchange-ps/exchange/Get-DlpIncidentDetailReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpincidentdetailsreport
applicable: Exchange Online, Security & Compliance
+title: Get-DlpIncidentDetailReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpincidentdetailsreport
-schema: 2.0.0
-title: Get-DlpIncidentDetailReport
+ms.reviewer:
---
# Get-DlpIncidentDetailReport
@@ -15,7 +14,7 @@ title: Get-DlpIncidentDetailReport
## SYNOPSIS
This cmdlet is available only in the cloud-based service.
-**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata) instead.
+**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata) instead.
Use the Get-DlpIncidentDetailReport cmdlet to view the details of incidents that happened in the last 30 days.
@@ -80,9 +79,6 @@ This example lists the details of the all incidents that occurred between the da
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Security & Compliance
-
The Action parameter filters the report by the action taken by DLP policies. Valid values are:
- BlockAccess
@@ -95,6 +91,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -104,9 +101,6 @@ Accept wildcard characters: False
```
### -Actor
-
-> Applicable: Exchange Online, Security & Compliance
-
The Actor parameter filters the report by the user who last modified the item. You can enter multiple users separated by commas.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -115,6 +109,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -124,9 +119,6 @@ Accept wildcard characters: False
```
### -DlpCompliancePolicy
-
-> Applicable: Exchange Online, Security & Compliance
-
The DlpCompliancePolicy parameter filters the report by the name of the DLP compliance policy. You can specify multiple policies separated by commas.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -135,6 +127,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -144,9 +137,6 @@ Accept wildcard characters: False
```
### -DlpComplianceRule
-
-> Applicable: Exchange Online, Security & Compliance
-
The DlpComplianceRule parameter filters the report by the name of the DLP compliance rule. You can specify multiple rules separated by commas.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -155,6 +145,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -164,9 +155,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -175,6 +163,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -184,9 +173,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Security & Compliance
-
The EventType parameter filters the report by the event type. Valid values are:
- DLPByIncidentIdActionHits
@@ -204,6 +190,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -213,15 +200,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -231,15 +216,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -249,9 +232,6 @@ Accept wildcard characters: False
```
### -Source
-
-> Applicable: Exchange Online, Security & Compliance
-
The Source parameter filters the report by workload. Valid values are:
- EXCH: Exchange Online
@@ -265,6 +245,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -274,9 +255,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -285,6 +263,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpKeywordDictionary.md
rename to exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md
index 3158241804..cf21bb85d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpKeywordDictionary.md
+++ b/exchange/exchange-ps/exchange/Get-DlpKeywordDictionary.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpkeyworddictionary
applicable: Exchange Online, Security & Compliance
+title: Get-DlpKeywordDictionary
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpkeyworddictionary
-schema: 2.0.0
-title: Get-DlpKeywordDictionary
+ms.reviewer:
---
# Get-DlpKeywordDictionary
@@ -48,15 +47,13 @@ This example returns detailed information about the DLP keyword dictionary named
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Security & Compliance
-
The Name parameter specifies the name of the DLP keyword dictionary that you want to view. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md b/exchange/exchange-ps/exchange/Get-DlpPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
rename to exchange/exchange-ps/exchange/Get-DlpPolicy.md
index d8452dfc15..ef75ad1628 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-DlpPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlppolicy
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-DlpPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlppolicy
-schema: 2.0.0
-title: Get-DlpPolicy
+ms.reviewer:
---
# Get-DlpPolicy
@@ -51,9 +50,6 @@ This example returns detailed information about the DLP policy named Employee Nu
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the DLP policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the DLP policy that you want to view. You can u
Type: DlpPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md b/exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
rename to exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md
index c43bb97aac..bafb90d765 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/exchange/Get-DlpPolicyTemplate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlppolicytemplate
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-DlpPolicyTemplate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlppolicytemplate
-schema: 2.0.0
-title: Get-DlpPolicyTemplate
+ms.reviewer:
---
# Get-DlpPolicyTemplate
@@ -51,15 +50,13 @@ This example returns detailed information about the DLP policy template named GL
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the DLP policy template you want to view. You can use any value that uniquely identifies the DLP policy template. For example, you can specify the name, GUID or distinguished name (DN) of the DLP policy template.
```yaml
Type: DlpPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -80,6 +74,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationType.md
rename to exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md
index 601dfddd45..99d0a14db7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationType.md
+++ b/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationType.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpsensitiveinformationtype
applicable: Exchange Online, Security & Compliance
+title: Get-DlpSensitiveInformationType
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype
-schema: 2.0.0
-title: Get-DlpSensitiveInformationType
+ms.reviewer:
---
# Get-DlpSensitiveInformationType
@@ -54,9 +53,6 @@ This example lists all the properties of the sensitive information type named "C
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the sensitive information type that you want to view. Valid values are:
- Name
@@ -66,6 +62,7 @@ The Identity parameter specifies the sensitive information type that you want to
Type: SensitiveInformationTypeIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -Capability
-
-> Applicable: Security & Compliance
-
{{ Fill Capability Description }}
```yaml
Type: ClassificationCapabilityType
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -93,15 +88,13 @@ Accept wildcard characters: False
```
### -IncludeDetails
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeDetails Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -111,15 +104,13 @@ Accept wildcard characters: False
```
### -IncludeElements
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeElements Description }}
```yaml
Type: ClassificationPrimitiveElementType
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -129,15 +120,13 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationTypeRulePackage.md
rename to exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md
index 4cce370d02..322925e01f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpSensitiveInformationTypeRulePackage.md
+++ b/exchange/exchange-ps/exchange/Get-DlpSensitiveInformationTypeRulePackage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpsensitiveinformationtyperulepackage
applicable: Exchange Online, Security & Compliance
+title: Get-DlpSensitiveInformationTypeRulePackage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpsensitiveinformationtyperulepackage
-schema: 2.0.0
-title: Get-DlpSensitiveInformationTypeRulePackage
+ms.reviewer:
---
# Get-DlpSensitiveInformationTypeRulePackage
@@ -51,9 +50,6 @@ This example returns detailed information for the sensitive information type rul
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the sensitive information type rule package that you want to view. You can use any value that uniquely identifies the rule package. For example:
- RuleCollectionName
@@ -64,6 +60,7 @@ The Identity parameter specifies the sensitive information type rule package tha
Type: SensitiveInformationTypeRuleCollectionIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -Capability
-
-> Applicable: Exchange Online, Security & Compliance
-
{{ Fill Capability Description }}
```yaml
Type: ClassificationCapabilityType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpSiDetectionsReport.md b/exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DlpSiDetectionsReport.md
rename to exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md
index f66ffd8c70..b89d2416f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpSiDetectionsReport.md
+++ b/exchange/exchange-ps/exchange/Get-DlpSiDetectionsReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dlpsidetectionsreport
applicable: Exchange Online, Security & Compliance
+title: Get-DlpSiDetectionsReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpsidetectionsreport
-schema: 2.0.0
-title: Get-DlpSiDetectionsReport
+ms.reviewer:
---
# Get-DlpSiDetectionsReport
@@ -15,7 +14,7 @@ title: Get-DlpSiDetectionsReport
## SYNOPSIS
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
-**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet.
+**Note**: This cmdlet will be retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchange/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet.
Use the Get-DlpSiDetectionsReport cmdlet to view information about data loss prevention (DLP) sensitive information type detections in the Microsoft Purview compliance portal for the last 90 days.
@@ -60,9 +59,6 @@ This example returns detections for the sensitive information type 0e9b3178-9678
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -71,6 +67,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -80,9 +77,6 @@ Accept wildcard characters: False
```
### -SensitiveType
-
-> Applicable: Exchange Online, Security & Compliance
-
The SensitiveType parameter filters the results by the specified sensitive information type. A valid value is the GUID of the sensitive information type (for example, 0e9b3178-9678-47dd-a509-37222ca96b42). To find the GUID value of a sensitive information type, run this command: Get-DlpSensitiveInformationType.
You can enter multiple values separated by commas: `"Value1","Value2",..."ValueN"`.
@@ -91,6 +85,7 @@ You can enter multiple values separated by commas: `"Value1","Value2",..."ValueN
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md b/exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md
rename to exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md
index 36ca1bd7a8..05ddacb11c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md
+++ b/exchange/exchange-ps/exchange/Get-DnssecStatusForVerifiedDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dnssecstatusforverifieddomain
applicable: Exchange Online
+title: Get-DnssecStatusForVerifiedDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dnssecstatusforverifieddomain
-schema: 2.0.0
-title: Get-DnssecStatusForVerifiedDomain
+ms.reviewer:
---
# Get-DnssecStatusForVerifiedDomain
@@ -98,15 +97,13 @@ This example contains the output from Example 1 and readable values for the DnsV
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Online
-
The DomainName parameter specifies the accepted domain in the Exchange Online organization where you want to view information about DNSSEC (for example, contoso.com).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
@@ -116,15 +113,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -134,15 +129,13 @@ Accept wildcard characters: False
```
### -SkipDnsValidation
-
-> Applicable: Exchange Online
-
The SkipDnsValidation switch specifies whether to skip the check for the DNSSEC-secured MX record in the domain. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -152,15 +145,13 @@ Accept wildcard characters: False
```
### -SkipMtaStsValidation
-
-> Applicable: Exchange Online
-
The SkipMtaStsValidation switch specifies whether to skip the check for the DNSSEC-secured mail host in the MTA-STS Policy. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -170,15 +161,13 @@ Accept wildcard characters: False
```
### -SkipMxValidation
-
-> Applicable: Exchange Online
-
The SkipMxValidation switch specifies whether to skip the check for the priority value 10 in the DNSSEC-secured MX record. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -188,15 +177,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md b/exchange/exchange-ps/exchange/Get-DomainController.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
rename to exchange/exchange-ps/exchange/Get-DomainController.md
index 7a52528003..b36194819e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
+++ b/exchange/exchange-ps/exchange/Get-DomainController.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-domaincontroller
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-DomainController
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-domaincontroller
-schema: 2.0.0
-title: Get-DomainController
+ms.reviewer:
---
# Get-DomainController
@@ -60,15 +59,13 @@ For more information about pipelining and the Format-Table cmdlet, see [About Pi
## PARAMETERS
### -GlobalCatalog
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The GlobalCatalog switch specifies whether the command should return a list of global catalog servers. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: GlobalCatalog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
This parameter requires the creation and passing of a credential object. This credential object is created by using the Get-Credential cmdlet. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -91,6 +85,7 @@ If you use the Forest parameter, the credentials are used to access the forest.
Type: NetworkCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -100,15 +95,13 @@ Accept wildcard characters: False
```
### -DomainName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainName parameter specifies the fully qualified domain name (FQDN) of the domain for which you want to return a list of domain controllers.
```yaml
Type: Fqdn
Parameter Sets: DomainController
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -118,15 +111,13 @@ Accept wildcard characters: False
```
### -Forest
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Forest parameter specifies the FQDN of the root domain of the forest for which you want to return a list of domain controllers.
```yaml
Type: Fqdn
Parameter Sets: GlobalCatalog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
rename to exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md
index 87c60a02f3..4dfc211e99 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dynamicdistributiongroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-DynamicDistributionGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dynamicdistributiongroup
-schema: 2.0.0
-title: Get-DynamicDistributionGroup
+ms.reviewer:
---
# Get-DynamicDistributionGroup
@@ -127,9 +126,6 @@ This example returns the members for the dynamic distribution group named Full T
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the dynamic distribution group that you want to view. You can use any value that uniquely identifies the dynamic distribution group. For example:
- Name
@@ -143,6 +139,7 @@ The Identity parameter specifies the dynamic distribution group that you want to
Type: DynamicGroupIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -152,9 +149,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -167,6 +161,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -176,9 +171,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -187,6 +179,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -196,9 +189,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -207,6 +197,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -216,9 +207,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -234,6 +222,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -243,9 +232,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -259,6 +245,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -268,9 +255,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of AcceptMessagesOnlyFromDLMembers recipients in the AcceptMessagesOnlyFromDLMembersWithDisplayNames property. You don't need to specify a value with this switch.
@@ -281,6 +265,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -290,9 +275,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of AcceptMessagesOnlyFromSendersOrMembers recipients in the AcceptMessagesOnlyFromSendersOrMembersWithDisplayNames property. You don't need to specify a value with this switch.
@@ -303,6 +285,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -312,9 +295,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeAcceptMessagesOnlyFromWithDisplayNames switch specifies whether to return the SMTP addresses and display names of AcceptMessagesOnlyFrom recipients in the AcceptMessagesOnlyFromWithDisplayNames property. You don't need to specify a value with this switch.
@@ -325,6 +305,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -334,9 +315,6 @@ Accept wildcard characters: False
```
### -IncludeBypassModerationFromSendersOrMembersWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeBypassModerationFromSendersOrMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of BypassModerationFromSendersOrMembers recipients in the BypassModerationFromSendersOrMembersWithDisplayNames property. You don't need to specify a value with this switch.
@@ -347,6 +325,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -356,9 +335,6 @@ Accept wildcard characters: False
```
### -IncludeGrantSendOnBehalfToWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeGrantSendOnBehalfToWithDisplayNames switch specifies whether to return the SMTP addresses and display names of GrantSendOnBehalfTo recipients in the GrantSendOnBehalfToWithDisplayNames property. You don't need to specify a value with this switch.
@@ -369,6 +345,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -378,9 +355,6 @@ Accept wildcard characters: False
```
### -IncludeManagedByWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeManagedByWithDisplayNames switch specifies whether to return the SMTP addresses and display names of group owners in the ManagedByWithDisplayNames property. You don't need to specify a value with this switch.
@@ -391,6 +365,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -400,9 +375,6 @@ Accept wildcard characters: False
```
### -IncludeModeratedByWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeModeratedByWithDisplayNames switch specifies whether to return the SMTP addresses and display names of ModeratedBy recipients in the ModeratedByWithDisplayNames property. You don't need to specify a value with this switch.
@@ -413,6 +385,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -422,9 +395,6 @@ Accept wildcard characters: False
```
### -IncludeSystemObjects
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -433,6 +403,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -442,9 +413,6 @@ Accept wildcard characters: False
```
### -ManagedBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ManagedBy parameter filters the results by the owner of the group. You can use any value that uniquely identifies the owner. For example:
- Name
@@ -458,6 +426,7 @@ The ManagedBy parameter filters the results by the owner of the group. You can u
Type: GeneralRecipientIdParameter
Parameter Sets: ManagedBySet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -467,9 +436,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -481,6 +447,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -490,9 +457,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -505,6 +469,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -514,15 +479,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -532,9 +495,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -549,6 +509,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroupMember.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md
rename to exchange/exchange-ps/exchange/Get-DynamicDistributionGroupMember.md
index 0f7bc5f3fe..d93483e17c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md
+++ b/exchange/exchange-ps/exchange/Get-DynamicDistributionGroupMember.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-dynamicdistributiongroupmember
applicable: Exchange Online, Exchange Online Protection
+title: Get-DynamicDistributionGroupMember
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-dynamicdistributiongroupmember
-schema: 2.0.0
-title: Get-DynamicDistributionGroupMember
+ms.reviewer:
---
# Get-DynamicDistributionGroupMember
@@ -46,9 +45,6 @@ This example returns the existing members for the dynamic distribution group nam
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the dynamic distribution group. You can use any value that uniquely identifies the group. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the dynamic distribution group. You can use any
Type: DynamicDistributionGroupMemberIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -82,6 +76,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -91,9 +86,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedObjects
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeSoftDeletedGroups switch specifies whether to include soft-deleted group members in the results. You don't need to specify a value with this switch.
Soft-deleted group members are deleted Microsoft 365 Groups or mailboxes that are still recoverable.
@@ -102,6 +94,7 @@ Soft-deleted group members are deleted Microsoft 365 Groups or mailboxes that ar
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -111,15 +104,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md
index ca0f1e8085..b10e5bcf46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/Get-EOPProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-eopprotectionpolicyrule
applicable: Exchange Online, Exchange Online Protection
+title: Get-EOPProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-eopprotectionpolicyrule
-schema: 2.0.0
-title: Get-EOPProtectionPolicyRule
+ms.reviewer:
---
# Get-EOPProtectionPolicyRule
@@ -51,9 +50,6 @@ This example returns detailed information about the rule named Strict Preset Sec
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -66,6 +62,7 @@ By default, the available rules (if they exist) are named Standard Preset Securi
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 0
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The State parameter filters the results by the state of the rule. Valid values are:
- Enabled
@@ -88,6 +82,7 @@ Type: RuleState
Parameter Sets: (All)
Aliases:
Accepted values: Enabled, Disabled
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOCasMailbox.md b/exchange/exchange-ps/exchange/Get-EXOCasMailbox.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXOCasMailbox.md
rename to exchange/exchange-ps/exchange/Get-EXOCasMailbox.md
index 173797cbcd..72e7aca6f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOCasMailbox.md
+++ b/exchange/exchange-ps/exchange/Get-EXOCasMailbox.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exocasmailbox
applicable: Exchange Online
+title: Get-EXOCasMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exocasmailbox
-schema: 2.0.0
-title: Get-EXOCasMailbox
+ms.reviewer:
---
# Get-EXOCasMailbox
@@ -83,9 +83,6 @@ This example returns the values of the following client access settings for the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox you want to view. For the best performance, we recommend using the following values:
- User ID or user principal name (UPN)
@@ -107,6 +104,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmt
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -116,9 +114,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Online
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -133,6 +128,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, Prima
Type: String
Parameter Sets: Anr
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -142,15 +138,13 @@ Accept wildcard characters: False
```
### -ActiveSyncDebugLogging
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -160,9 +154,6 @@ Accept wildcard characters: False
```
### -ExternalDirectoryObjectId
-
-> Applicable: Exchange Online
-
The ExternalDirectoryObjectId parameter identifies the mailbox that you want to view by the ObjectId in Microsoft Entra ID.
You can't use this parameter with the Anr, Identity, PrimarySmtpAddress, or UserPrincipalName parameters.
@@ -171,6 +162,7 @@ You can't use this parameter with the Anr, Identity, PrimarySmtpAddress, or User
Type: Guid
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -180,9 +172,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -198,6 +187,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -207,15 +197,13 @@ Accept wildcard characters: False
```
### -GetImapProtocolLog
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -225,15 +213,13 @@ Accept wildcard characters: False
```
### -GetPopProtocolLog
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -243,15 +229,13 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -261,9 +245,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Online
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's visible using the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -275,6 +256,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -284,9 +266,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the mailbox that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity, or UserPrincipalName parameters.
@@ -295,6 +274,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity,
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -304,9 +284,6 @@ Accept wildcard characters: False
```
### -Properties
-
-> Applicable: Exchange Online
-
The Properties parameter specifies the properties that are returned in the output of this cmdlet. You can specify multiple values separated by commas.
For more information about the available properties, see [Get-EXOCasMailbox property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exocasmailbox-property-sets).
@@ -315,6 +292,7 @@ For more information about the available properties, see [Get-EXOCasMailbox prop
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -324,9 +302,6 @@ Accept wildcard characters: False
```
### -PropertySets
-
-> Applicable: Exchange Online
-
The PropertySets parameter specifies a logical grouping of properties that are returned in the output of this cmdlet. Valid values are:
- Minimum (this is the default value)
@@ -346,6 +321,7 @@ For more information about the properties that are included in each property set
Type: PropertySet[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -355,9 +331,6 @@ Accept wildcard characters: False
```
### -ProtocolSettings
-
-> Applicable: Exchange Online
-
The ProtocolSettings switch returns the server names, TCP ports and encryption methods for the following settings:
- ExternalImapSettings
@@ -375,6 +348,7 @@ To see these values, you need to use a formatting cmdlet. For example, `Get-CasM
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -384,15 +358,13 @@ Accept wildcard characters: False
```
### -ReadIsOptimizedForAccessibility
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -402,15 +374,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -420,15 +390,13 @@ Accept wildcard characters: False
```
### -SendLogsTo
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -438,9 +406,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity or PrimarySmtpAddress parameters.
@@ -449,6 +414,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity o
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailbox.md b/exchange/exchange-ps/exchange/Get-EXOMailbox.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXOMailbox.md
rename to exchange/exchange-ps/exchange/Get-EXOMailbox.md
index 73afabf04d..29b21ed26e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailbox.md
+++ b/exchange/exchange-ps/exchange/Get-EXOMailbox.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailbox
applicable: Exchange Online
+title: Get-EXOMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exomailbox
-schema: 2.0.0
-title: Get-EXOMailbox
+ms.reviewer:
---
# Get-EXOMailbox
@@ -105,9 +105,6 @@ This example returns the specified properties for the mailbox John@contoso.com.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox you want to view. For the best performance, we recommend using the following values:
- User ID or user principal name (UPN)
@@ -129,6 +126,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmt
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -138,9 +136,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Online
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -155,6 +150,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, Prima
Type: String
Parameter Sets: Anr
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -164,15 +160,13 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Online
-
The Archive switch filters the results by mailboxes that have an archive enabled (only mailboxes that have an archive mailbox are returned). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -182,15 +176,13 @@ Accept wildcard characters: False
```
### -Async
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -200,9 +192,6 @@ Accept wildcard characters: False
```
### -ExternalDirectoryObjectId
-
-> Applicable: Exchange Online
-
The ExternalDirectoryObjectId parameter identifies the mailbox that you want to view by the ObjectId in Microsoft Entra ID.
You can't use this parameter with the Anr, Identity, PrimarySmtpAddress, or UserPrincipalName parameters.
@@ -211,6 +200,7 @@ You can't use this parameter with the Anr, Identity, PrimarySmtpAddress, or User
Type: Guid
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -220,9 +210,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -238,6 +225,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -247,15 +235,13 @@ Accept wildcard characters: False
```
### -GroupMailbox
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -265,9 +251,6 @@ Accept wildcard characters: False
```
### -InactiveMailboxOnly
-
-> Applicable: Exchange Online
-
The InactiveMailboxOnly switch specifies whether to return only inactive mailboxes in the results. You don't need to specify a value with this switch.
An inactive mailbox is a mailbox that's placed on Litigation Hold or In-Place Hold before it's soft-deleted. The contents of an inactive mailbox are preserved until the hold is removed.
@@ -278,6 +261,7 @@ To return both active mailboxes and inactive mailboxes in the results, don't use
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -287,9 +271,6 @@ Accept wildcard characters: False
```
### -IncludeInactiveMailbox
-
-> Applicable: Exchange Online
-
The IncludeInactiveMailbox switch specifies whether to include inactive mailboxes in the results. You don't need to specify a value with this switch.
An inactive mailbox is a mailbox that's placed on Litigation Hold or In-Place Hold before it's soft-deleted. The contents of an inactive mailbox are preserved until the hold is removed.
@@ -300,6 +281,7 @@ To return only inactive mailboxes in the results, don't use this switch. Instead
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -309,9 +291,6 @@ Accept wildcard characters: False
```
### -MailboxPlan
-
-> Applicable: Exchange Online
-
The MailboxPlan parameter filters the results by mailbox plan. When you use this parameter, only mailboxes that are assigned the specified mailbox plan are returned in the results. You can use any value that uniquely identifies the mailbox plan. For example:
- Name
@@ -326,6 +305,7 @@ A mailbox plan specifies the permissions and features available to a mailbox use
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -335,15 +315,13 @@ Accept wildcard characters: False
```
### -Migration
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -353,9 +331,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Online
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's visible using the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -367,6 +342,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -376,9 +352,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the mailbox that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity, or UserPrincipalName parameters.
@@ -387,6 +360,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity,
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -396,9 +370,6 @@ Accept wildcard characters: False
```
### -Properties
-
-> Applicable: Exchange Online
-
The Properties parameter specifies the properties that are returned in the output of this cmdlet. You can specify multiple values separated by commas.
For more information about the available properties, see [Get-EXOMailbox property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exomailbox-property-sets).
@@ -407,6 +378,7 @@ For more information about the available properties, see [Get-EXOMailbox propert
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -416,9 +388,6 @@ Accept wildcard characters: False
```
### -PropertySets
-
-> Applicable: Exchange Online
-
The PropertySets parameter specifies a logical grouping of properties that are returned in the output of this cmdlet. Valid values are:
- All
@@ -448,6 +417,7 @@ For more information about the properties that are included in each property set
Type: PropertySet[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -457,15 +427,13 @@ Accept wildcard characters: False
```
### -PublicFolder
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -475,9 +443,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Online
-
The RecipientTypeDetails parameter filters the results by the specified mailbox subtype. Valid values are:
- DiscoveryMailbox
@@ -497,6 +462,7 @@ You can specify multiple values separated by commas.
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -506,15 +472,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -524,9 +488,6 @@ Accept wildcard characters: False
```
### -SoftDeletedMailbox
-
-> Applicable: Exchange Online
-
The SoftDeletedMailbox switch is required to return soft-deleted mailboxes in the results. You don't need to specify a value with this switch.
Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
@@ -535,6 +496,7 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -544,9 +506,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity or PrimarySmtpAddress parameters.
@@ -555,6 +514,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity o
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md b/exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md
rename to exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md
index 5cbf8ec31b..d15ff5ab3c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md
+++ b/exchange/exchange-ps/exchange/Get-EXOMailboxFolderPermission.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderpermission
applicable: Exchange Online
+title: Get-EXOMailboxFolderPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exomailboxfolderpermission
-schema: 2.0.0
-title: Get-EXOMailboxFolderPermission
+ms.reviewer:
---
# Get-EXOMailboxFolderPermission
@@ -53,9 +53,6 @@ This example returns the permissions for the same folder in John's mailbox, but
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox folder that you want to view. This parameter uses the syntax: `:\`. For the best performance, we recommend using the user ID or user principal name (UPN) to identify the mailbox.
Otherwise, you can use any value that uniquely identifies the mailbox. For example:
@@ -73,6 +70,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -82,9 +80,6 @@ Accept wildcard characters: False
```
### -ExternalDirectoryObjectId
-
-> Applicable: Exchange Online
-
The ExternalDirectoryObjectId parameter identifies the mailbox that you want to view by the ObjectId in Microsoft Entra ID.
You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrincipalName parameters.
@@ -93,6 +88,7 @@ You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrinc
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -102,15 +98,13 @@ Accept wildcard characters: False
```
### -GroupMailbox
-
-> Applicable: Exchange Online
-
The GroupMailbox switch is required to return Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -120,9 +114,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the mailbox that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or UserPrincipalName parameters.
@@ -131,6 +122,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Us
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -140,9 +132,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Online
-
The User parameter filters the results by the specified mailbox, mail user, or mail-enabled security group (security principal) that's granted permission to the mailbox folder. You can use any value that uniquely identifies the user or group. For example:
- Name
@@ -158,6 +147,7 @@ The User parameter filters the results by the specified mailbox, mail user, or m
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -167,9 +157,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or PrimarySmtpAddress parameters.
@@ -178,6 +165,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Pr
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -197,10 +185,10 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
## RELATED LINKS
-[Get-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxfolderpermission)
+[Get-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderpermission)
-[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxfolderpermission)
+[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission)
-[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/remove-mailboxfolderpermission)
+[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission)
-[Add-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/add-mailboxfolderpermission)
+[Add-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/add-mailboxfolderpermission)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderStatistics.md b/exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderStatistics.md
rename to exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md
index 62cc044bb4..b6d21cf8d8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-EXOMailboxFolderStatistics.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderstatistics
applicable: Exchange Online
+title: Get-EXOMailboxFolderStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exomailboxfolderstatistics
-schema: 2.0.0
-title: Get-EXOMailboxFolderStatistics
+ms.reviewer:
---
# Get-EXOMailboxFolderStatistics
@@ -67,9 +67,6 @@ This example uses the FolderScope parameter to view Inbox folder statistics for
## PARAMETERS
### -Archive
-
-> Applicable: Exchange Online
-
The Archive switch specifies whether to return the usage statistics of the archive mailbox that's associated with the mailbox or mail user. You don't need to specify a value with this switch.
If you use this switch on a mailbox that doesn't have archiving enabled, an error is returned.
@@ -78,6 +75,7 @@ If you use this switch on a mailbox that doesn't have archiving enabled, an erro
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -87,15 +85,13 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -105,9 +101,6 @@ Accept wildcard characters: False
```
### -ExternalDirectoryObjectId
-
-> Applicable: Exchange Online
-
The ExternalDirectoryObjectId parameter identifies the mailbox that you want to view by the ObjectId in Microsoft Entra ID.
You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrincipalName parameters.
@@ -116,6 +109,7 @@ You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrinc
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -125,9 +119,6 @@ Accept wildcard characters: False
```
### -Folderscope
-
-> Applicable: Exchange Online
-
The FolderScope parameter specifies the scope of the search by folder type. Valid values include:
- All
@@ -157,6 +148,7 @@ The FolderScope parameter specifies the scope of the search by folder type. Vali
Type: ElcFolderType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -166,9 +158,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the identity of the mailbox or mail user. For the best performance, we recommend using the user ID or user principal name (UPN) to identify the mailbox.
Otherwise, you can use any value that uniquely identifies the mailbox or mail user. For example:
@@ -185,6 +174,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -194,15 +184,13 @@ Accept wildcard characters: False
```
### -IncludeAnalysis
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -212,15 +200,13 @@ Accept wildcard characters: False
```
### -IncludeOldestAndNewestItems
-
-> Applicable: Exchange Online
-
The IncludeOldestAndNewestItems switch specifies whether to return the dates of the oldest and newest items in each folder. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -230,9 +216,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedRecipients
-
-> Applicable: Exchange Online
-
The IncludeSoftDeletedRecipients switch specifies whether to include soft-deleted mailboxes in the results. You don't need to specify a value with this switch.
Soft-deleted mailboxes are mailboxes that have been deleted, but are still recoverable.
@@ -241,6 +224,7 @@ Soft-deleted mailboxes are mailboxes that have been deleted, but are still recov
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -250,9 +234,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the mailbox that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or UserPrincipalName parameters.
@@ -261,6 +242,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Us
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -270,9 +252,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or PrimarySmtpAddress parameters.
@@ -281,6 +260,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Pr
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md b/exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md
rename to exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md
index d52f055125..d008aa8f24 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md
+++ b/exchange/exchange-ps/exchange/Get-EXOMailboxPermission.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailboxpermission
applicable: Exchange Online
+title: Get-EXOMailboxPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exomailboxpermission
-schema: 2.0.0
-title: Get-EXOMailboxPermission
+ms.reviewer:
---
# Get-EXOMailboxPermission
@@ -72,9 +72,6 @@ This example return the permission the user has on mailboxes
## PARAMETERS
### -ExternalDirectoryObjectId
-
-> Applicable: Exchange Online
-
The ExternalDirectoryObjectId parameter identifies the mailbox that you want to view by the ObjectId in Microsoft Entra ID.
You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrincipalName parameters.
@@ -83,6 +80,7 @@ You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrinc
Type: Guid
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -92,9 +90,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox you want to view. For the best performance, we recommend using the user ID or user principal name (UPN) to identify the mailbox.
Otherwise, you can use any value that uniquely identifies the mailbox. For example:
@@ -111,6 +106,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -120,15 +116,13 @@ Accept wildcard characters: False
```
### -Owner
-
-> Applicable: Exchange Online
-
The Owner switch returns the owner information for the mailbox that's specified by the Identity parameter. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -138,9 +132,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the mailbox that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or UserPrincipalName parameters.
@@ -149,6 +140,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Us
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -158,15 +150,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -176,9 +166,6 @@ Accept wildcard characters: False
```
### -SoftDeletedMailbox
-
-> Applicable: Exchange Online
-
The SoftDeletedMailbox switch is required to return soft-deleted mailboxes in the results. You don't need to specify a value with this switch.
Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
@@ -187,6 +174,7 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -196,9 +184,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Online
-
The User parameter returns information about the user who has permissions to the mailbox specified by the Identity parameter.
The user that you specify for this parameter must be a user or security group (a security principal that can have permissions assigned). You can use any value that uniquely identifies the user. For example:
@@ -214,6 +199,7 @@ The user that you specify for this parameter must be a user or security group (a
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -223,9 +209,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or PrimarySmtpAddress parameters.
@@ -234,6 +217,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Pr
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxStatistics.md b/exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxStatistics.md
rename to exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md
index 4840704c43..cbe03cc816 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-EXOMailboxStatistics.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exomailboxstatistics
applicable: Exchange Online
+title: Get-EXOMailboxStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exomailboxstatistics
-schema: 2.0.0
-title: Get-EXOMailboxStatistics
+ms.reviewer:
---
# Get-EXOMailboxStatistics
@@ -61,15 +61,13 @@ This example retrieves the minimum set of properties and the specified propertie
## PARAMETERS
### -Archive
-
-> Applicable: Exchange Online
-
The Archive switch specifies whether to return mailbox statistics for the archive mailbox associated with the specified mailbox. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -79,15 +77,13 @@ Accept wildcard characters: False
```
### -DatabaseGuid
-
-> Applicable: Exchange Online
-
The DatabaseGuid parameter filters the results by the GUID of mailbox database that hosts the Mailbox. You can find this property value by using the Get-EXOMailbox cmdlet with the Properties parameter value DatabaseGuid.
```yaml
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -97,15 +93,13 @@ Accept wildcard characters: False
```
### -ExchangeGuid
-
-> Applicable: Exchange Online
-
The ExchangeGuid parameter filters the results by the GUID of mailbox (aso known as the Mailbox GUID). You can find this property value by using the Get-EXOMailbox cmdlet with Properties filter set to ExchangeGuid.
```yaml
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -115,9 +109,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox you want to view. For the best performance, we recommend using the user ID or user principal name (UPN) to identify the mailbox.
Otherwise, you can use any value that uniquely identifies the mailbox. For example:
@@ -136,6 +127,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -145,15 +137,13 @@ Accept wildcard characters: False
```
### -IncludeMoveHistory
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -163,15 +153,13 @@ Accept wildcard characters: False
```
### -IncludeMoveReport
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -181,9 +169,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedRecipients
-
-> Applicable: Exchange Online
-
The IncludeSoftDeletedRecipients switch specifies whether to include soft deleted recipients in the results. You don't need to specify a value with this switch.
Soft-deleted recipients are deleted recipients that are still recoverable.
@@ -192,6 +177,7 @@ Soft-deleted recipients are deleted recipients that are still recoverable.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -201,9 +187,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the mailbox that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or UserPrincipalName parameters.
@@ -212,6 +195,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Us
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -221,9 +205,6 @@ Accept wildcard characters: False
```
### -Properties
-
-> Applicable: Exchange Online
-
The Properties parameter specifies the properties that are returned in the output of this cmdlet. You can specify multiple values separated by commas.
For more information about the available properties, see [Get-EXOMailboxStatistics property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exomailboxstatistics-property-sets).
@@ -232,6 +213,7 @@ For more information about the available properties, see [Get-EXOMailboxStatisti
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -241,9 +223,6 @@ Accept wildcard characters: False
```
### -PropertySets
-
-> Applicable: Exchange Online
-
The PropertySets parameter specifies a logical grouping of properties that are returned in the output of this cmdlet. Valid values are:
- Minimum (this is the default value)
@@ -257,6 +236,7 @@ For more information about the properties that are included in each property set
Type: PropertySet[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -266,9 +246,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or PrimarySmtpAddress parameters.
@@ -277,6 +254,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Pr
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMobileDeviceStatistics.md b/exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXOMobileDeviceStatistics.md
rename to exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md
index ac4e8c62b0..91b5ebab64 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMobileDeviceStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-EXOMobileDeviceStatistics.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exomobiledevicestatistics
applicable: Exchange Online
+title: Get-EXOMobileDeviceStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exomobiledevicestatistics
-schema: 2.0.0
-title: Get-EXOMobileDeviceStatistics
+ms.reviewer:
---
# Get-EXOMobileDeviceStatistics
@@ -72,9 +72,6 @@ This example returns the statistics for active sync devices linked to user with
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mobile device that you want to view. You can use any value that uniquely identifies the mobile device. For example:
- GUID
@@ -86,6 +83,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Mailbox, Primar
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -95,9 +93,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Online
-
The Mailbox parameter filters the results by the user mailbox that's associated with the mobile device. You can use any value that uniquely identifies the mailbox. For example:
- GUID
@@ -109,6 +104,7 @@ You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrinc
Type: String
Parameter Sets: MobileDeviceIdentity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -118,15 +114,13 @@ Accept wildcard characters: False
```
### -ActiveSync
-
-> Applicable: Exchange Online
-
The ActiveSync switch filters the results by Exchange ActiveSync devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -136,9 +130,6 @@ Accept wildcard characters: False
```
### -ExternalDirectoryObjectId
-
-> Applicable: Exchange Online
-
The ExternalDirectoryObjectId parameter identifies the mailbox that you want to view by the ObjectId in Microsoft Entra ID.
You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrincipalName parameters.
@@ -147,6 +138,7 @@ You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrinc
Type: Guid
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -156,15 +148,13 @@ Accept wildcard characters: False
```
### -GetMailboxLog
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -174,15 +164,13 @@ Accept wildcard characters: False
```
### -NotificationEmailAddresses
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -192,15 +180,13 @@ Accept wildcard characters: False
```
### -OWAforDevices
-
-> Applicable: Exchange Online
-
The OWAforDevices switch filters the results by devices where Outlook on the web for devices is enabled. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -210,9 +196,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the mailbox that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or UserPrincipalName parameters.
@@ -221,6 +204,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Us
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -230,15 +214,13 @@ Accept wildcard characters: False
```
### -RestApi
-
-> Applicable: Exchange Online
-
The RestApi switch filters the results by REST API devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -248,15 +230,13 @@ Accept wildcard characters: False
```
### -ShowRecoveryPassword
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -266,15 +246,13 @@ Accept wildcard characters: False
```
### -UniversalOutlook
-
-> Applicable: Exchange Online
-
The UniversalOutlook switch filters the results by Mail and Calendar devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -284,9 +262,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the ExternalDirectoryObjectId, Mailbox, Identity, or PrimarySmtpAddress parameters.
@@ -295,6 +270,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Mailbox, Identi
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md b/exchange/exchange-ps/exchange/Get-EXORecipient.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md
rename to exchange/exchange-ps/exchange/Get-EXORecipient.md
index eac17545ab..fd34b10f9d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md
+++ b/exchange/exchange-ps/exchange/Get-EXORecipient.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exorecipient
applicable: Exchange Online
+title: Get-EXORecipient
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exorecipient
-schema: 2.0.0
-title: Get-EXORecipient
+ms.reviewer:
---
# Get-EXORecipient
@@ -76,9 +76,6 @@ This example returns the recipient attribute details for the user john@contoso.c
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the recipient object that you want to view. For the best performance, we recommend using the following values to identify the recipient:
- User ID or user principal name (UPN)
@@ -100,6 +97,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, PrimarySmt
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -109,9 +107,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Online
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -126,6 +121,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, Prima
Type: String
Parameter Sets: Anr
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -135,9 +131,6 @@ Accept wildcard characters: False
```
### -ExternalDirectoryObjectId
-
-> Applicable: Exchange Online
-
The ExternalDirectoryObjectId parameter identifies the recipient that you want to view by the ObjectId in Microsoft Entra ID.
You can't use this parameter with the Anr, Identity, PrimarySmtpAddress, or UserPrincipalName parameters.
@@ -146,6 +139,7 @@ You can't use this parameter with the Anr, Identity, PrimarySmtpAddress, or User
Type: Guid
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -155,9 +149,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -173,6 +164,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -182,9 +174,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedRecipients
-
-> Applicable: Exchange Online
-
The IncludeSoftDeletedRecipients switch specifies whether to include soft deleted recipients in the results. You don't need to specify a value with this switch.
Soft-deleted recipients are deleted recipients that are still recoverable.
@@ -193,6 +182,7 @@ Soft-deleted recipients are deleted recipients that are still recoverable.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -202,9 +192,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Online
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's visible using the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -216,6 +203,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -225,9 +213,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the recipient that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity or UserPrincipalName parameters.
@@ -236,6 +221,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity o
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -245,9 +231,6 @@ Accept wildcard characters: False
```
### -Properties
-
-> Applicable: Exchange Online
-
The Properties parameter specifies the properties that are returned in the output of this cmdlet. You can specify multiple values separated by commas.
For more information about the available properties, see [Get-EXORecipient property sets](https://learn.microsoft.com/powershell/exchange/cmdlet-property-sets#get-exorecipient-property-sets).
@@ -256,6 +239,7 @@ For more information about the available properties, see [Get-EXORecipient prope
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -265,9 +249,6 @@ Accept wildcard characters: False
```
### -PropertySets
-
-> Applicable: Exchange Online
-
The PropertySets parameter specifies a logical grouping of properties that are returned in the output of this cmdlet. Valid values are:
- Minimum (this is the default value)
@@ -282,6 +263,7 @@ For more information about the properties that are included in each property set
Type: PropertySet[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -291,15 +273,13 @@ Accept wildcard characters: False
```
### -RecipientPreviewFilter
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -309,9 +289,6 @@ Accept wildcard characters: False
```
### -RecipientType
-
-> Applicable: Exchange Online
-
The RecipientType parameter filters the results by the specified recipient type. Valid values are:
- DynamicDistributionGroup
@@ -329,6 +306,7 @@ You can specify multiple values separated by commas.
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -338,9 +316,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Online
-
The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are:
- DiscoveryMailbox
@@ -380,6 +355,7 @@ The value of the RecipientType parameter affects the values that you can use for
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -389,15 +365,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -407,9 +381,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the recipient that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity, or PrimarySmtpAddress parameters.
@@ -418,6 +389,7 @@ You can't use this parameter with the Anr, ExternalDirectoryObjectId, Identity,
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md b/exchange/exchange-ps/exchange/Get-EXORecipientPermission.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md
rename to exchange/exchange-ps/exchange/Get-EXORecipientPermission.md
index 41c27a1675..3ec37b7a9d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md
+++ b/exchange/exchange-ps/exchange/Get-EXORecipientPermission.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exorecipientpermission
applicable: Exchange Online
+title: Get-EXORecipientPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exorecipientpermission
-schema: 2.0.0
-title: Get-EXORecipientPermission
+ms.reviewer:
---
# Get-EXORecipientPermission
@@ -56,9 +56,6 @@ Above example returns recipient permission for first 100 mailbox users in the na
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter identifies the recipient that you want to view. The user or group specified by the Trustee parameter has Send As permissions on this recipient. You can specify any type of recipient, for example:
- Mailboxes
@@ -88,6 +85,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, PrimarySmtpAddr
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -97,15 +95,13 @@ Accept wildcard characters: False
```
### -AccessRights
-
-> Applicable: Exchange Online
-
The AccessRights parameter filters the results by permission. The only valid value for this parameter is SendAs.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -115,9 +111,6 @@ Accept wildcard characters: False
```
### -ExternalDirectoryObjectId
-
-> Applicable: Exchange Online
-
The ExternalDirectoryObjectId parameter identifies the recipient that you want to view by the ObjectId in Microsoft Entra ID.
You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrincipalName parameters.
@@ -126,6 +119,7 @@ You can't use this parameter with the Identity, PrimarySmtpAddress, or UserPrinc
Type: Guid
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -135,9 +129,6 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Online
-
The PrimarySmtpAddress identifies the recipient that you want to view by primary SMTP email address (for example, navin@contoso.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or UserPrincipalName parameters.
@@ -146,6 +137,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Us
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -155,15 +147,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -173,9 +163,6 @@ Accept wildcard characters: False
```
### -Trustee
-
-> Applicable: Exchange Online
-
The Trustee parameter filters the results by the user or group who has Send As permissions. You can specify the following types of users or groups:
- Mailbox users
@@ -198,6 +185,7 @@ You need to use this parameter with the Identity, PrimarySmtpAddress, UserPrinci
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -207,9 +195,6 @@ Accept wildcard characters: False
```
### -UserPrincipalName
-
-> Applicable: Exchange Online
-
The UserPrincipalName parameter identifies the recipient that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
You can't use this parameter with the ExternalDirectoryObjectId, Identity, or PrimarySmtpAddress parameters.
@@ -218,6 +203,7 @@ You can't use this parameter with the ExternalDirectoryObjectId, Identity, or Pr
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
rename to exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md
index 250dab85ba..1235c14ba1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/Get-EcpVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ecpvirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-EcpVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ecpvirtualdirectory
-schema: 2.0.0
-title: Get-EcpVirtualDirectory
+ms.reviewer:
---
# Get-EcpVirtualDirectory
@@ -70,9 +69,6 @@ This example returns a summary list of all Exchange Control Panel virtual direct
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the ECP virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -87,6 +83,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -96,9 +93,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -112,6 +106,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -121,9 +116,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -132,6 +124,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,15 +134,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -159,9 +150,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
By default, this cmdlet shows information about virtual directories in the Client Access services on Mailbox servers. Client connections are proxied from the Client Access services on Mailbox servers to the backend services on Mailbox servers. Clients don't connect directly to the backend services.
@@ -172,6 +160,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md b/exchange/exchange-ps/exchange/Get-EdgeSubscription.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
rename to exchange/exchange-ps/exchange/Get-EdgeSubscription.md
index 75362938ad..4e288d9293 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
+++ b/exchange/exchange-ps/exchange/Get-EdgeSubscription.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-edgesubscription
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-EdgeSubscription
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-edgesubscription
-schema: 2.0.0
-title: Get-EdgeSubscription
+ms.reviewer:
---
# Get-EdgeSubscription
@@ -51,15 +50,13 @@ This example retrieves the Edge Subscription information for the Edge Transport
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of the Edge Transport server for which you want to retrieve Edge Subscription information. The identity is expressed as the host name of the Edge Transport server. If no identity is specified, all Edge Subscriptions are returned.
```yaml
Type: TransportServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -80,6 +74,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md b/exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
rename to exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md
index 0f9ce42282..fa33987f4c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/exchange/Get-EdgeSyncServiceConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-edgesyncserviceconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-EdgeSyncServiceConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-edgesyncserviceconfig
-schema: 2.0.0
-title: Get-EdgeSyncServiceConfig
+ms.reviewer:
---
# Get-EdgeSyncServiceConfig
@@ -43,15 +42,13 @@ This example reads the configuration of the Microsoft Exchange EdgeSync service
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of the Microsoft Exchange EdgeSync service configuration you want to view.
```yaml
Type: EdgeSyncServiceConfigIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -61,15 +58,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -79,15 +74,13 @@ Accept wildcard characters: False
```
### -Site
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Site parameter specifies the Active Directory site that EdgeSync connects to for synchronizing configuration and recipient data.
```yaml
Type: AdSiteIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md b/exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
rename to exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md
index dabfa9610d..fe9c386e7f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
+++ b/exchange/exchange-ps/exchange/Get-EligibleDistributionGroupForMigration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-eligibledistributiongroupformigration
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-EligibleDistributionGroupForMigration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-eligibledistributiongroupformigration
-schema: 2.0.0
-title: Get-EligibleDistributionGroupForMigration
+ms.reviewer:
---
# Get-EligibleDistributionGroupForMigration
@@ -52,9 +51,6 @@ This example returns a summary list of all distribution groups that can be upgra
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter filters the results by the email address of the specified distribution group. If no results are returned for the specified email address, the group can't be upgraded to a Microsoft 365 Group.
You can't use this parameter with the ManagedBy parameter.
@@ -63,6 +59,7 @@ You can't use this parameter with the ManagedBy parameter.
Type: DistributionGroupIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -ManagedBy
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ManagedBy parameter filters the results by the manager of the distribution group (the ManagedBy property). You can use any value that uniquely identifies the distribution group manager. For example:
- Name
@@ -90,6 +84,7 @@ You can't use this parameter with the Identity parameter.
Type: GeneralRecipientIdParameter
Parameter Sets: ManagedBy
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -99,9 +94,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -113,6 +105,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -122,15 +115,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
rename to exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md
index ccc466c3b6..1cb8b5a7a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-EmailAddressPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-emailaddresspolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-EmailAddressPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-emailaddresspolicy
-schema: 2.0.0
-title: Get-EmailAddressPolicy
+ms.reviewer:
---
# Get-EmailAddressPolicy
@@ -50,9 +49,6 @@ This example returns detailed information for the email address policy named Con
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the email address policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the email address policy that you want to view.
Type: EmailAddressPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -83,6 +77,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -92,9 +87,6 @@ Accept wildcard characters: False
```
### -IncludeMailboxSettingOnlyPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is functional only in Exchange Server 2010.
The IncludeMailboxSettingOnlyPolicy switch retrieves Microsoft Exchange Server 2003 address policies that contain only mailbox management configuration. You don't need to specify a value with this switch.
@@ -107,6 +99,7 @@ The attributes of address policies that contain only mailbox management configur
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md b/exchange/exchange-ps/exchange/Get-EmailTenantSettings.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md
rename to exchange/exchange-ps/exchange/Get-EmailTenantSettings.md
index 8fa56a3fe5..025fdca73a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md
+++ b/exchange/exchange-ps/exchange/Get-EmailTenantSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-emailtenantsettings
applicable: Exchange Online
+title: Get-EmailTenantSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-emailtenantsettings
-schema: 2.0.0
-title: Get-EmailTenantSettings
+ms.reviewer:
---
# Get-EmailTenantSettings
@@ -40,15 +39,13 @@ This example shows whether priority account protection is enabled or disabled in
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the settings object that you want to view. The only settings object in the organization is named Default.
```yaml
Type: EmailTenantSettingsIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md b/exchange/exchange-ps/exchange/Get-EtrLimits.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md
rename to exchange/exchange-ps/exchange/Get-EtrLimits.md
index ddcf5e44e4..759a8d045c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md
+++ b/exchange/exchange-ps/exchange/Get-EtrLimits.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-etrlimits
applicable: Exchange Online, Exchange Online Protection
+title: Get-EtrLimits
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-etrlimits
-schema: 2.0.0
-title: Get-EtrLimits
+ms.reviewer:
---
# Get-EtrLimits
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md b/exchange/exchange-ps/exchange/Get-EventLogLevel.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
rename to exchange/exchange-ps/exchange/Get-EventLogLevel.md
index e44116bb97..cc925f4f3d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
+++ b/exchange/exchange-ps/exchange/Get-EventLogLevel.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-eventloglevel
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-EventLogLevel
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-eventloglevel
-schema: 2.0.0
-title: Get-EventLogLevel
+ms.reviewer:
---
# Get-EventLogLevel
@@ -50,9 +49,6 @@ This example displays the event categories and log levels for the server Exchang
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter filters the results by the name of the event category. To see the available event categories, run the following command: Get-EventLogLevel.
You can't use this parameter with the Server parameter.
@@ -61,6 +57,7 @@ You can't use this parameter with the Server parameter.
Type: ECIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -70,9 +67,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -86,6 +80,7 @@ You can't use this parameter with the Identity parameter.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -106,6 +98,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md b/exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md
rename to exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md
index 739c0aca33..30df67b8a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-eventsfromemailconfiguration
applicable: Exchange Online
+title: Get-EventsFromEmailConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-eventsfromemailconfiguration
-schema: 2.0.0
-title: Get-EventsFromEmailConfiguration
+ms.reviewer:
---
# Get-EventsFromEmailConfiguration
@@ -43,15 +42,13 @@ This example retrieves all events from email settings for peter@contoso.com's ma
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You identify the mailbox by email address.
```yaml
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md b/exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
rename to exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md
index 6935ba187f..d2853de47a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
+++ b/exchange/exchange-ps/exchange/Get-ExchangeAssistanceConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangeassistanceconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ExchangeAssistanceConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangeassistanceconfig
-schema: 2.0.0
-title: Get-ExchangeAssistanceConfig
+ms.reviewer:
---
# Get-ExchangeAssistanceConfig
@@ -49,15 +48,13 @@ This example shows the configuration information for all organizations and forma
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the organization.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -78,6 +72,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Get-ExchangeCertificate.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
rename to exchange/exchange-ps/exchange/Get-ExchangeCertificate.md
index fea0c58a77..eec9e123ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
+++ b/exchange/exchange-ps/exchange/Get-ExchangeCertificate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangecertificate
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ExchangeCertificate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangecertificate
-schema: 2.0.0
-title: Get-ExchangeCertificate
+ms.reviewer:
---
# Get-ExchangeCertificate
@@ -127,9 +126,6 @@ This example shows which certificate Exchange will select for the domain name ma
## PARAMETERS
### -Thumbprint
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Thumbprint parameter specifies the thumbprint value of the certificate that you want to view.
The Thumbprint parameter, not the Identity parameter, is the positional parameter for this cmdlet. Therefore, when you specify a thumbprint value by itself, the command uses that value for the Thumbprint parameter.
@@ -138,6 +134,7 @@ The Thumbprint parameter, not the Identity parameter, is the positional paramete
Type: String
Parameter Sets: Thumbprint
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -147,9 +144,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the certificate that you want to view. Valid values are:
- `ServerNameOrFQDN\Thumbprint`
@@ -163,6 +157,7 @@ The Thumbprint parameter, not the Identity parameter, is the positional paramete
Type: ExchangeCertificateIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -172,9 +167,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -183,6 +175,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -192,15 +185,13 @@ Accept wildcard characters: False
```
### -DomainName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainName parameter filters the results by the fully qualified domain name (FQDN) or server name values in the Subject Name or the Subject Alternative Name fields. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -210,15 +201,13 @@ Accept wildcard characters: False
```
### -Instance
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter has been deprecated and is no longer used.
```yaml
Type: X509Certificate2
Parameter Sets: Instance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -228,9 +217,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -246,6 +232,7 @@ You can't use this parameter with the Identity parameter, but you can use it wit
Type: ServerIdParameter
Parameter Sets: Instance, Thumbprint
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md b/exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
rename to exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md
index 26ef51e172..ca36c14478 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
+++ b/exchange/exchange-ps/exchange/Get-ExchangeDiagnosticInfo.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.Management-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangediagnosticinfo
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ExchangeDiagnosticInfo
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangediagnosticinfo
-schema: 2.0.0
-title: Get-ExchangeDiagnosticInfo
+ms.reviewer:
---
# Get-ExchangeDiagnosticInfo
@@ -54,9 +53,6 @@ This example display the XML output of the command in format that's easier to re
## PARAMETERS
### -Argument
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Argument parameter specifies a valid argument to use with the specified Component value.
Common Argument values that you can use with virtually Component value are Help and Verbose.
@@ -67,6 +63,7 @@ To see the Argument values that are available for a given Component value, run t
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -76,9 +73,6 @@ Accept wildcard characters: False
```
### -Component
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Component parameter returns detailed information for the specified Component of the given Process value.
To see the Component values that are available for a given Process value, run the command `Get-ExchangeDiagnosticInfo -Process ProcessName -Argument Help`.
@@ -87,6 +81,7 @@ To see the Component values that are available for a given Process value, run th
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -96,9 +91,6 @@ Accept wildcard characters: False
```
### -Process
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Process parameter provides details for the specified Exchange process. Valid values are the name of the process (for example, MSExchangeTransport or Microsoft.Exchange.Directory.TopologyService).
To see the list of available Exchange processes, run the command Get-ExchangeDiagnosticInfo.
@@ -107,6 +99,7 @@ To see the list of available Exchange processes, run the command Get-ExchangeDia
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -132,6 +122,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,15 +132,13 @@ Accept wildcard characters: False
```
### -Unlimited
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Unlimited switch tells the command to return all available information. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md b/exchange/exchange-ps/exchange/Get-ExchangeFeature.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
rename to exchange/exchange-ps/exchange/Get-ExchangeFeature.md
index 124cbe2406..6bf6bb29bf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
+++ b/exchange/exchange-ps/exchange/Get-ExchangeFeature.md
@@ -1,14 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangefeature
applicable: Exchange Server 2019
+title: Get-ExchangeFeature
+schema: 2.0.0
author: lusassl-msft
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: lusassl
ms.reviewer: srvar
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangefeature
-schema: 2.0.0
-title: Get-ExchangeFeature
---
# Get-ExchangeFeature
@@ -52,9 +50,6 @@ This example returns information about the feature with the feature id PING.1.0.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2019
-
The Identity parameter specifies the Exchange server that you want to modify. You can use any value that uniquely identifies the server. For example:
- Name
@@ -68,6 +63,7 @@ If you don't use this parameter, the command returns information for all Exchang
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: 0
@@ -77,15 +73,13 @@ Accept wildcard characters: False
```
### -FeatureID
-
-> Applicable: Exchange Server 2019
-
The FeatureID parameter specifies the feature you want to query information about.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -95,15 +89,13 @@ Accept wildcard characters: False
```
### -RingLevel
-
-> Applicable: Exchange Server 2019
-
The RingLevel parameter specifies the ring level you want to query information about.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -113,15 +105,13 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2019
-
The Status parameter specifies the status you want to query information about.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md b/exchange/exchange-ps/exchange/Get-ExchangeServer.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
rename to exchange/exchange-ps/exchange/Get-ExchangeServer.md
index 5bbf2d4944..4331ccbb63 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
+++ b/exchange/exchange-ps/exchange/Get-ExchangeServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangeserver
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ExchangeServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangeserver
-schema: 2.0.0
-title: Get-ExchangeServer
+ms.reviewer:
---
# Get-ExchangeServer
@@ -63,9 +62,6 @@ This example returns detailed information about the Exchange server named Mailbo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Exchange server that you want to view. You can use any value that uniquely identifies the Exchange server. For example:
- Name
@@ -79,6 +75,7 @@ You can't use this parameter with the Domain parameter.
Type: ServerIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -88,9 +85,6 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Domain parameter filters the results by the fully qualified domain name (FQDN) of the domain (for example, contoso.com).
You can't use this parameter with the Identity parameter.
@@ -99,6 +93,7 @@ You can't use this parameter with the Identity parameter.
Type: Fqdn
Parameter Sets: Domain
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -108,9 +103,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -119,6 +111,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -128,9 +121,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Status switch specifies whether to include additional property values in the results, for example, the Watson state, StaticDomainControllers, and runtime domain controller usage. You don't need to specify a value with this switch.
To see the additional values, you need to pipe the output to a formatting cmdlet, for example, the Format-List cmdlet.
@@ -139,6 +129,7 @@ To see the additional values, you need to pipe the output to a formatting cmdlet
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md b/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
rename to exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md
index 1663316338..4d95f68bfd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
+++ b/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicense.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangeserveraccesslicense
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ExchangeServerAccessLicense
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangeserveraccesslicense
-schema: 2.0.0
-title: Get-ExchangeServerAccessLicense
+ms.reviewer:
---
# Get-ExchangeServerAccessLicense
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md b/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
rename to exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md
index 4c452c27b0..4c62c163e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
+++ b/exchange/exchange-ps/exchange/Get-ExchangeServerAccessLicenseUser.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangeserveraccesslicenseuser
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ExchangeServerAccessLicenseUser
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangeserveraccesslicenseuser
-schema: 2.0.0
-title: Get-ExchangeServerAccessLicenseUser
+ms.reviewer:
---
# Get-ExchangeServerAccessLicenseUser
@@ -43,9 +42,6 @@ This example returns the unique users for the license named Exchange Server 2016
## PARAMETERS
### -LicenseName
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LicenseName parameter specifies the license type that you want to view. You can find the available license type values by running the Get-ExchangeServerAccessLicense cmdlet. Valid values are:
- `Exchange Server Standard CAL`
@@ -59,6 +55,7 @@ The `` value is 2013, 2016, or 2019.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md b/exchange/exchange-ps/exchange/Get-ExchangeSettings.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
rename to exchange/exchange-ps/exchange/Get-ExchangeSettings.md
index 23cefad71d..9088353301 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
+++ b/exchange/exchange-ps/exchange/Get-ExchangeSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exchangesettings
applicable: Exchange Server 2016, Exchange Server 2019
+title: Get-ExchangeSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exchangesettings
-schema: 2.0.0
-title: Get-ExchangeSettings
+ms.reviewer:
---
# Get-ExchangeSettings
@@ -61,9 +60,6 @@ This example returns a summary list of all Exchange setting objects.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of the Exchange setting object. You can use any value that uniquely identifies the object. For example:
- Name
@@ -74,6 +70,7 @@ The Identity parameter specifies the name of the Exchange setting object. You ca
Type: ExchangeSettingsIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -83,9 +80,6 @@ Accept wildcard characters: False
```
### -ConfigName
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The ConfigName parameter filter the results by the specified property name. The value you specify is visible in the EffectiveSetting property.
The available values are determined by the schema of the Exchange setting object.
@@ -94,6 +88,7 @@ The available values are determined by the schema of the Exchange setting object
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -103,9 +98,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Database parameter filters the results by mailbox database. You can use any value that uniquely identifies the database. For example:
- Name
@@ -117,6 +109,7 @@ The Database parameter filters the results by mailbox database. You can use any
Type: DatabaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -126,9 +119,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
The detailed information is visible in the DiagnosticInfo property.
@@ -139,6 +129,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -148,15 +139,13 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -166,15 +155,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -184,9 +171,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -195,6 +179,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -204,15 +189,13 @@ Accept wildcard characters: False
```
### -GenericScopeName
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The GenericScopeName parameter filters the results by the scope. The available values are determined by the schema of the Exchange setting object.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -222,15 +205,13 @@ Accept wildcard characters: False
```
### -GenericScopes
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The GenericScopes parameter filters the results by the scope. The available values are determined by the schema of the Exchange setting object. This parameter uses the syntax `"key1=value1","key2=value2", "keyN=valueN`.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -240,15 +221,13 @@ Accept wildcard characters: False
```
### -GenericScopeValue
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The GenericScopeValue parameter filters the results by the value of the scope specified by the GenericScopeName parameter. The available values are determined by the schema of the Exchange setting object.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -258,15 +237,13 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -276,15 +253,13 @@ Accept wildcard characters: False
```
### -Process
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Process parameter filters the results by the specified process. The available values are determined by the schema of the Exchange setting object.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -294,9 +269,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Server parameter filters the results by Exchange server. You can use any value that uniquely identifies the server. For example:
- Name
@@ -308,6 +280,7 @@ The Server parameter filters the results by Exchange server. You can use any val
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -317,15 +290,13 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The User parameter filters the results by user. You identify the user by their GUID value (for example, 87246450-1b19-4c81-93dc-1a4200eff66c). To find the GUID for a user, run the following command: `Get-User | Format-List Name,GUID`.
```yaml
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md
rename to exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md
index 593507275d..08f6210738 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exoinformationbarrierpolicy
applicable: Exchange Online
+title: Get-ExoInformationBarrierPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exoinformationbarrierpolicy
-schema: 2.0.0
-title: Get-ExoInformationBarrierPolicy
+ms.reviewer:
---
# Get-ExoInformationBarrierPolicy
@@ -47,9 +46,6 @@ This example shows detailed information for the specified Exchange Online inform
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the Exchange Online information barrier policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -61,6 +57,7 @@ The Identity parameter specifies the Exchange Online information barrier policy
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -70,9 +67,6 @@ Accept wildcard characters: False
```
### -ShowFriendlyValues
-
-> Applicable: Exchange Online
-
The ShowFriendlyValues switch specifies whether to show friendly values in the output of the command. You don't need to specify a value with this switch.
When you use this switch, the following property values are shown:
@@ -84,6 +78,7 @@ When you use this switch, the following property values are shown:
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md
rename to exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md
index a21fb872a1..8e1ddb9d25 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md
+++ b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierRelationship.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exoinformationbarrierrelationship
applicable: Exchange Online
+title: Get-ExoInformationBarrierRelationship
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exoinformationbarrierrelationship
-schema: 2.0.0
-title: Get-ExoInformationBarrierRelationship
+ms.reviewer:
---
# Get-ExoInformationBarrierRelationship
@@ -41,9 +40,6 @@ This example shows the Exchange Online information barrier relationship between
## PARAMETERS
### -RecipientId1
-
-> Applicable: Exchange Online
-
The RecipientId1 parameter specifies the first recipient in the Exchange Online barrier relationship. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -57,6 +53,7 @@ The RecipientId1 parameter specifies the first recipient in the Exchange Online
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -66,9 +63,6 @@ Accept wildcard characters: False
```
### -RecipientId2
-
-> Applicable: Exchange Online
-
The RecipientId2 parameter specifies the second recipient in the Exchange Online barrier relationship. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -82,6 +76,7 @@ The RecipientId2 parameter specifies the second recipient in the Exchange Online
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md
rename to exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md
index 2133d84497..b0caf1efcb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md
+++ b/exchange/exchange-ps/exchange/Get-ExoInformationBarrierSegment.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exoinformationbarriersegment
applicable: Exchange Online
+title: Get-ExoInformationBarrierSegment
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exoinformationbarriersegment
-schema: 2.0.0
-title: Get-ExoInformationBarrierSegment
+ms.reviewer:
---
# Get-ExoInformationBarrierSegment
@@ -47,9 +46,6 @@ This example shows detailed information for the specified Exchange Online inform
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the Exchange Online information barrier segment that you want to view. You can use any value that uniquely identifies the segment. For example:
- Name
@@ -61,6 +57,7 @@ The Identity parameter specifies the Exchange Online information barrier segment
Type: InformationBarrierSegmentIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -70,9 +67,6 @@ Accept wildcard characters: False
```
### -ShowFriendlyValues
-
-> Applicable: Exchange Online
-
The ShowFriendlyValues switch specifies whether to show friendly values in the output of the command. You don't need to specify a value with this switch.
When you use this switch, the FriendlyMembershipFilter property value is shown.
@@ -81,6 +75,7 @@ When you use this switch, the FriendlyMembershipFilter property value is shown.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md
rename to exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md
index 3b747b043e..f909f50138 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md
+++ b/exchange/exchange-ps/exchange/Get-ExoPhishSimOverrideRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exophishsimoverriderule
applicable: Exchange Online
+title: Get-ExoPhishSimOverrideRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exophishsimoverriderule
-schema: 2.0.0
-title: Get-ExoPhishSimOverrideRule
+ms.reviewer:
---
# Get-ExoPhishSimOverrideRule
@@ -54,9 +53,6 @@ Although the previous command should return only one rule, a rule that's pending
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the phishing simulation override rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -70,6 +66,7 @@ The name of the rule uses the following syntax: `_Exe:PhishSimOverr:` \[s
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Exchange Online
-
The Policy parameter filters the results by phishing simulator override policy. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -129,6 +119,7 @@ The Policy parameter filters the results by phishing simulator override policy.
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -138,15 +129,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md
rename to exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md
index 6a7a7b3409..8fd400e919 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md
+++ b/exchange/exchange-ps/exchange/Get-ExoSecOpsOverrideRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-exosecopsoverriderule
applicable: Exchange Online
+title: Get-ExoSecOpsOverrideRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-exosecopsoverriderule
-schema: 2.0.0
-title: Get-ExoSecOpsOverrideRule
+ms.reviewer:
---
# Get-ExoSecOpsOverrideRule
@@ -54,9 +53,6 @@ Although the previous command should return only one rule, a rule that's pending
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the SecOps override rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -70,6 +66,7 @@ The name of the rule uses the following syntax: `_Exe:SecOpsOverrid:` \[s
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Exchange Online
-
The Policy parameter filters the results by SecOps mailbox override policy. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -129,6 +119,7 @@ The Policy parameter filters the results by SecOps mailbox override policy. You
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -138,15 +129,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md b/exchange/exchange-ps/exchange/Get-ExternalInOutlook.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md
rename to exchange/exchange-ps/exchange/Get-ExternalInOutlook.md
index 8da1e93597..451de0b213 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md
+++ b/exchange/exchange-ps/exchange/Get-ExternalInOutlook.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-externalinoutlook
applicable: Exchange Online, Exchange Online Protection
+title: Get-ExternalInOutlook
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-externalinoutlook
-schema: 2.0.0
-title: Get-ExternalInOutlook
+ms.reviewer:
---
# Get-ExternalInOutlook
@@ -45,15 +44,13 @@ This example returns the settings of the external sender identification feature
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the GUID of the external sender identification object that you want to view. Although this parameter is available, you don't need to use it.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md b/exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
rename to exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md
index 509c2fe2d2..14df25198f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
+++ b/exchange/exchange-ps/exchange/Get-FailedContentIndexDocuments.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-failedcontentindexdocuments
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-FailedContentIndexDocuments
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-failedcontentindexdocuments
-schema: 2.0.0
-title: Get-FailedContentIndexDocuments
+ms.reviewer:
---
# Get-FailedContentIndexDocuments
@@ -92,9 +91,6 @@ This example retrieves a list of items that couldn't be indexed by Exchange Sear
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -112,6 +108,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -121,9 +118,6 @@ Accept wildcard characters: False
```
### -MailboxDatabase
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MailboxDatabase parameter specifies the database from which to get the mailbox. You can use any value that uniquely identifies the database. For example:
- Name
@@ -134,6 +128,7 @@ The MailboxDatabase parameter specifies the database from which to get the mailb
Type: DatabaseIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -143,9 +138,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies a Mailbox server. You can use the following values:
- Name
@@ -156,6 +148,7 @@ The Server parameter specifies a Mailbox server. You can use the following value
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -165,9 +158,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -177,6 +167,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -186,15 +177,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -204,9 +193,6 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Archive switch restricts the scope of the cmdlet to the user's archive. You don't need to specify a value with this switch.
When using the Archive switch, you must also specify the Identity parameter.
@@ -215,6 +201,7 @@ When using the Archive switch, you must also specify the Identity parameter.
Type: SwitchParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -224,9 +211,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -235,6 +219,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -244,15 +229,13 @@ Accept wildcard characters: False
```
### -ErrorCode
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ErrorCode parameter allows you to retrieve documents that failed indexing with a specific error code. You can use the cmdlet without this parameter to list all failed documents for a mailbox, a mailbox database or a Mailbox server. The output includes the error codes and reason for failure. If required, you can then restrict the output to a specific error code from the results.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -262,9 +245,6 @@ Accept wildcard characters: False
```
### -FailureMode
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FailureMode parameter specifies the type of error. Use the following values.
- Transient: Returns items that couldn't be indexed due to transient errors. Exchange Search attempts to index these items again.
@@ -275,6 +255,7 @@ The FailureMode parameter specifies the type of error. Use the following values.
Type: FailureMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -284,15 +265,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -302,9 +281,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -313,6 +289,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -322,15 +299,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FeatureConfiguration.md b/exchange/exchange-ps/exchange/Get-FeatureConfiguration.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FeatureConfiguration.md
rename to exchange/exchange-ps/exchange/Get-FeatureConfiguration.md
index ae9ba0feae..87063ff596 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FeatureConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-FeatureConfiguration.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-featureconfiguration
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/get-featureconfiguration
+applicable: Security & Compliance
title: Get-FeatureConfiguration
+schema: 2.0.0
---
# Get-FeatureConfiguration
@@ -54,9 +52,6 @@ This example returns detailed information about the specified collection policy.
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity policy specifies the feature configuration that you want to view. You can use any value that uniquely identifies the configuration. For example:
- Name
@@ -67,6 +62,7 @@ The Identity policy specifies the feature configuration that you want to view. Y
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -76,9 +72,6 @@ Accept wildcard characters: False
```
### -FeatureScenario
-
-> Applicable: Security & Compliance
-
The FeatureScenario parameter specifies the scenario for the feature configuration. Currently, the only valid values are:
- `KnowYourData` for collection policies
- `TrustContainer` for Endpoint DLP trust container
@@ -87,6 +80,7 @@ The FeatureScenario parameter specifies the scenario for the feature configurati
Type: PolicyScenario
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -96,15 +90,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -114,15 +106,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md b/exchange/exchange-ps/exchange/Get-FederatedDomainProof.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
rename to exchange/exchange-ps/exchange/Get-FederatedDomainProof.md
index 6e8cafa070..498c943b79 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
+++ b/exchange/exchange-ps/exchange/Get-FederatedDomainProof.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-federateddomainproof
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-FederatedDomainProof
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-federateddomainproof
-schema: 2.0.0
-title: Get-FederatedDomainProof
+ms.reviewer:
---
# Get-FederatedDomainProof
@@ -52,15 +51,13 @@ This example uses a specific certificate for the domain contoso.com.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainName parameter specifies the domain name for which the cryptographically secure string is generated.
```yaml
Type: SmtpDomain
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -70,15 +67,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -88,15 +83,13 @@ Accept wildcard characters: False
```
### -Thumbprint
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Thumbprint parameter specifies the thumbprint of an existing certificate.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
rename to exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md
index 9e34d46c14..141f7f644a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
+++ b/exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-federatedorganizationidentifier
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-FederatedOrganizationIdentifier
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-federatedorganizationidentifier
-schema: 2.0.0
-title: Get-FederatedOrganizationIdentifier
+ms.reviewer:
---
# Get-FederatedOrganizationIdentifier
@@ -52,15 +51,13 @@ This example retrieves the Exchange organization's federated organization identi
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the organization ID.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -70,9 +67,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -81,6 +75,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -90,9 +85,6 @@ Accept wildcard characters: False
```
### -IncludeExtendedDomainInfo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The IncludeExtendedDomainInfo switch specifies that the command query Microsoft Federation Gateway for the status of each accepted domain that's federated. You don't need to specify a value with this switch.
The status is returned with each domain in the Domains property.
@@ -101,6 +93,7 @@ The status is returned with each domain in the Domains property.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md b/exchange/exchange-ps/exchange/Get-FederationInformation.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
rename to exchange/exchange-ps/exchange/Get-FederationInformation.md
index 3d86985c9a..bcd6a357a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
+++ b/exchange/exchange-ps/exchange/Get-FederationInformation.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-federationinformation
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-FederationInformation
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-federationinformation
-schema: 2.0.0
-title: Get-FederationInformation
+ms.reviewer:
---
# Get-FederationInformation
@@ -49,15 +48,13 @@ This example gets federation information from the domain contoso.com.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The DomainName parameter specifies the domain name for which federation information is to be retrieved.
```yaml
Type: SmtpDomain
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -BypassAdditionalDomainValidation
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The BypassAdditionalDomainValidation switch specifies that the command skip validation of domains from the external Exchange organization. You don't need to specify a value with this switch.
We recommend that you only use this switch to retrieve federation information in a hybrid deployment between on-premises and Exchange Online organizations. Don't use this switch to retrieve federation information for on-premises Exchange organizations in a cross-organization arrangement.
@@ -78,6 +72,7 @@ We recommend that you only use this switch to retrieve federation information in
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -87,9 +82,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
A confirmation prompt warns you if the host name in the Autodiscover endpoint of the domain doesn't match the Secure Sockets Layer (SSL) certificate presented by the endpoint and the host name isn't specified in the TrustedHostnames parameter.
@@ -98,6 +90,7 @@ A confirmation prompt warns you if the host name in the Autodiscover endpoint of
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -107,15 +100,13 @@ Accept wildcard characters: False
```
### -TrustedHostnames
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The TrustedHostnames parameter specifies the fully qualified domain name (FQDN) of federation endpoints. Federation endpoints are the client access (frontend) services on Mailbox servers in an organization with federation enabled. Explicitly specifying the TrustedHostnames parameter allows the cmdlet to bypass prompting if the certificate presented by the endpoint doesn't match the domain name specified in the DomainName parameter.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md b/exchange/exchange-ps/exchange/Get-FederationTrust.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
rename to exchange/exchange-ps/exchange/Get-FederationTrust.md
index e4bb95f38d..98175c1a29 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
+++ b/exchange/exchange-ps/exchange/Get-FederationTrust.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-federationtrust
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-FederationTrust
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-federationtrust
-schema: 2.0.0
-title: Get-FederationTrust
+ms.reviewer:
---
# Get-FederationTrust
@@ -42,15 +41,13 @@ This example retrieves properties of the federation trust configured for the Exc
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies a federation trust ID. If not specified, the cmdlet returns all federation trusts configured for the Exchange organization.
```yaml
Type: FederationTrustIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -60,9 +57,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -71,6 +65,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyAuthority.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyAuthority.md
rename to exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md
index 057baf0d1d..023b70021a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyAuthority.md
+++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyAuthority.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-fileplanpropertyauthority
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertyauthority
+applicable: Security & Compliance
title: Get-FilePlanPropertyAuthority
+schema: 2.0.0
---
# Get-FilePlanPropertyAuthority
@@ -45,9 +43,6 @@ This example returns detailed information about the custom file plan property au
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the custom file plan property authority that you want to view. You can use any value that uniquely identifies the authority. For example:
- Name
@@ -58,6 +53,7 @@ The Identity parameter specifies the custom file plan property authority that yo
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCategory.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCategory.md
rename to exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md
index f3a73dbc1b..c7b0bab4ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCategory.md
+++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyCategory.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-https: //learn.microsoft.com/powershell/module/exchangepowershell/get-fileplanpropertycategory
-Locale: en-US
-Module Name: ExchangePowerShell
-schema: 2.0.0
+https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertycategory
+applicable: Security & Compliance
title: Get-FilePlanPropertyCategory
+schema: 2.0.0
---
# Get-FilePlanPropertyCategory
@@ -45,9 +43,6 @@ This example returns detailed information about the custom file plan property ca
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the custom file plan property category that you want to view. You can use any value that uniquely identifies the category. For example:
- Name
@@ -58,6 +53,7 @@ The Identity parameter specifies the custom file plan property category that you
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCitation.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCitation.md
rename to exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md
index ade6daa96e..9080e6137a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyCitation.md
+++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyCitation.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/set-fileplanpropertycitation
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/set-fileplanpropertycitation
+applicable: Security & Compliance
title: Get-FilePlanPropertyCitation
+schema: 2.0.0
---
# Get-FilePlanPropertyCitation
@@ -45,9 +43,6 @@ This example returns detailed information about the custom file plan property ci
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the custom file plan property citation that you want to view. You can use any value that uniquely identifies the citation. For example:
- Name
@@ -58,6 +53,7 @@ The Identity parameter specifies the custom file plan property citation that you
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyDepartment.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyDepartment.md
rename to exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md
index 2a66acd2ef..58fc2c7f5e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyDepartment.md
+++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyDepartment.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-fileplanpropertydepartment
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertydepartment
+applicable: Security & Compliance
title: Get-FilePlanPropertyDepartment
+schema: 2.0.0
---
# Get-FilePlanPropertyDepartment
@@ -45,9 +43,6 @@ This example returns detailed information about the custom file plan property de
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the custom file plan property department that you want to view. You can use any value that uniquely identifies the department. For example:
- Name
@@ -58,6 +53,7 @@ The Identity parameter specifies the custom file plan property department that y
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyReferenceId.md
rename to exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md
index b3fa5d4ebb..c1ec2f310a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyReferenceId.md
+++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyReferenceId.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-fileplanpropertyreferenceid
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertyreferenceid
+applicable: Security & Compliance
title: Get-FilePlanPropertyReferenceId
+schema: 2.0.0
---
# Get-FilePlanPropertyReferenceId
@@ -45,9 +43,6 @@ This example returns detailed information about the custom file plan property re
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the custom file plan property reference ID that you want to view. You can use any value that uniquely identifies the reference ID. For example:
- Name
@@ -58,6 +53,7 @@ The Identity parameter specifies the custom file plan property reference ID that
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyStructure.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyStructure.md
rename to exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md
index 5c212bdc85..f2e64f89a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertyStructure.md
+++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertyStructure.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-fileplanpropertystructure
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertystructure
+applicable: Security & Compliance
title: Get-FilePlanPropertyStructure
+schema: 2.0.0
---
# Get-FilePlanPropertyStructure
@@ -38,15 +36,13 @@ This example returns the file plan property structure.
## PARAMETERS
### -IncludeAdditionalInfo
-
-> Applicable: Security & Compliance
-
The IncludeAdditionalInfo switch specifies whether to include additional information in the output of the cmdlet. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertySubCategory.md b/exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertySubCategory.md
rename to exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md
index 04407cdf4d..ed2bc3113e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FilePlanPropertySubCategory.md
+++ b/exchange/exchange-ps/exchange/Get-FilePlanPropertySubCategory.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-fileplanpropertysubcategory
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/get-fileplanpropertysubcategory
+applicable: Security & Compliance
title: Get-FilePlanPropertySubCategory
+schema: 2.0.0
---
# Get-FilePlanPropertySubCategory
@@ -45,9 +43,6 @@ This example returns detailed information about the custom file plan property su
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the custom file plan property subcategory that you want to view. You can use any value that uniquely identifies the subcategory. For example:
- Name
@@ -58,6 +53,7 @@ The Identity parameter specifies the custom file plan property subcategory that
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md b/exchange/exchange-ps/exchange/Get-FocusedInbox.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md
rename to exchange/exchange-ps/exchange/Get-FocusedInbox.md
index 5ffb9ea050..c7b5967c67 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md
+++ b/exchange/exchange-ps/exchange/Get-FocusedInbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.Management-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-focusedinbox
applicable: Exchange Online, Exchange Online Protection
+title: Get-FocusedInbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-focusedinbox
-schema: 2.0.0
-title: Get-FocusedInbox
+ms.reviewer:
---
# Get-FocusedInbox
@@ -44,9 +43,6 @@ This example returns the Focused Inbox configuration for the mailbox of julia@co
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online, Exchange Online Protection
-
{{ Fill UseCustomRouting Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md b/exchange/exchange-ps/exchange/Get-ForeignConnector.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
rename to exchange/exchange-ps/exchange/Get-ForeignConnector.md
index 7abc2d7b28..1d19d0d26f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
+++ b/exchange/exchange-ps/exchange/Get-ForeignConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-foreignconnector
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ForeignConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-foreignconnector
-schema: 2.0.0
-title: Get-ForeignConnector
+ms.reviewer:
---
# Get-ForeignConnector
@@ -49,9 +48,6 @@ This example displays detailed configuration information for the Foreign connect
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Foreign connector that you want to examine. The Identity parameter can take any of the following values for the Foreign connector object:
- GUID
@@ -62,6 +58,7 @@ The Identity parameter specifies the Foreign connector that you want to examine.
Type: ForeignConnectorIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -82,6 +76,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md b/exchange/exchange-ps/exchange/Get-FrontendTransportService.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
rename to exchange/exchange-ps/exchange/Get-FrontendTransportService.md
index 2c21f00765..e768cd1838 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
+++ b/exchange/exchange-ps/exchange/Get-FrontendTransportService.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-frontendtransportservice
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-FrontendTransportService
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-frontendtransportservice
-schema: 2.0.0
-title: Get-FrontendTransportService
+ms.reviewer:
---
# Get-FrontendTransportService
@@ -51,9 +50,6 @@ This example retrieves the detailed configuration information for the Front End
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Exchange server with the Client Access server role installed that you want to view.
You can use any value that uniquely identifies the server. For example:
@@ -67,6 +63,7 @@ You can use any value that uniquely identifies the server. For example:
Type: FrontendTransportServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -76,15 +73,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md b/exchange/exchange-ps/exchange/Get-GlobalAddressList.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
rename to exchange/exchange-ps/exchange/Get-GlobalAddressList.md
index 6725543d75..0a3a6daa60 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
+++ b/exchange/exchange-ps/exchange/Get-GlobalAddressList.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-globaladdresslist
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-GlobalAddressList
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-globaladdresslist
-schema: 2.0.0
-title: Get-GlobalAddressList
+ms.reviewer:
---
# Get-GlobalAddressList
@@ -61,9 +60,6 @@ This example returns detailed information about the GAL named GAL\_AgencyB.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the global address list that you want to view. You can use any value that uniquely identifies the GAL. For example:
- Name
@@ -74,6 +70,7 @@ The Identity parameter specifies the global address list that you want to view.
Type: GlobalAddressListIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -83,15 +80,13 @@ Accept wildcard characters: False
```
### -DefaultOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DefaultOnly switch filters the results so only the default GAL is returned. You don't need to use a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: DefaultOnly
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -101,9 +96,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -112,6 +104,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md b/exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
rename to exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md
index 83d6144720..24e4681b00 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/exchange/Get-GlobalMonitoringOverride.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-globalmonitoringoverride
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-GlobalMonitoringOverride
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-globalmonitoringoverride
-schema: 2.0.0
-title: Get-GlobalMonitoringOverride
+ms.reviewer:
---
# Get-GlobalMonitoringOverride
@@ -48,9 +47,6 @@ This example returns detailed information for the global monitoring overrides th
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -59,6 +55,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md b/exchange/exchange-ps/exchange/Get-Group.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Group.md
rename to exchange/exchange-ps/exchange/Get-Group.md
index dbaaa4b176..b940181519 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
+++ b/exchange/exchange-ps/exchange/Get-Group.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-group
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-Group
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-group
-schema: 2.0.0
-title: Get-Group
+ms.reviewer:
---
# Get-Group
@@ -82,9 +81,6 @@ This example uses the Anr parameter to return all groups that begin with "Mar".
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the group object that you want to view. You can use any value that uniquely identifies the group. For example:
- Name
@@ -96,6 +92,7 @@ The Identity parameter specifies the group object that you want to view. You can
Type: GroupIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: 1
@@ -105,9 +102,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -120,6 +114,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -129,9 +124,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -142,6 +134,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -151,9 +144,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -164,6 +154,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -173,9 +164,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -191,6 +179,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -200,9 +189,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -216,6 +202,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -225,9 +212,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -239,6 +223,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -248,9 +233,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -263,6 +245,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -272,9 +255,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientTypeDetails parameter filters the results by the specified group subtype. Valid values are:
- MailNonUniversalGroup
@@ -291,6 +271,7 @@ You can specify multiple values separated by commas.
Type: RecipientTypeDetails[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -300,15 +281,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -318,9 +297,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -334,6 +310,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md b/exchange/exchange-ps/exchange/Get-HealthReport.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
rename to exchange/exchange-ps/exchange/Get-HealthReport.md
index e95ba742ac..fb4ff840c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
+++ b/exchange/exchange-ps/exchange/Get-HealthReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-healthreport
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-HealthReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-healthreport
-schema: 2.0.0
-title: Get-HealthReport
+ms.reviewer:
---
# Get-HealthReport
@@ -55,9 +54,6 @@ This example retrieves health information for the server named Mailbox01.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -69,6 +65,7 @@ The Identity parameter specifies the Exchange server where you want to run this
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -78,15 +75,13 @@ Accept wildcard characters: False
```
### -GroupSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The GroupSize parameter determines the size of the group to process against for a rollup. The default value is 12.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -96,15 +91,13 @@ Accept wildcard characters: False
```
### -HaImpactingOnly
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The HaImpactingOnly switch filters the results to only the monitors that have HaImpacting set to True. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -114,15 +107,13 @@ Accept wildcard characters: False
```
### -HealthSet
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The HealthSet parameter filters the results by the specified health set. Monitors that are similar or are tied to a component's architecture are grouped to form a health set. You can determine the collection of monitors (and associated probes and responders) in a given health set by using the Get-MonitoringItemIdentity cmdlet.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -132,15 +123,13 @@ Accept wildcard characters: False
```
### -MinimumOnlinePercent
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MinimumOnlinePercent parameter specifies the number of members in the group to be functioning with rollup information Degraded instead of Unhealthy. The default value is 70 percent.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -150,15 +139,13 @@ Accept wildcard characters: False
```
### -RollupGroup
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RollupGroup switch specifies that the health data is rolled up across servers with redundancy limits. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md b/exchange/exchange-ps/exchange/Get-HistoricalSearch.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md
rename to exchange/exchange-ps/exchange/Get-HistoricalSearch.md
index 27051147bd..9aa5b5f171 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md
+++ b/exchange/exchange-ps/exchange/Get-HistoricalSearch.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-historicalsearch
applicable: Exchange Online, Exchange Online Protection
+title: Get-HistoricalSearch
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-historicalsearch
-schema: 2.0.0
-title: Get-HistoricalSearch
+ms.reviewer:
---
# Get-HistoricalSearch
@@ -50,15 +49,13 @@ This example returns detailed information about the historical search that's in
## PARAMETERS
### -JobId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The JobId parameter specifies the GUID identifier of the historical search that you want to view.
```yaml
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md
rename to exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md
index 78c781ef0f..ec353acb7a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-HoldCompliancePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-holdcompliancepolicy
applicable: Security & Compliance
+title: Get-HoldCompliancePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-holdcompliancepolicy
-schema: 2.0.0
-title: Get-HoldCompliancePolicy
+ms.reviewer:
---
# Get-HoldCompliancePolicy
@@ -58,9 +57,6 @@ This example displays detailed information for the policy named "Regulation 123
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the preservation policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -71,6 +67,7 @@ The Identity parameter specifies the preservation policy that you want to view.
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -80,15 +77,13 @@ Accept wildcard characters: False
```
### -DistributionDetail
-
-> Applicable: Security & Compliance
-
The DistributionDetail switch returns detailed policy distribution information in the DistributionResults property. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md b/exchange/exchange-ps/exchange/Get-HoldComplianceRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md
rename to exchange/exchange-ps/exchange/Get-HoldComplianceRule.md
index 6f68eb4b30..898c6c476a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md
+++ b/exchange/exchange-ps/exchange/Get-HoldComplianceRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-holdcompliancerule
applicable: Security & Compliance
+title: Get-HoldComplianceRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-holdcompliancerule
-schema: 2.0.0
-title: Get-HoldComplianceRule
+ms.reviewer:
---
# Get-HoldComplianceRule
@@ -58,9 +57,6 @@ This example displays detailed information for the preservation rule named "30 D
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the preservation rule you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -71,6 +67,7 @@ The Identity parameter specifies the preservation rule you want to view. You can
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -80,9 +77,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter filters the preservation rule results by the associated preservation policy. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -95,6 +89,7 @@ You can use this parameter with the Identity parameter in the same command.
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md
rename to exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md
index 3b9e5bdaac..5c3c8cd5f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-HostedConnectionFilterPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedconnectionfilterpolicy
applicable: Exchange Online, Exchange Online Protection
+title: Get-HostedConnectionFilterPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-hostedconnectionfilterpolicy
-schema: 2.0.0
-title: Get-HostedConnectionFilterPolicy
+ms.reviewer:
---
# Get-HostedConnectionFilterPolicy
@@ -48,9 +47,6 @@ This example returns detailed information about the connection filter policy nam
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the connection filter policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -63,6 +59,7 @@ Typically, you only have one connection filter policy: the default policy named
Type: HostedConnectionFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md b/exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md
rename to exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md
index 3fd2f2b42b..855377d33a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-HostedContentFilterPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedcontentfilterpolicy
applicable: Exchange Online, Exchange Online Protection
+title: Get-HostedContentFilterPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-hostedcontentfilterpolicy
-schema: 2.0.0
-title: Get-HostedContentFilterPolicy
+ms.reviewer:
---
# Get-HostedContentFilterPolicy
@@ -57,9 +56,6 @@ This example shows the allowed and blocked senders and domains in all spam filte
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the spam filter policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -70,6 +66,7 @@ The Identity parameter specifies the spam filter policy that you want to view. Y
Type: HostedContentFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
rename to exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md
index 1f67787900..0531374eab 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/exchange/Get-HostedContentFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedcontentfilterrule
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-HostedContentFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-hostedcontentfilterrule
-schema: 2.0.0
-title: Get-HostedContentFilterRule
+ms.reviewer:
---
# Get-HostedContentFilterRule
@@ -50,9 +49,6 @@ This example retrieves details about the spam filter rule named Contoso Recipien
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the spam filter rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the spam filter rule that you want to view. You
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -72,15 +69,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -90,9 +85,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The State parameter filters the results by the state of the rule. Valid values are:
- Enabled: The command returns only enabled rules.
@@ -102,6 +94,7 @@ The State parameter filters the results by the state of the rule. Valid values a
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md
rename to exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md
index 20ca00576b..1e40b52a4d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedoutboundspamfilterpolicy
applicable: Exchange Online, Exchange Online Protection
+title: Get-HostedOutboundSpamFilterPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-hostedoutboundspamfilterpolicy
-schema: 2.0.0
-title: Get-HostedOutboundSpamFilterPolicy
+ms.reviewer:
---
# Get-HostedOutboundSpamFilterPolicy
@@ -48,9 +47,6 @@ This example returns detailed information about the outbound spam filter policy
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the outbound spam filter policy you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -61,6 +57,7 @@ The Identity parameter specifies the outbound spam filter policy you want to vie
Type: HostedOutboundSpamFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md
rename to exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md
index 2a1d5d73a1..0a620cec54 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/exchange/Get-HostedOutboundSpamFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-hostedoutboundspamfilterrule
applicable: Exchange Online, Exchange Online Protection
+title: Get-HostedOutboundSpamFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-hostedoutboundspamfilterrule
-schema: 2.0.0
-title: Get-HostedOutboundSpamFilterRule
+ms.reviewer:
---
# Get-HostedOutboundSpamFilterRule
@@ -49,9 +48,6 @@ This example returns detailed information for the outbound spam filter rule name
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the outbound spam filter rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the outbound spam filter rule that you want to
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 0
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The State parameter filters the results by enabled or disabled rules. Valid values are:
- Enabled: Only enabled rules are returned.
@@ -83,6 +77,7 @@ The State parameter filters the results by enabled or disabled rules. Valid valu
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md b/exchange/exchange-ps/exchange/Get-HybridConfiguration.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
rename to exchange/exchange-ps/exchange/Get-HybridConfiguration.md
index fd1ebea9b8..426766c54c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-HybridConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-hybridconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-HybridConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-hybridconfiguration
-schema: 2.0.0
-title: Get-HybridConfiguration
+ms.reviewer:
---
# Get-HybridConfiguration
@@ -41,15 +40,13 @@ This example returns detailed information about the hybrid deployment configurat
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md b/exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md
rename to exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md
index b9e16d25d2..4f793be1a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md
+++ b/exchange/exchange-ps/exchange/Get-HybridMailflowDatacenterIPs.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-hybridmailflowdatacenterips
applicable: Exchange Online
+title: Get-HybridMailflowDatacenterIPs
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-hybridmailflowdatacenterips
-schema: 2.0.0
-title: Get-HybridMailflowDatacenterIPs
+ms.reviewer:
---
# Get-HybridMailflowDatacenterIPs
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md b/exchange/exchange-ps/exchange/Get-IPAllowListConfig.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md
rename to exchange/exchange-ps/exchange/Get-IPAllowListConfig.md
index fa783a57cf..0da96065e8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md
+++ b/exchange/exchange-ps/exchange/Get-IPAllowListConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipallowlistconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-IPAllowListConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipallowlistconfig
-schema: 2.0.0
-title: Get-IPAllowListConfig
+ms.reviewer:
---
# Get-IPAllowListConfig
@@ -43,9 +42,6 @@ This example returns detailed information about the IP Allow list configuration
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -54,6 +50,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md b/exchange/exchange-ps/exchange/Get-IPAllowListEntry.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md
rename to exchange/exchange-ps/exchange/Get-IPAllowListEntry.md
index 33954acbcb..7221b9e90b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md
+++ b/exchange/exchange-ps/exchange/Get-IPAllowListEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipallowlistentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-IPAllowListEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipallowlistentry
-schema: 2.0.0
-title: Get-IPAllowListEntry
+ms.reviewer:
---
# Get-IPAllowListEntry
@@ -59,15 +58,13 @@ This example returns an IP Allow list entry in which the specified IP address is
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity integer value of the IP Allow list entry that you want to view. When you add an entry to the IP Allow list, the Identity value is automatically assigned.
```yaml
Type: IPListEntryIdentity
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -77,15 +74,13 @@ Accept wildcard characters: False
```
### -IPAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IPAddress parameter specifies an IP address to view in the IP Allow list entry or entries. For example, if you have an IP Allow list entry that specifies a range of IP addresses from 192.168.0.1 through 192.168.0.20, enter any IP address in the IP Allow list IP address range to return the IP Allow list entry.
```yaml
Type: IPAddress
Parameter Sets: IPAddress
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,9 +106,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -131,6 +121,7 @@ You can't use this parameter to configure other Edge Transport servers remotely.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md b/exchange/exchange-ps/exchange/Get-IPAllowListProvider.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md
rename to exchange/exchange-ps/exchange/Get-IPAllowListProvider.md
index 7cc5d7d182..1d17905936 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md
+++ b/exchange/exchange-ps/exchange/Get-IPAllowListProvider.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipallowlistprovider
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-IPAllowListProvider
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipallowlistprovider
-schema: 2.0.0
-title: Get-IPAllowListProvider
+ms.reviewer:
---
# Get-IPAllowListProvider
@@ -49,9 +48,6 @@ This example returns detailed information for the IP Allow list provider named C
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the IP Allow list provider that you want to view. You can use any value that uniquely identifies the IP Allow list provider. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the IP Allow list provider that you want to vie
Type: IPAllowListProviderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -82,6 +76,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md b/exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md
rename to exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md
index 33845fc425..b56f559df4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md
+++ b/exchange/exchange-ps/exchange/Get-IPAllowListProvidersConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipallowlistprovidersconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-IPAllowListProvidersConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipallowlistprovidersconfig
-schema: 2.0.0
-title: Get-IPAllowListProvidersConfig
+ms.reviewer:
---
# Get-IPAllowListProvidersConfig
@@ -43,9 +42,6 @@ This example returns detailed information about the IP Allow list providers conf
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -54,6 +50,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md b/exchange/exchange-ps/exchange/Get-IPBlockListConfig.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md
rename to exchange/exchange-ps/exchange/Get-IPBlockListConfig.md
index badc1fb114..517988a7ae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md
+++ b/exchange/exchange-ps/exchange/Get-IPBlockListConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipblocklistconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-IPBlockListConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipblocklistconfig
-schema: 2.0.0
-title: Get-IPBlockListConfig
+ms.reviewer:
---
# Get-IPBlockListConfig
@@ -43,9 +42,6 @@ This example returns detailed information about the IP Block list configuration
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -54,6 +50,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md b/exchange/exchange-ps/exchange/Get-IPBlockListEntry.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md
rename to exchange/exchange-ps/exchange/Get-IPBlockListEntry.md
index ac6528eb90..d6a1d41ce8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md
+++ b/exchange/exchange-ps/exchange/Get-IPBlockListEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipblocklistentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-IPBlockListEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipblocklistentry
-schema: 2.0.0
-title: Get-IPBlockListEntry
+ms.reviewer:
---
# Get-IPBlockListEntry
@@ -59,15 +58,13 @@ This example returns machine-generated entries in the IP Block list that are ins
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity integer value of the IP Block list entry that you want to view. When you add an entry to the IP Block list, the Identity value is automatically assigned.
```yaml
Type: IPListEntryIdentity
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -77,15 +74,13 @@ Accept wildcard characters: False
```
### -IPAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IPAddress parameter specifies an IP address to view in the IP Block list entry or entries. For example, if you have an IP Block list entry that specifies a range of IP addresses from 192.168.0.1 through 192.168.0.20, enter any IP address in the IP Block list IP address range to return the IP Block list entry.
```yaml
Type: IPAddress
Parameter Sets: IPAddress
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,9 +106,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -131,6 +121,7 @@ You can't use this parameter to configure other Edge Transport servers remotely.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md b/exchange/exchange-ps/exchange/Get-IPBlockListProvider.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md
rename to exchange/exchange-ps/exchange/Get-IPBlockListProvider.md
index a6befcee10..f8849f592d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md
+++ b/exchange/exchange-ps/exchange/Get-IPBlockListProvider.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipblocklistprovider
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-IPBlockListProvider
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipblocklistprovider
-schema: 2.0.0
-title: Get-IPBlockListProvider
+ms.reviewer:
---
# Get-IPBlockListProvider
@@ -49,9 +48,6 @@ This example returns detailed information for the existing IP Block list provide
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the IP Block list provider that you want to view. You can use any value that uniquely identifies the IP Block list provider. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the IP Block list provider that you want to vie
Type: IPBlockListProviderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -82,6 +76,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md b/exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md
rename to exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md
index f84def95bc..f7bcc606fa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md
+++ b/exchange/exchange-ps/exchange/Get-IPBlockListProvidersConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipblocklistprovidersconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-IPBlockListProvidersConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipblocklistprovidersconfig
-schema: 2.0.0
-title: Get-IPBlockListProvidersConfig
+ms.reviewer:
---
# Get-IPBlockListProvidersConfig
@@ -43,9 +42,6 @@ This example returns detailed information about the IP Block list providers on t
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -54,6 +50,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md b/exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md
rename to exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md
index 95b42a54fc..e8d7109c9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md
+++ b/exchange/exchange-ps/exchange/Get-IPv6StatusForAcceptedDomain.md
@@ -1,12 +1,12 @@
---
+external help file:
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ipv6statusforaccepteddomain
applicable: Exchange Online
+title: Get-IPv6StatusForAcceptedDomain
+schema: 2.0.0
author: chrisda
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ipv6statusforaccepteddomain
-schema: 2.0.0
-title: Get-IPv6StatusForAcceptedDomain
+ms.reviewer:
---
# Get-IPv6StatusForAcceptedDomain
@@ -58,15 +58,13 @@ This example returns the status of IPv6 support for mail sent to contoso.com.
## PARAMETERS
### -Domain
-
-> Applicable: Exchange Online
-
The Domain parameter specifies the accepted domain that you want to view IPv6 status for.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -76,15 +74,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -94,15 +90,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md b/exchange/exchange-ps/exchange/Get-IRMConfiguration.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
rename to exchange/exchange-ps/exchange/Get-IRMConfiguration.md
index dc6a295bf7..377c44454f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-IRMConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-irmconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-IRMConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-irmconfiguration
-schema: 2.0.0
-title: Get-IRMConfiguration
+ms.reviewer:
---
# Get-IRMConfiguration
@@ -43,9 +42,6 @@ This example retrieves the IRM configuration in your organization.
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -54,6 +50,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md b/exchange/exchange-ps/exchange/Get-ImapSettings.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
rename to exchange/exchange-ps/exchange/Get-ImapSettings.md
index 09f01eed05..78a0faa6d4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
+++ b/exchange/exchange-ps/exchange/Get-ImapSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-imapsettings
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ImapSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-imapsettings
-schema: 2.0.0
-title: Get-ImapSettings
+ms.reviewer:
---
# Get-ImapSettings
@@ -42,15 +41,13 @@ This example displays the settings and values of the Microsoft Exchange IMAP4 se
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -60,9 +57,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -76,6 +70,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md b/exchange/exchange-ps/exchange/Get-InboundConnector.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md
rename to exchange/exchange-ps/exchange/Get-InboundConnector.md
index 4b8f165f3a..2447b733ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md
+++ b/exchange/exchange-ps/exchange/Get-InboundConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-inboundconnector
applicable: Exchange Online, Exchange Online Protection
+title: Get-InboundConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-inboundconnector
-schema: 2.0.0
-title: Get-InboundConnector
+ms.reviewer:
---
# Get-InboundConnector
@@ -51,15 +50,13 @@ This example lists all the Inbound connectors configured in your cloud-based org
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the name or GUID of the Inbound connector. If the Identity name contains spaces, enclose the name in quotation marks ("). You can omit the Identity parameter label.
```yaml
Type: InboundConnectorIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md b/exchange/exchange-ps/exchange/Get-InboxRule.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
rename to exchange/exchange-ps/exchange/Get-InboxRule.md
index 59c768d5f7..5ed6b13784 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
+++ b/exchange/exchange-ps/exchange/Get-InboxRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-inboxrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-InboxRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-inboxrule
-schema: 2.0.0
-title: Get-InboxRule
+ms.reviewer:
---
# Get-InboxRule
@@ -60,9 +59,6 @@ This example retrieves the Inbox rule ReceivedLastYear from the mailbox joe@cont
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the Inbox rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -74,6 +70,7 @@ The Identity parameter specifies the Inbox rule that you want to view. You can u
Type: InboxRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -83,15 +80,13 @@ Accept wildcard characters: False
```
### -BypassScopeCheck
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BypassScopeCheck switch specifies whether to bypass the scope check for the user that's running the command. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -101,9 +96,6 @@ Accept wildcard characters: False
```
### -DescriptionTimeFormat
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DescriptionTimeFormat parameter specifies the format for time values in the rule description. For example:
MM/dd/yyyy, where MM is the 2-digit month, dd is the 2-digit day and yyyy is the 4-digit year.
@@ -112,6 +104,7 @@ MM/dd/yyyy, where MM is the 2-digit month, dd is the 2-digit day and yyyy is the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -121,9 +114,6 @@ Accept wildcard characters: False
```
### -DescriptionTimeZone
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DescriptionTimeZone parameter specifies time zone that's used for time values in the rule description.
A valid value for this parameter is a supported time zone key name (for example, "Pacific Standard Time").
@@ -136,6 +126,7 @@ If the value contains spaces, enclose the value in quotation marks ("). The defa
Type: ExTimeZoneValue
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -145,9 +136,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -156,6 +144,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -165,15 +154,13 @@ Accept wildcard characters: False
```
### -IncludeHidden
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeHidden switch specifies whether to include hidden Inbox rules in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -183,9 +170,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -203,6 +187,7 @@ The Mailbox parameter specifies the mailbox that contains the Inbox rule. You ca
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -212,9 +197,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -223,6 +205,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -232,9 +215,6 @@ Accept wildcard characters: False
```
### -SkipCount
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill SkipCount Description }}
@@ -243,6 +223,7 @@ This parameter is available only in the cloud-based service.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -252,9 +233,6 @@ Accept wildcard characters: False
```
### -SweepRules
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The SweepRules switch specifies whether to return only Sweep rules in the results. You don't need to specify a value with this switch.
@@ -265,6 +243,7 @@ Sweep rules run at regular intervals to help keep your Inbox clean.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -274,9 +253,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -285,6 +261,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPoliciesApplicationStatus.md b/exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPoliciesApplicationStatus.md
rename to exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md
index a7e9c553d8..4ba383b667 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPoliciesApplicationStatus.md
+++ b/exchange/exchange-ps/exchange/Get-InformationBarrierPoliciesApplicationStatus.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-informationbarrierpoliciesapplicationstatus
applicable: Security & Compliance
+title: Get-InformationBarrierPoliciesApplicationStatus
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-informationbarrierpoliciesapplicationstatus
-schema: 2.0.0
-title: Get-InformationBarrierPoliciesApplicationStatus
+ms.reviewer:
---
# Get-InformationBarrierPoliciesApplicationStatus
@@ -58,15 +57,13 @@ This example returns all applications of information barrier policies by the Sta
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the information barrier policy application that you want to view. This value is a GUID that's displayed when you run the Start-InformationBarrierPoliciesApplication cmdlet (for example, a0551cee-db3d-4002-9fa0-94358035fdf2). You can also find the Identity value by running the command Get-InformationBarrierPoliciesApplicationStatus -All.
```yaml
Type: PolicyIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -76,9 +73,6 @@ Accept wildcard characters: False
```
### -All
-
-> Applicable: Security & Compliance
-
The All switch specifies whether to include all applications of information barrier policies in the results. You don't need to specify a value with this switch.
If you don't use this switch, the command only returns the most recent policy application.
@@ -87,6 +81,7 @@ If you don't use this switch, the command only returns the most recent policy ap
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPolicy.md
rename to exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md
index 8afc72a88e..32c2276297 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-InformationBarrierPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-informationbarrierpolicy
applicable: Security & Compliance
+title: Get-InformationBarrierPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-informationbarrierpolicy
-schema: 2.0.0
-title: Get-InformationBarrierPolicy
+ms.reviewer:
---
# Get-InformationBarrierPolicy
@@ -58,9 +57,6 @@ This example displays detailed information for the information barrier policy na
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the information barrier policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -73,6 +69,7 @@ You can't use this parameter with the ExOPolicyId parameter.
Type: PolicyIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -ExoPolicyId
-
-> Applicable: Security & Compliance
-
The ExOPolicyId parameter specifies the information barrier policy that you want to view, but using the GUID part of the ExoPolicyId property value from the output of the Get-InformationBarrierRecipientStatus cmdlet.
You can't use this parameter with the Identity parameter.
@@ -93,6 +87,7 @@ You can't use this parameter with the Identity parameter.
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -114,4 +109,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies)
-[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchangepowershell/new-informationbarrierpolicy)
+[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierRecipientStatus.md b/exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierRecipientStatus.md
rename to exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md
index 2d332b51d7..862519808e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InformationBarrierRecipientStatus.md
+++ b/exchange/exchange-ps/exchange/Get-InformationBarrierRecipientStatus.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-informationbarrierrecipientstatus
applicable: Security & Compliance
+title: Get-InformationBarrierRecipientStatus
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-informationbarrierrecipientstatus
-schema: 2.0.0
-title: Get-InformationBarrierRecipientStatus
+ms.reviewer:
---
# Get-InformationBarrierRecipientStatus
@@ -57,9 +56,6 @@ This example returns the information barrier policy relationship for the users m
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the recipient that you want to view the segment and policy assignment information for. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -73,6 +69,7 @@ The Identity parameter specifies the recipient that you want to view the segment
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -Identity2
-
-> Applicable: Security & Compliance
-
The Identity2 parameter specifies an optional second recipient when you want to view the information barrier policy relationship to the first recipient specified by the Identity parameter. You can use any value that uniquely identifies the second recipient. For example:
- Name
@@ -102,6 +96,7 @@ You can only use this parameter with the Identity parameter; you can't use it by
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -125,4 +120,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies)
-[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchangepowershell/new-informationbarrierpolicy)
+[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md b/exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
rename to exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md
index a0fff4f00b..3178fd949a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-IntraOrganizationConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-intraorganizationconfiguration
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-IntraOrganizationConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-intraorganizationconfiguration
-schema: 2.0.0
-title: Get-IntraOrganizationConfiguration
+ms.reviewer:
---
# Get-IntraOrganizationConfiguration
@@ -45,9 +44,6 @@ This example returns the settings of the intra-organization configuration.
## PARAMETERS
### -OrganizationGuid
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The OrganizationGuid parameter specifies the on-premises organization in a hybrid deployment that has multiple on-premises organizations defined. If you don't use the OrganizationGuid parameter for these types of hybrid deployments, the Get-IntraOrganizationConfiguration cmdlet will generate errors. To view the on-premises organization GUID values that are required for this parameter, use the Get-OnPremisesOrganization cmdlet.
@@ -56,6 +52,7 @@ The OrganizationGuid parameter specifies the on-premises organization in a hybri
Type: OnPremisesOrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 2
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md b/exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
rename to exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md
index 9b1bb44334..d07a069726 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/exchange/Get-IntraOrganizationConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-intraorganizationconnector
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-IntraOrganizationConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-intraorganizationconnector
-schema: 2.0.0
-title: Get-IntraOrganizationConnector
+ms.reviewer:
---
# Get-IntraOrganizationConnector
@@ -51,9 +50,6 @@ This example returns details about the Intra-Organization connector named "MainC
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the Intra-Organization connector that you want to view. You can use any value that uniquely identifies the connector. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the Intra-Organization connector that you want
Type: IntraOrganizationConnectorIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -84,6 +78,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md b/exchange/exchange-ps/exchange/Get-JournalRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
rename to exchange/exchange-ps/exchange/Get-JournalRule.md
index c1bc9f9203..68b259f8f9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
+++ b/exchange/exchange-ps/exchange/Get-JournalRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-journalrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-JournalRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-journalrule
-schema: 2.0.0
-title: Get-JournalRule
+ms.reviewer:
---
# Get-JournalRule
@@ -51,15 +50,13 @@ This example retrieves the specific journal rule Brokerage Communications and pi
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the rule you want to view. Enter either the name or the GUID of the journal rule. You can omit the parameter label.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -80,6 +74,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Label.md b/exchange/exchange-ps/exchange/Get-Label.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Label.md
rename to exchange/exchange-ps/exchange/Get-Label.md
index 7f2a6250ac..b2cf3b4226 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Label.md
+++ b/exchange/exchange-ps/exchange/Get-Label.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-label
applicable: Security & Compliance
+title: Get-Label
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-label
-schema: 2.0.0
-title: Get-Label
+ms.reviewer:
---
# Get-Label
@@ -51,9 +50,6 @@ This example returns detailed information for the sensitivity label named Engine
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the sensitivity label that you want to view. You can use any value that uniquely identifies the label. For example:
- Name
@@ -64,6 +60,7 @@ The Identity parameter specifies the sensitivity label that you want to view. Yo
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -IncludeDetailedLabelActions
-
-> Applicable: Security & Compliance
-
The IncludeDetailedLabelActions parameter specifies whether to expand label actions into properties for better readability. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -91,15 +86,13 @@ Accept wildcard characters: False
```
### -SkipValidations
-
-> Applicable: Security & Compliance
-
{{ Fill SkipValidations Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -109,15 +102,13 @@ Accept wildcard characters: False
```
### -ValidateContentTypeRemoval
-
-> Applicable: Security & Compliance
-
{{ Fill ValidateContentTypeRemoval Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LabelPolicy.md b/exchange/exchange-ps/exchange/Get-LabelPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-LabelPolicy.md
rename to exchange/exchange-ps/exchange/Get-LabelPolicy.md
index 758f9dee87..7a90fbaa71 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-LabelPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-LabelPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-labelpolicy
applicable: Security & Compliance
+title: Get-LabelPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-labelpolicy
-schema: 2.0.0
-title: Get-LabelPolicy
+ms.reviewer:
---
# Get-LabelPolicy
@@ -49,9 +48,6 @@ This example returns detailed information for the policy named Engineering Group
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the sensitivity label policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the sensitivity label policy that you want to v
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -ForceValidate
-
-> Applicable: Security & Compliance
-
{{ Fill ForceValidate Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md b/exchange/exchange-ps/exchange/Get-LinkedUser.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md
rename to exchange/exchange-ps/exchange/Get-LinkedUser.md
index a4e3fe0a73..7407a5f12b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md
+++ b/exchange/exchange-ps/exchange/Get-LinkedUser.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-linkeduser
applicable: Exchange Online
+title: Get-LinkedUser
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-linkeduser
-schema: 2.0.0
-title: Get-LinkedUser
+ms.reviewer:
---
# Get-LinkedUser
@@ -63,9 +62,6 @@ This example returns a detailed information for the linked for the user laura@co
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the linked user that you want to view. You can use any value that uniquely identifies the linked user. For example:
- Name
@@ -77,6 +73,7 @@ The Identity parameter specifies the linked user that you want to view. You can
Type: UserIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -86,9 +83,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Online
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -101,6 +95,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -128,6 +120,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -137,15 +130,13 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -155,15 +146,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -173,9 +162,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -193,6 +179,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md b/exchange/exchange-ps/exchange/Get-LogonStatistics.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
rename to exchange/exchange-ps/exchange/Get-LogonStatistics.md
index dc9385ddb7..bfdee00794 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-LogonStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-logonstatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-LogonStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-logonstatistics
-schema: 2.0.0
-title: Get-LogonStatistics
+ms.reviewer:
---
# Get-LogonStatistics
@@ -61,9 +60,6 @@ This example returns logon statistics for all users connected to the server Serv
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox to get logon statistics from. You can use one of the following values to identify the mailbox:
- GUID
@@ -82,6 +78,7 @@ You can't use this parameter with the Database or Server parameters.
Type: LogonableObjectIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -91,9 +88,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Database parameter specifies the mailbox database to get logon statistics from (all mailboxes in the specified database). You can use any value that uniquely identifies the mailbox database. For example:
- Name
@@ -108,6 +102,7 @@ You can't use this parameter with the Identity or Server parameters.
Type: DatabaseIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -117,9 +112,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Mailbox server to get logon statistics from (all mailboxes on all databases, including recovery databases, on the specified server). You can use one of the following values to identify the server:
- Fully qualified domain name (FQDN)
@@ -133,6 +125,7 @@ You can't use this parameter with the Database or Identity parameters.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -142,15 +135,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md
rename to exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md
index fa455671a6..c7992e4955 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-m365dataatrestencryptionpolicy
applicable: Exchange Online, Exchange Online Protection
+title: Get-M365DataAtRestEncryptionPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-m365dataatrestencryptionpolicy
-schema: 2.0.0
-title: Get-M365DataAtRestEncryptionPolicy
+ms.reviewer:
---
# Get-M365DataAtRestEncryptionPolicy
@@ -55,9 +54,6 @@ This example returns detailed information about the policy named Contoso Corpora
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the Microsoft 365 data-at-rest encryption policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -68,6 +64,7 @@ The Identity parameter specifies the Microsoft 365 data-at-rest encryption polic
Type: DataEncryptionPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 0
@@ -77,9 +74,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -89,6 +83,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -116,15 +109,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md
rename to exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md
index b096ce31ee..486e093215 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md
+++ b/exchange/exchange-ps/exchange/Get-M365DataAtRestEncryptionPolicyAssignment.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-m365dataatrestencryptionpolicyassignment
applicable: Exchange Online
+title: Get-M365DataAtRestEncryptionPolicyAssignment
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-m365dataatrestencryptionpolicyassignment
-schema: 2.0.0
-title: Get-M365DataAtRestEncryptionPolicyAssignment
+ms.reviewer:
---
# Get-M365DataAtRestEncryptionPolicyAssignment
@@ -46,8 +45,6 @@ Get-M365DataAtRestEncryptionPolicyAssignment | Format-List
This example returns detailed information for all Microsoft 365 data-at-rest encryption policy assignments.
-## PARAMETERS
-
### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md b/exchange/exchange-ps/exchange/Get-MailContact.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md
rename to exchange/exchange-ps/exchange/Get-MailContact.md
index ae2917a68a..aa00b27a06 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md
+++ b/exchange/exchange-ps/exchange/Get-MailContact.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailcontact
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-MailContact
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailcontact
-schema: 2.0.0
-title: Get-MailContact
+ms.reviewer:
---
# Get-MailContact
@@ -75,9 +74,6 @@ This example retrieves detailed information for the mail contact named Arlene.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the mail contact that you want to view. You can use any value that uniquely identifies the mail contact. For example:
- Name
@@ -91,6 +87,7 @@ The Identity parameter specifies the mail contact that you want to view. You can
Type: MailContactIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -100,9 +97,6 @@ Accept wildcard characters: False
```
### -ANR
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -115,6 +109,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -124,9 +119,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -137,6 +129,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -146,9 +139,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -157,6 +147,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -166,9 +157,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -184,6 +172,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -193,9 +182,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -209,6 +195,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -218,9 +205,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -232,6 +216,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -241,9 +226,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -256,6 +238,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -265,9 +248,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RecipientTypeDetails parameter filters the results by the specified mail contact subtype. Valid values are:
- MailContact
@@ -279,6 +259,7 @@ You can specify multiple values separated by commas.
Type: RecipientTypeDetails[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -288,15 +269,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -306,9 +285,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -323,6 +299,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md b/exchange/exchange-ps/exchange/Get-MailDetailATPReport.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md
rename to exchange/exchange-ps/exchange/Get-MailDetailATPReport.md
index 0cd35bc4ee..2894c21ea7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailDetailATPReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetailatpreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-MailDetailATPReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-maildetailatpreport
-schema: 2.0.0
-title: Get-MailDetailATPReport
+ms.reviewer:
---
# Get-MailDetailATPReport
@@ -79,15 +78,13 @@ This example returns the actions for the last 10 days in July, 2018. (Note: Cust
## PARAMETERS
### -DataSource
-
-> Applicable: Exchange Online, Exchange Online Protection
-
{{ Fill DataSource Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -97,9 +94,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -112,6 +106,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -121,15 +116,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -139,9 +132,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only. If you enter the date, enclose the value in quotation marks ("), for example, "09/01/2018".
@@ -150,6 +140,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -159,9 +150,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EventType parameter filters the report by the event type. Valid values are:
- Advanced filter
@@ -193,6 +181,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -202,9 +191,6 @@ Accept wildcard characters: False
```
### -MalwareName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MalwareName parameter filters the results by malware payload. Valid values are:
- Excel
@@ -221,6 +207,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -230,15 +217,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -248,9 +233,6 @@ Accept wildcard characters: False
```
### -MessageTraceId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1).
You can specify multiple values separated by commas.
@@ -267,6 +249,7 @@ The MessageTraceId value is also available in the output of the following cmdlet
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -276,15 +259,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -294,15 +275,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -312,15 +291,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -330,15 +307,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -348,15 +323,13 @@ Accept wildcard characters: False
```
### -SenderAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -366,9 +339,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018".
@@ -377,6 +347,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md b/exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md
rename to exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md
index 2043cdee62..213354eae3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailDetailDlpPolicyReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetaildlppolicyreport
applicable: Exchange Online
+title: Get-MailDetailDlpPolicyReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-maildetaildlppolicyreport
-schema: 2.0.0
-title: Get-MailDetailDlpPolicyReport
+ms.reviewer:
---
# Get-MailDetailDlpPolicyReport
@@ -55,9 +54,6 @@ This example retrieves the details of messages sent by john@contoso.com that mat
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -66,6 +62,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -89,6 +83,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -DlpPolicy
-
-> Applicable: Exchange Online
-
The DlpPolicy parameter filters the report by the name of the DLP policy. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -116,15 +109,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -134,9 +125,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -145,6 +133,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -154,9 +143,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online
-
The EventType parameter filters the report by the event type. Valid values are:
- DLPActionHits
@@ -173,6 +159,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -182,15 +169,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -200,9 +185,6 @@ Accept wildcard characters: False
```
### -MessageTraceId
-
-> Applicable: Exchange Online
-
The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1).
You can specify multiple values separated by commas.
@@ -219,6 +201,7 @@ The MessageTraceId value is also available in the output of the following cmdlet
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -228,15 +211,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -246,15 +227,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -264,15 +243,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -282,15 +259,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -300,15 +275,13 @@ Accept wildcard characters: False
```
### -SenderAddress
-
-> Applicable: Exchange Online
-
The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -318,9 +291,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -329,6 +299,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -338,15 +309,13 @@ Accept wildcard characters: False
```
### -TransportRule
-
-> Applicable: Exchange Online
-
The TransportRule parameter filters the report by the name of the transport rule. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md b/exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md
rename to exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md
index 3f2175e653..62ff5f0f00 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailDetailEncryptionReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetailencryptionreport
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-MailDetailEncryptionReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-maildetailencryptionreport
-schema: 2.0.0
-title: Get-MailDetailEncryptionReport
+ms.reviewer:
---
# Get-MailDetailEncryptionReport
@@ -68,15 +67,13 @@ This example retrieves encryption details for messages between December 13, 2021
## PARAMETERS
### -Organization
-
-> Applicable: Security & Compliance
-
{{ Fill Organization Description }}
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -86,15 +83,13 @@ Accept wildcard characters: False
```
### -AggregateBy
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The AggregateBy parameter specifies the reporting period. Valid values are Hour, Day, or Summary. The default value is Day.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -104,9 +99,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -118,6 +110,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -127,15 +120,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -145,9 +136,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -156,6 +144,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -165,9 +154,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EventType parameter filters the report by the event type. Valid values are:
- EncryptionManual
@@ -181,6 +167,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -190,9 +177,6 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
You can specify multiple values separated by commas.
@@ -201,6 +185,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -210,9 +195,6 @@ Accept wildcard characters: False
```
### -MessageTraceId
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1).
You can specify multiple values separated by commas.
@@ -229,6 +211,7 @@ The MessageTraceId value is also available in the output of the following cmdlet
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -238,15 +221,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -256,15 +237,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -274,15 +253,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -292,9 +269,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -303,6 +277,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md b/exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md
rename to exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md
index 7ca077624a..ca463e1112 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailDetailTransportRuleReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-maildetailtransportrulereport
applicable: Exchange Online, Exchange Online Protection
+title: Get-MailDetailTransportRuleReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-maildetailtransportrulereport
-schema: 2.0.0
-title: Get-MailDetailTransportRuleReport
+ms.reviewer:
---
# Get-MailDetailTransportRuleReport
@@ -54,9 +53,6 @@ This example retrieves the details of messages sent by john@contoso.com that mat
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -65,6 +61,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -88,6 +82,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -126,6 +116,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -135,9 +126,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EventType parameter filters the report by the event type. Valid values are:
- EncryptionManual
@@ -153,6 +141,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -162,15 +151,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -180,9 +167,6 @@ Accept wildcard characters: False
```
### -MessageTraceId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1).
You can specify multiple values separated by commas.
@@ -199,6 +183,7 @@ The MessageTraceId value is also available in the output of the following cmdlet
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -208,15 +193,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -226,15 +209,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -244,15 +225,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -262,15 +241,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -280,15 +257,13 @@ Accept wildcard characters: False
```
### -SenderAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -298,9 +273,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -311,6 +283,7 @@ Although you can enter a date up to 30 days old, only data from the last 10 days
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -320,15 +293,13 @@ Accept wildcard characters: False
```
### -TransportRule
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The TransportRule parameter filters the report by the name of the transport rule. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md b/exchange/exchange-ps/exchange/Get-MailFilterListReport.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md
rename to exchange/exchange-ps/exchange/Get-MailFilterListReport.md
index fca22fa5d4..4fe3fbe363 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailFilterListReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailfilterlistreport
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-MailFilterListReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailfilterlistreport
-schema: 2.0.0
-title: Get-MailFilterListReport
+ms.reviewer:
---
# Get-MailFilterListReport
@@ -45,15 +44,13 @@ This example uses the Get-MailFilterListReport cmdlet to return information abou
## PARAMETERS
### -Domain
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -63,9 +60,6 @@ Accept wildcard characters: False
```
### -Expression
-
-> Applicable: Security & Compliance
-
This parameter is available only in Security & Compliance PowerShell.
This parameter is reserved for internal Microsoft use.
@@ -74,6 +68,7 @@ This parameter is reserved for internal Microsoft use.
Type: Expression
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -83,15 +78,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -101,9 +94,6 @@ Accept wildcard characters: False
```
### -SelectionTarget
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The SelectionTarget parameter filters the report information by object type. Valid values are:
- Actions
@@ -118,6 +108,7 @@ The SelectionTarget parameter filters the report information by object type. Val
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md b/exchange/exchange-ps/exchange/Get-MailPublicFolder.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md
rename to exchange/exchange-ps/exchange/Get-MailPublicFolder.md
index 0ff82748fe..eea8f2f7e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md
+++ b/exchange/exchange-ps/exchange/Get-MailPublicFolder.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailpublicfolder
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailPublicFolder
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailpublicfolder
-schema: 2.0.0
-title: Get-MailPublicFolder
+ms.reviewer:
---
# Get-MailPublicFolder
@@ -78,9 +77,6 @@ This example returns all mail-enabled public folders that begin with the word Ma
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder.
You can omit the parameter label so that only the public folder name or GUID is supplied.
@@ -89,6 +85,7 @@ You can omit the parameter label so that only the public folder name or GUID is
Type: MailPublicFolderIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -98,9 +95,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -113,6 +107,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -122,9 +117,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -133,6 +125,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -142,9 +135,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -153,6 +143,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -162,9 +153,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -180,6 +168,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -189,9 +178,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -203,6 +189,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -212,9 +199,6 @@ Accept wildcard characters: False
```
### -IncludeGrantSendOnBehalfToWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeGrantSendOnBehalfToWithDisplayNames Description }}
@@ -223,6 +207,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -232,9 +217,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -247,6 +229,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -256,15 +239,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -274,9 +255,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example:
@@ -290,6 +268,7 @@ The Server parameter filters the results by the specified Exchange server. You c
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -299,9 +278,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -317,6 +293,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md b/exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md
rename to exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md
index 318fbbbe60..f846e08198 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailTrafficATPReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailtrafficatpreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-MailTrafficATPReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailtrafficatpreport
-schema: 2.0.0
-title: Get-MailTrafficATPReport
+ms.reviewer:
---
# Get-MailTrafficATPReport
@@ -74,9 +73,6 @@ This example retrieves the statistics for outgoing messages on December 25, 2021
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -85,6 +81,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -94,15 +91,13 @@ Accept wildcard characters: False
```
### -AggregateBy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AggregateBy parameter specifies the reporting period. Valid values are Hour, Day, or Summary. The default value is Day.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -112,9 +107,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -127,6 +119,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -136,15 +129,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -154,9 +145,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end of the date range in Coordinated Universal Time (UTC).
To specify a date/time value for this parameter, use either of the following options:
@@ -170,6 +158,7 @@ If you use this parameter, you also need to use the StartDate parameter.
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -179,9 +168,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EventType parameter filters the report by the event type. Valid values are:
- Advanced filter
@@ -213,6 +199,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -222,15 +209,13 @@ Accept wildcard characters: False
```
### -NumberOfRows
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The NumberOfRows parameter specifies the number of rows to return in the report. The maximum value is 10000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -240,15 +225,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -258,15 +241,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -276,15 +257,13 @@ Accept wildcard characters: False
```
### -PivotBy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
{{ Fill PivotBy Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -294,15 +273,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -312,9 +289,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start of the date range in Coordinated Universal Time (UTC).
To specify a date/time value for this parameter, use either of the following options:
@@ -328,6 +302,7 @@ If you use this parameter, you also need to use the EndDate parameter.
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -337,9 +312,6 @@ Accept wildcard characters: False
```
### -SummarizeBy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SummarizeBy parameter returns totals based on the values you specify. If your report filters data using any of the values accepted by this parameter, you can use the SummarizeBy parameter to summarize the results based on those values. To decrease the number of rows returned in the report, consider using the SummarizeBy parameter. Summarizing reduces the amount of data that's retrieved for the report and delivers the report faster. For example, instead of seeing each instance of a specific value of EventType on an individual row in the report, you can use the SummarizeBy parameter to see the total number of instances of that value of EventType on one row in the report.
For this cmdlet, valid values are:
@@ -355,6 +327,7 @@ You can specify multiple values separated by commas. When you specify the values
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -364,15 +337,13 @@ Accept wildcard characters: False
```
### -ThreatClassification
-
-> Applicable: Exchange Online, Exchange Online Protection
-
{{ Fill ThreatClassification Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md b/exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md
rename to exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md
index e864108d17..8fe274f754 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailTrafficEncryptionReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailtrafficencryptionreport
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-MailTrafficEncryptionReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailtrafficencryptionreport
-schema: 2.0.0
-title: Get-MailTrafficEncryptionReport
+ms.reviewer:
---
# Get-MailTrafficEncryptionReport
@@ -61,9 +60,6 @@ This example retrieves encryption information for incoming messages between Dece
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -72,6 +68,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -81,15 +78,13 @@ Accept wildcard characters: False
```
### -AggregateBy
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The AggregateBy parameter specifies the reporting period. Valid values are Hour, Day, or Summary. The default value is Day.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -99,9 +94,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -113,6 +105,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -122,15 +115,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -140,9 +131,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -151,6 +139,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -160,9 +149,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EventType parameter filters the report by the event type. Valid values are:
- EncryptionManual
@@ -176,6 +162,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -185,15 +172,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -203,15 +188,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -221,15 +204,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -239,9 +220,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -250,6 +228,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -259,9 +238,6 @@ Accept wildcard characters: False
```
### -SummarizeBy
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The SummarizeBy parameter returns totals based on the values you specify. If your report filters data using any of the values accepted by this parameter, you can use the SummarizeBy parameter to summarize the results based on those values. To decrease the number of rows returned in the report, consider using the SummarizeBy parameter. Summarizing reduces the amount of data that's retrieved for the report and delivers the report faster. For example, instead of seeing each instance of a specific value of EventType on an individual row in the report, you can use the SummarizeBy parameter to see the total number of instances of that value of EventType on one row in the report.
For this cmdlet, valid values are:
@@ -276,6 +252,7 @@ You can specify multiple values separated by commas. When you specify the values
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md b/exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md
rename to exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md
index 78abc412a0..f1ab603a7f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailTrafficPolicyReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailtrafficpolicyreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-MailTrafficPolicyReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailtrafficpolicyreport
-schema: 2.0.0
-title: Get-MailTrafficPolicyReport
+ms.reviewer:
---
# Get-MailTrafficPolicyReport
@@ -77,9 +76,6 @@ This example is similar to the previous example, but now the results are summari
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -88,6 +84,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -97,15 +94,13 @@ Accept wildcard characters: False
```
### -AggregateBy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AggregateBy parameter specifies the reporting period. Valid values are Hour, Day, or Summary. The default value is Day.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -115,9 +110,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -129,6 +121,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -138,15 +131,13 @@ Accept wildcard characters: False
```
### -DlpPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The DlpPolicy parameter filters the report by the name of the DLP policy. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -156,15 +147,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -174,9 +163,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -185,6 +171,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -194,9 +181,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EventType parameter filters the report by the event type. Valid values are:
- DLPActionHits
@@ -215,6 +199,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -224,15 +209,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -242,15 +225,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -260,15 +241,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -278,9 +257,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -289,6 +265,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -298,9 +275,6 @@ Accept wildcard characters: False
```
### -SummarizeBy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SummarizeBy parameter returns totals based on the values you specify. If your report filters data using any of the values accepted by this parameter, you can use the SummarizeBy parameter to summarize the results based on those values. To decrease the number of rows returned in the report, consider using the SummarizeBy parameter. Summarizing reduces the amount of data that's retrieved for the report, and delivers the report faster. For example, instead of seeing each instance of a specific value of EventType on an individual row in the report, you can use the SummarizeBy parameter to see the total number of instances of that value of EventType on one row in the report.
For this cmdlet, valid values are:
@@ -318,6 +292,7 @@ You can specify multiple values separated by commas. When you specify the values
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -327,15 +302,13 @@ Accept wildcard characters: False
```
### -TransportRule
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The TransportRule parameter filters the report by the name of the transport rule. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md b/exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md
rename to exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md
index 05ad814da1..5ef4d9692a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailTrafficSummaryReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailtrafficsummaryreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-MailTrafficSummaryReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailtrafficsummaryreport
-schema: 2.0.0
-title: Get-MailTrafficSummaryReport
+ms.reviewer:
---
# Get-MailTrafficSummaryReport
@@ -55,9 +54,6 @@ This example shows the top spam recipient statistics between June 13, 2015 and J
## PARAMETERS
### -Category
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Category parameter filters the report by category. Valid values are:
- InboundDLPHits
@@ -88,6 +84,7 @@ The Category parameter filters the report by category. Valid values are:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -97,15 +94,13 @@ Accept wildcard characters: False
```
### -DlpPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The DlpPolicy parameter filters the report by the name of the data loss prevention (DLP) policy. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -115,15 +110,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Domain parameter filters the results by an accepted domain in the cloud-based organization. You can specify multiple domain values separated by commas, or the value All.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -133,9 +126,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -144,6 +134,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -153,15 +144,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -171,15 +160,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -189,15 +176,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -207,9 +192,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -218,6 +200,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -227,15 +210,13 @@ Accept wildcard characters: False
```
### -TransportRule
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The TransportRule parameter filters the report by the name of the transport rule. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md b/exchange/exchange-ps/exchange/Get-MailUser.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md
rename to exchange/exchange-ps/exchange/Get-MailUser.md
index 7e8cd7aefb..82f050e5ea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md
+++ b/exchange/exchange-ps/exchange/Get-MailUser.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailuser
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-MailUser
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailuser
-schema: 2.0.0
-title: Get-MailUser
+ms.reviewer:
---
# Get-MailUser
@@ -100,9 +99,6 @@ This example returns detailed information for the mail user named Ed.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the mail user that you want to view. You can use any value that uniquely identifies the mail user. For example:
- Name
@@ -116,6 +112,7 @@ The Identity parameter specifies the mail user that you want to view. You can us
Type: MailUserIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -125,9 +122,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -140,6 +134,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -149,9 +144,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -162,6 +154,7 @@ This parameter requires the creation and passing of a credential object. This cr
Type: PSCredential
Parameter Sets: AnrSet, Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -171,9 +164,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -182,6 +172,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: AnrSet, Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -191,9 +182,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -209,6 +197,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -218,9 +207,6 @@ Accept wildcard characters: False
```
### -HVEAccount
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The HVEAccount switch specifies that this mail user account is specifically used for the [High volume email service](https://learn.microsoft.com/exchange/mail-flow-best-practices/high-volume-mails-m365). You don't need to specify a value with this switch.
@@ -229,6 +215,7 @@ The HVEAccount switch specifies that this mail user account is specifically used
Type: SwitchParameter
Parameter Sets: HVEAccount
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Position: Named
Default value: None
@@ -238,9 +225,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -254,6 +238,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: AnrSet, Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -263,9 +248,6 @@ Accept wildcard characters: False
```
### -LOBAppAccount
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -274,6 +256,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: LOBAppAccount
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -283,9 +266,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -297,6 +277,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -306,9 +287,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -321,6 +299,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: AnrSet, Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -330,15 +309,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -348,9 +325,6 @@ Accept wildcard characters: False
```
### -SharedWithMailUser
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
{{ Fill SharedWithMailUser Description }}
@@ -359,6 +333,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: AnrSet, Identity
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -368,9 +343,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -386,6 +358,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -395,9 +368,6 @@ Accept wildcard characters: False
```
### -SoftDeletedMailUser
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The SoftDeletedMailUser switch specifies whether to include soft-deleted mail users in the results. You don't need to specify a value with this switch.
@@ -408,6 +378,7 @@ Soft-deleted mail users are deleted mail users that are still recoverable.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md b/exchange/exchange-ps/exchange/Get-Mailbox.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
rename to exchange/exchange-ps/exchange/Get-Mailbox.md
index 1d1068f22f..cae3773fe1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
+++ b/exchange/exchange-ps/exchange/Get-Mailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-Mailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailbox
-schema: 2.0.0
-title: Get-Mailbox
+ms.reviewer:
---
# Get-Mailbox
@@ -210,9 +209,6 @@ This example returns information about the remote archive mailbox for the user e
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -232,6 +228,7 @@ You can't use this parameter with the Anr, Database, MailboxPlan or Server param
Type: MailboxIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -241,9 +238,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -256,6 +250,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -265,9 +260,6 @@ Accept wildcard characters: False
```
### -Arbitration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Arbitration switch specifies whether to return only arbitration mailboxes in the results. You don't need to specify a value with this switch.
@@ -280,6 +272,7 @@ To return arbitration mailboxes that are used to store audit log settings or dat
Type: SwitchParameter
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -289,15 +282,13 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Archive switch specifies whether to return only mailboxes that have an archive enabled in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -307,9 +298,6 @@ Accept wildcard characters: False
```
### -AuditLog
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The AuditLog switch specifies whether to return only audit log mailboxes in the results. You don't need to specify a value with this switch.
@@ -322,6 +310,7 @@ To return other types of arbitration mailboxes, don't use this switch. Instead,
Type: SwitchParameter
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -331,9 +320,6 @@ Accept wildcard characters: False
```
### -AuxAuditLog
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The AuxAuditLog switch specifies whether to return only auxiliary audit log mailboxes in the results. You don't need to specify a value with this switch.
@@ -346,6 +332,7 @@ To return other types of arbitration mailboxes, don't use this switch. Instead,
Type: SwitchParameter
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -355,9 +342,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -368,6 +352,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -377,9 +362,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Database parameter filters the results by mailbox database. When you use this parameter, only mailboxes on the specified database are included in the results. You can any value that uniquely identifies the database. For example:
@@ -394,6 +376,7 @@ You can't use this parameter with the Anr, Identity, or Server parameters.
Type: DatabaseIdParameter
Parameter Sets: DatabaseSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -403,9 +386,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -414,6 +394,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -423,9 +404,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -441,6 +419,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -450,15 +429,13 @@ Accept wildcard characters: False
```
### -GroupMailbox
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The GroupMailbox switch specifies whether to return only Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -468,9 +445,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -484,6 +458,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -493,9 +468,6 @@ Accept wildcard characters: False
```
### -InactiveMailboxOnly
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The InactiveMailboxOnly switch specifies whether to return only inactive mailboxes in the results. You don't need to specify a value with this switch.
@@ -508,6 +480,7 @@ To include active and inactive mailboxes in the results, don't use this switch.
Type: SwitchParameter
Parameter Sets: AnrSet, Identity, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -517,9 +490,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeAcceptMessagesOnlyFromDLMembersWithDisplayNames Description }}
@@ -528,6 +498,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, AnrSet, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -537,9 +508,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames Description }}
@@ -548,6 +516,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, AnrSet, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -557,9 +526,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeAcceptMessagesOnlyFromWithDisplayNames Description }}
@@ -568,6 +534,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, AnrSet, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -577,9 +544,6 @@ Accept wildcard characters: False
```
### -IncludeEmailAddressDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeEmailAddressDisplayNames Description }}
@@ -588,6 +552,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, AnrSet, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -597,9 +562,6 @@ Accept wildcard characters: False
```
### -IncludeForwardingAddressWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeForwardingAddressWithDisplayNames Description }}
@@ -608,6 +570,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, AnrSet, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -617,9 +580,6 @@ Accept wildcard characters: False
```
### -IncludeGrantSendOnBehalfToWithDisplayNames
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeGrantSendOnBehalfToWithDisplayNames Description }}
@@ -628,6 +588,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, AnrSet, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -637,9 +598,6 @@ Accept wildcard characters: False
```
### -IncludeInactiveMailbox
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeInactiveMailbox switch specifies whether to include inactive mailboxes in the results. You don't need to specify a value with this switch.
@@ -652,6 +610,7 @@ To return only inactive mailboxes in the results, don't use this switch. Instead
Type: SwitchParameter
Parameter Sets: AnrSet, Identity, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -661,9 +620,6 @@ Accept wildcard characters: False
```
### -MailboxPlan
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The MailboxPlan parameter filters the results by mailbox plan. When you use this parameter, only mailboxes that are assigned the specified mailbox plan are returned in the results. You can use any value that uniquely identifies the mailbox plan. For example:
@@ -682,6 +638,7 @@ You can't use this parameter with the Anr or Identity parameters.
Type: MailboxPlanIdParameter
Parameter Sets: MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -691,15 +648,13 @@ Accept wildcard characters: False
```
### -Migration
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Migration switch specifies whether to return only migration mailboxes in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -709,9 +664,6 @@ Accept wildcard characters: False
```
### -Monitoring
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Monitoring switch specifies whether to return only monitoring mailboxes in the results. You don't need to specify a value with this switch.
@@ -722,6 +674,7 @@ Monitoring mailboxes are associated with managed availability and the Exchange H
Type: SwitchParameter
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -731,9 +684,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -745,6 +695,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -754,9 +705,6 @@ Accept wildcard characters: False
```
### -PublicFolder
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The PublicFolder switch specifies whether to return only public folder mailboxes in the results. You don't need to specify a value with this switch.
Public folder mailboxes are specially designed mailboxes that store the hierarchy and content of public folders.
@@ -765,6 +713,7 @@ Public folder mailboxes are specially designed mailboxes that store the hierarch
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -774,9 +723,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -789,6 +735,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -798,9 +745,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RecipientTypeDetails parameter filters the results by the specified mailbox subtype. Valid values are:
- DiscoveryMailbox
@@ -821,6 +765,7 @@ You can specify multiple values separated by commas.
Type: RecipientTypeDetails[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -830,9 +775,6 @@ Accept wildcard characters: False
```
### -RemoteArchive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RemoteArchive switch specifies whether to return only remote archive mailboxes in the results. You don't need to specify a value with this switch.
@@ -843,6 +785,7 @@ Remote archive mailboxes are archive mailboxes in the cloud-based service that a
Type: SwitchParameter
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -852,15 +795,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -870,9 +811,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Server parameter filters the results by Exchange server. When you use this parameter, only mailboxes on the specified Exchange server are included in the results.
@@ -894,6 +832,7 @@ The ServerName and ServerLegacyDN properties for a mailbox may not be updated im
Type: ServerIdParameter
Parameter Sets: ServerSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -903,9 +842,6 @@ Accept wildcard characters: False
```
### -SoftDeletedMailbox
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The SoftDeletedMailbox switch specifies whether to return only soft-deleted mailboxes in the results. You don't need to specify a value with this switch.
@@ -916,6 +852,7 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
Type: SwitchParameter
Parameter Sets: AnrSet, Identity, MailboxPlanSet
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -925,9 +862,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -944,6 +878,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -953,9 +888,6 @@ Accept wildcard characters: False
```
### -SupervisoryReviewPolicy
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -964,6 +896,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: AnrSet, DatabaseSet, Identity, ServerSet
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md
rename to exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md
index 6085bdb0ae..52e699b66f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxAuditBypassAssociation.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxauditbypassassociation
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxAuditBypassAssociation
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxauditbypassassociation
-schema: 2.0.0
-title: Get-MailboxAuditBypassAssociation
+ms.reviewer:
---
# Get-MailboxAuditBypassAssociation
@@ -15,7 +14,7 @@ title: Get-MailboxAuditBypassAssociation
## SYNOPSIS
This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
-Use the Get-MailboxAuditBypassAssociation cmdlet to retrieve information about the AuditBypassEnabled property value for user accounts (on-premises Exchange and the cloud) and computer accounts (on-premises Exchange only). You use the [Set-MailboxAuditBypassAssociation](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxauditbypassassociation) cmdlet to enable this property to bypass mailbox audit logging.
+Use the Get-MailboxAuditBypassAssociation cmdlet to retrieve information about the AuditBypassEnabled property value for user accounts (on-premises Exchange and the cloud) and computer accounts (on-premises Exchange only). You use the [Set-MailboxAuditBypassAssociation](https://learn.microsoft.com/powershell/module/exchange/set-mailboxauditbypassassociation) cmdlet to enable this property to bypass mailbox audit logging.
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
@@ -61,15 +60,13 @@ This example returns all accounts that are configured for mailbox audit logging
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the user account or computer account where you want to view the value of the AuditBypassEnabled property.
```yaml
Type: MailboxAuditBypassAssociationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -90,6 +84,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -99,15 +94,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md
rename to exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md
index cee567d5c3..2eaf391e3c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxAutoReplyConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxautoreplyconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxAutoReplyConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxautoreplyconfiguration
-schema: 2.0.0
-title: Get-MailboxAutoReplyConfiguration
+ms.reviewer:
---
# Get-MailboxAutoReplyConfiguration
@@ -61,9 +60,6 @@ This example retrieves Automatic Replies settings for Tony's mailbox at contoso.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -81,6 +77,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -90,9 +87,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -101,6 +95,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -121,6 +113,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,9 +123,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -143,6 +133,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -152,15 +143,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of settings to return. If you want to return all settings that match the command, use unlimited for the value of this parameter.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -170,9 +159,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -181,6 +167,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md
rename to exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md
index bb084b22b9..d8966ce18e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxCalendarConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxcalendarconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxCalendarConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxcalendarconfiguration
-schema: 2.0.0
-title: Get-MailboxCalendarConfiguration
+ms.reviewer:
---
# Get-MailboxCalendarConfiguration
@@ -81,9 +80,6 @@ This example requests that the domain controller DC1 retrieves calendar settings
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -99,8 +95,9 @@ The Identity parameter specifies the mailbox that you want to view. You can use
```yaml
Type: MailboxIdParameter
-Parameter Sets: Default, Identity
+Parameter Sets: Default
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -109,10 +106,20 @@ Accept pipeline input: True (ByPropertyName, ByValue)
Accept wildcard characters: False
```
-### -DomainController
+```yaml
+Type: MailboxIdParameter
+Parameter Sets: Identity
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+### -DomainController
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -121,6 +128,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: Default
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,9 +138,6 @@ Accept wildcard characters: False
```
### -MailboxLocation
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill MailboxLocation Description }}
@@ -141,6 +146,7 @@ This parameter is available only in the cloud-based service.
Type: MailboxLocationIdParameter
Parameter Sets: MailboxLocation
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md b/exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md
rename to exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md
index 39190a3f18..075437cc2c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxCalendarFolder.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxcalendarfolder
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxCalendarFolder
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxcalendarfolder
-schema: 2.0.0
-title: Get-MailboxCalendarFolder
+ms.reviewer:
---
# Get-MailboxCalendarFolder
@@ -59,9 +58,6 @@ This example returns all provided publishing information for the specified calen
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the calendar folder that you want to view. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example:
@@ -83,6 +79,7 @@ Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Cal
Type: MailboxFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -92,9 +89,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -103,6 +97,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -112,9 +107,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -123,6 +115,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md b/exchange/exchange-ps/exchange/Get-MailboxDatabase.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md
rename to exchange/exchange-ps/exchange/Get-MailboxDatabase.md
index d0c9fca722..82286a48e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxDatabase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxdatabase
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MailboxDatabase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxdatabase
-schema: 2.0.0
-title: Get-MailboxDatabase
+ms.reviewer:
---
# Get-MailboxDatabase
@@ -74,9 +73,6 @@ This example returns detailed information about the mailbox database named Mailb
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox database that you want to view. You can use any value that uniquely identifies the database. For example:
- Name
@@ -89,6 +85,7 @@ If you have multiple databases with the same name, the command retrieves all dat
Type: DatabaseIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -98,9 +95,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter filters the results by the specified Mailbox server. You can use any value that uniquely identifies the server. For example:
- Name
@@ -114,6 +108,7 @@ You can't use this parameter with the Identity parameter.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -123,15 +118,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,15 +134,13 @@ Accept wildcard characters: False
```
### -DumpsterStatistics
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DumpsterStatistics switch specifies that transport dumpster statistics be returned with the database status. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -159,15 +150,13 @@ Accept wildcard characters: False
```
### -IncludeCorrupted
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -177,9 +166,6 @@ Accept wildcard characters: False
```
### -IncludePreExchange2010
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The IncludePreExchange2010 switch specifies whether to return information about Exchange 2007 ore earlier mailbox databases. You don't need to specify a value with this switch.
@@ -188,6 +174,7 @@ The IncludePreExchange2010 switch specifies whether to return information about
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -197,15 +184,13 @@ Accept wildcard characters: False
```
### -IncludePreExchange2013
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludePreExchange2013 switch specifies whether to return information about Exchange 2010 or earlier mailbox databases. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -215,9 +200,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Status switch specifies whether to retrieve the available free space in the database root and information about the following attributes:
- BackupInProgress
@@ -232,6 +214,7 @@ If you specify this switch, you should format the output in such a way that you
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md b/exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md
rename to exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md
index 90105c739e..d58b4dc67d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxDatabaseCopyStatus.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxdatabasecopystatus
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MailboxDatabaseCopyStatus
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxdatabasecopystatus
-schema: 2.0.0
-title: Get-MailboxDatabaseCopyStatus
+ms.reviewer:
---
# Get-MailboxDatabaseCopyStatus
@@ -75,15 +74,13 @@ This example returns the status for the copy of database DB1 on the Mailbox serv
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of the database copy for which the command should gather information. The Identity parameter can be specified in the form of `\`. Specifying just `` returns information for all copies of the database. This parameter can't be combined with the Server parameter.
```yaml
Type: DatabaseCopyIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -93,15 +90,13 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies that a Mailbox server returns status information for all of its mailbox database copies. This parameter can't be combined with the Identity parameter.
```yaml
Type: MailboxServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -111,15 +106,13 @@ Accept wildcard characters: False
```
### -Active
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Active switch specifies whether to return mailbox database copy status for the active mailbox database copy only. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -129,15 +122,13 @@ Accept wildcard characters: False
```
### -ConnectionStatus
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter has been deprecated and is no longer used.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -147,15 +138,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -165,15 +154,13 @@ Accept wildcard characters: False
```
### -Local
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Local switch specifies whether to return mailbox database copy status information from only the local Mailbox server. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -183,15 +170,13 @@ Accept wildcard characters: False
```
### -ExtendedErrorInfo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedErrorInfo switch specifies whether to return an output object containing any exception details. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -201,15 +186,13 @@ Accept wildcard characters: False
```
### -UseServerCache
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The UseServerCache switch specifies whether to enable a server-side remote procedure call (RPC) caching of status information for 5 seconds. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md b/exchange/exchange-ps/exchange/Get-MailboxExportRequest.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md
rename to exchange/exchange-ps/exchange/Get-MailboxExportRequest.md
index 15d115b5e7..106407e8e1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxExportRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxexportrequest
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MailboxExportRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxexportrequest
-schema: 2.0.0
-title: Get-MailboxExportRequest
+ms.reviewer:
---
# Get-MailboxExportRequest
@@ -99,9 +98,6 @@ This example returns all export requests that have the name DB01toPST where the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the export request. By default, export requests are named `\MailboxExportX` (where X = 0-9). If you specified a name for the export request when the request was created using the New-MailboxExportRequest cmdlet, use the following syntax: `Alias\Name`. Exchange automatically precedes the request with the mailbox's alias.
This parameter can't be with the following parameters:
@@ -117,6 +113,7 @@ This parameter can't be with the following parameters:
Type: MailboxExportRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -126,9 +123,6 @@ Accept wildcard characters: False
```
### -BatchName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BatchName parameter specifies the name given to a batch export request.
You can't use this parameter with the Identity parameter.
@@ -137,6 +131,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -146,9 +141,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Database parameter specifies the database in which the user's mailbox or archive resides. You can use any value that uniquely identifies the database. For example:
@@ -163,6 +155,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -172,15 +165,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -190,9 +181,6 @@ Accept wildcard characters: False
```
### -HighPriority
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
- $true Returns requests that were created with the Priority value High, Higher, Highest or Emergency.
@@ -204,6 +192,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -213,9 +202,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013
-
The Mailbox parameter filters the results by the source mailbox where the contents are being exported from.
In Exchange 2016 CU7 or later, this parameter is the type MailboxLocationIdParameter, so the easiest value that you can use to identify the mailbox is the Alias value.
@@ -237,8 +223,9 @@ You can't use this parameter with the Identity parameter.
```yaml
Type: MailboxOrMailUserIdParameter
-Parameter Sets: MailboxFiltering, MailboxLocationFiltering
+Parameter Sets: MailboxFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013
Required: False
Position: Named
@@ -247,10 +234,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -Name
+```yaml
+Type: MailboxLocationIdParameter
+Parameter Sets: MailboxLocationFiltering
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -Name
The Name parameter specifies that export requests that have the specified name are returned.
Use this parameter to search on the name that you provided when you created the export request.
@@ -263,6 +260,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -272,15 +270,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -290,9 +286,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Status parameter filters the results based on status. You can use the following values:
- AutoSuspended
@@ -314,6 +307,7 @@ CompletionInProgress and AutoSuspended don't apply to export requests and won't
Type: RequestStatus
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -323,9 +317,6 @@ Accept wildcard characters: False
```
### -Suspend
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
You can't use this parameter with the Identity parameter.
@@ -334,6 +325,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -343,9 +335,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
- Name
@@ -358,6 +347,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md
rename to exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md
index d5f0ed8fe8..27ef9ad06f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxExportRequestStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxexportrequeststatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MailboxExportRequestStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxexportrequeststatistics
-schema: 2.0.0
-title: Get-MailboxExportRequestStatistics
+ms.reviewer:
---
# Get-MailboxExportRequestStatistics
@@ -107,9 +106,6 @@ This example returns additional information for all the export requests that hav
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the export request. By default, export requests are named `\MailboxExportX` (where X = 0-9). If you specified a name for the export request when it was created by using the New-MailboxExportRequest cmdlet, use the following syntax: `Alias\Name`.
This parameter can't be used with the RequestGuid or RequestQueue parameters.
@@ -118,6 +114,7 @@ This parameter can't be used with the RequestGuid or RequestQueue parameters.
Type: MailboxExportRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -127,9 +124,6 @@ Accept wildcard characters: False
```
### -MRSInstance
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The MRSInstance parameter specifies the fully qualified domain name (FQDN) of the Client Access server on which the Microsoft Exchange Mailbox Replication service (MRS) resides. When using this parameter, all records are returned for this instance of MRS.
@@ -140,6 +134,7 @@ You can't use this parameter with the Identity or RequestQueue parameters.
Type: Fqdn
Parameter Sets: MRSInstance
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -149,9 +144,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is for debugging purposes only.
The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
@@ -166,6 +158,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -175,9 +168,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -186,6 +176,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: Identity, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -195,15 +186,13 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
```yaml
Type: String
Parameter Sets: Identity, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -213,9 +202,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -224,6 +210,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -233,15 +220,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -251,15 +236,13 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -269,15 +252,13 @@ Accept wildcard characters: False
```
### -ReportOnly
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -287,15 +268,13 @@ Accept wildcard characters: False
```
### -RequestGuid
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RequestGuid parameter specifies the unique identifier for the export request. To find the export request GUID, use the Get-MailboxExportRequest cmdlet. If you specify the RequestGuid parameter, you must also specify the RequestQueue parameter. You can't use this parameter with the Identity parameter.
```yaml
Type: Guid
Parameter Sets: MRSInstance, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md b/exchange/exchange-ps/exchange/Get-MailboxFolder.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md
rename to exchange/exchange-ps/exchange/Get-MailboxFolder.md
index 4f0450521d..3e9a4e5383 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxFolder.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolder
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxFolder
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxfolder
-schema: 2.0.0
-title: Get-MailboxFolder
+ms.reviewer:
---
# Get-MailboxFolder
@@ -86,9 +85,6 @@ This example returns a summary list of all levels of folders under Inbox in your
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox folder that you want to view. The syntax is `[MailboxID]:[\ParentFolder][\SubFolder]`.
You can only run this cmdlet on your own mailbox, so you don't need to (or can't) specify a `MailboxID` value.
@@ -114,6 +110,7 @@ Example values for this parameter are `john@contoso.com:`, `John:\Inbox`.
Type: MailboxFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -123,9 +120,6 @@ Accept wildcard characters: False
```
### -GetChildren
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The GetChildren switch specifies whether to return only the first level of subfolders under the specified parent folder. You don't need to specify a value with this switch.
You can't use this switch with the Recurse switch.
@@ -134,6 +128,7 @@ You can't use this switch with the Recurse switch.
Type: SwitchParameter
Parameter Sets: GetChildren
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -143,9 +138,6 @@ Accept wildcard characters: False
```
### -Recurse
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Recurse switch specifies whether to return the specified parent folder and all of its subfolders. You don't need to specify a value with this switch.
You can't use this switch with the GetChildren switch.
@@ -154,6 +146,7 @@ You can't use this switch with the GetChildren switch.
Type: SwitchParameter
Parameter Sets: Recurse
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -163,9 +156,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -174,6 +164,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -183,15 +174,13 @@ Accept wildcard characters: False
```
### -MailFolderOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MailFolderOnly switch specifies whether to return only the mail folders in the specified mailbox. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -201,15 +190,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md b/exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md
rename to exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md
index 45768bf0e7..1873b6abc7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxFolderPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderpermission
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxFolderPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxfolderpermission
-schema: 2.0.0
-title: Get-MailboxFolderPermission
+ms.reviewer:
---
# Get-MailboxFolderPermission
@@ -63,9 +62,6 @@ This example returns the permissions for the Calendar folder in John's mailbox,
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox folder that you want to view. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example:
@@ -87,6 +83,7 @@ Example values for this parameter are `john@contoso.com:\Calendar` or `John:\Inb
Type: MailboxFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -96,9 +93,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -107,6 +101,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -116,15 +111,13 @@ Accept wildcard characters: False
```
### -GroupMailbox
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The GroupMailbox switch is required to return Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -134,9 +127,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -145,6 +135,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -154,9 +145,6 @@ Accept wildcard characters: False
```
### -SkipCount
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill SkipCount Description }}
@@ -165,6 +153,7 @@ This parameter is available only in the cloud-based service.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -174,9 +163,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -185,6 +171,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -194,9 +181,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The User parameter filters the results by the specified mailbox, mail user, or mail-enabled security group (security principal) that's granted permission to the mailbox folder.
For the best results, we recommend using the following values:
@@ -217,6 +201,7 @@ Otherwise, you can use any value that uniquely identifies the user or group. For
Type: MailboxFolderUserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -242,10 +227,10 @@ To see the return types, which are also known as output types, that this cmdlet
## RELATED LINKS
-[Add-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/add-mailboxfolderpermission)
+[Add-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/add-mailboxfolderpermission)
-[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxfolderpermission)
+[Set-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/set-mailboxfolderpermission)
-[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/remove-mailboxfolderpermission)
+[Remove-MailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/remove-mailboxfolderpermission)
-[Get-EXOMailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchangepowershell/get-exomailboxfolderpermission)
+[Get-EXOMailboxFolderPermission](https://learn.microsoft.com/powershell/module/exchange/get-exomailboxfolderpermission)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md
rename to exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md
index 51eb753990..8b201910e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxFolderStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxfolderstatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxFolderStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxfolderstatistics
-schema: 2.0.0
-title: Get-MailboxFolderStatistics
+ms.reviewer:
---
# Get-MailboxFolderStatistics
@@ -116,9 +115,6 @@ This example uses the FolderScope parameter to view inbox folders statistics for
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the mailbox or mail user. You can use any value that uniquely identifies the mailbox or mail user. For example:
- Name
@@ -134,8 +130,9 @@ The Identity parameter specifies the identity of the mailbox or mail user. You c
```yaml
Type: GeneralMailboxOrMailUserIdParameter
-Parameter Sets: Identity, AuditLog
+Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -144,10 +141,20 @@ Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```
-### -Database
+```yaml
+Type: GeneralMailboxOrMailUserIdParameter
+Parameter Sets: AuditLog
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
-> Applicable: Exchange Online
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: True (ByPropertyName)
+Accept wildcard characters: False
+```
+### -Database
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -156,6 +163,7 @@ This parameter is reserved for internal Microsoft use.
Type: DatabaseIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -165,9 +173,6 @@ Accept wildcard characters: False
```
### -StoreMailboxIdentity
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -176,6 +181,7 @@ This parameter is reserved for internal Microsoft use.
Type: StoreMailboxIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -185,15 +191,13 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Archive switch specifies whether to return the usage statistics of the archive associated with the mailbox or mail user. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -203,9 +207,6 @@ Accept wildcard characters: False
```
### -AuditLog
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -214,6 +215,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: AuditLog
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -223,9 +225,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -234,6 +233,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -243,9 +243,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -254,6 +251,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: Identity, AuditLog
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -263,9 +261,6 @@ Accept wildcard characters: False
```
### -FolderScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FolderScope parameter specifies the scope of the search by folder type. Valid parameter values include:
- All
@@ -294,6 +289,7 @@ The FolderScope parameter specifies the scope of the search by folder type. Vali
Type: ElcFolderType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -303,9 +299,6 @@ Accept wildcard characters: False
```
### -IncludeAnalysis
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeAnalysis switch specifies whether to scan all items within a folder and return statistics related to the folder and item size. You don't need to specify a value with this switch.
You should use this switch for troubleshooting purposes, because the command might take a long time to complete.
@@ -314,6 +307,7 @@ You should use this switch for troubleshooting purposes, because the command mig
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -323,15 +317,13 @@ Accept wildcard characters: False
```
### -IncludeOldestAndNewestItems
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeOldestAndNewestItems switch specifies whether to return the dates of the oldest and newest items in each folder. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -341,9 +333,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedRecipients
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeSoftDeletedRecipients switch specifies whether to include soft deleted mailboxes in the results. You don't need to specify a value with this switch.
@@ -354,6 +343,7 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -363,9 +353,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -374,6 +361,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -383,9 +371,6 @@ Accept wildcard characters: False
```
### -SkipCount
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill SkipCount Description }}
@@ -394,6 +379,7 @@ This parameter is available only in the cloud-based service.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -403,9 +389,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -414,6 +397,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md b/exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md
rename to exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md
index 5988155a36..ca07bcdfd7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxIRMAccess.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxirmaccess
applicable: Exchange Online
+title: Get-MailboxIRMAccess
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxirmaccess
-schema: 2.0.0
-title: Get-MailboxIRMAccess
+ms.reviewer:
---
# Get-MailboxIRMAccess
@@ -57,9 +56,6 @@ This example returns information about delegate Chris' access to IRM-protected m
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox where you want to view delegate access to IRM-protected messages. You can use any value that uniquely identifies the mailbox. For example
- Name
@@ -77,6 +73,7 @@ The Identity parameter specifies the mailbox where you want to view delegate acc
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -86,9 +83,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Online
-
The User parameter filters the results in the mailbox by the specified delegate. The delegate must be a user mailbox or a mail user. You can use any value that uniquely identifies the delegate. For example:
- Name
@@ -106,6 +100,7 @@ The User parameter filters the results in the mailbox by the specified delegate.
Type: SecurityPrincipalIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md b/exchange/exchange-ps/exchange/Get-MailboxImportRequest.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md
rename to exchange/exchange-ps/exchange/Get-MailboxImportRequest.md
index 26a0c1dd9f..63f31df6ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxImportRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboximportrequest
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxImportRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboximportrequest
-schema: 2.0.0
-title: Get-MailboxImportRequest
+ms.reviewer:
---
# Get-MailboxImportRequest
@@ -101,9 +100,6 @@ This example returns all import requests that have the name Recovered where the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the import request. By default, import requests are named `\MailboxImportX` (where X = 0-9). If you specify a name for the import request, use the following syntax: `Alias\Name`. Microsoft Exchange automatically precedes the request with the mailbox's alias.
You can't use this parameter with the following parameters:
@@ -119,6 +115,7 @@ You can't use this parameter with the following parameters:
Type: MailboxImportRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -128,9 +125,6 @@ Accept wildcard characters: False
```
### -BatchName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BatchName parameter specifies the name given to a batch import request.
You can't use this parameter with the Identity parameter.
@@ -139,6 +133,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -148,9 +143,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Database parameter specifies the database in which the user's mailbox or archive resides. You can use any value that uniquely identifies the database. For example:
@@ -165,6 +157,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -174,9 +167,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -185,6 +175,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -194,9 +185,6 @@ Accept wildcard characters: False
```
### -HighPriority
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
@@ -210,6 +198,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -219,9 +208,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013
-
This parameter is functional only in on-premises Exchange.
The Mailbox parameter filters the results by the destination mailbox where the content is being imported to.
@@ -245,8 +231,9 @@ You can't use this parameter with the Identity parameter.
```yaml
Type: MailboxOrMailUserIdParameter
-Parameter Sets: MailboxFiltering, MailboxLocationFiltering
+Parameter Sets: MailboxFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013
Required: False
Position: Named
@@ -255,10 +242,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -Name
+```yaml
+Type: MailboxLocationIdParameter
+Parameter Sets: MailboxLocationFiltering
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -Name
The Name parameter specifies that import requests that have the specified name are returned.
Use this parameter to search on the name that you provided when you created the import request. If you didn't specify a name when the request was created, the default name is MailboxImportX (where X = 0-9).
@@ -269,6 +266,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -278,15 +276,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -296,9 +292,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Status parameter filters the results based on status. You can use the following values:
- AutoSuspended
@@ -320,6 +313,7 @@ CompletionInProgress and AutoSuspended don't apply to import requests and won't
Type: RequestStatus
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -329,9 +323,6 @@ Accept wildcard characters: False
```
### -Suspend
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
You can't use this parameter with the Identity parameter.
@@ -340,6 +331,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -349,9 +341,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
@@ -366,6 +355,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MailboxFiltering, MailboxLocationFiltering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md
rename to exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md
index f2b4d0172b..5803c36890 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxImportRequestStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboximportrequeststatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxImportRequestStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboximportrequeststatistics
-schema: 2.0.0
-title: Get-MailboxImportRequestStatistics
+ms.reviewer:
---
# Get-MailboxImportRequestStatistics
@@ -109,9 +108,6 @@ This example returns additional information for all the import requests that hav
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the import request. By default, import requests are named `\MailboxImportX` (where X = 0-9). If you specified a name when you created the import request, use the following syntax: `Alias\Name`.
**Note**: In Exchange Online, the alias of a soft-deleted mailbox might match the alias of an active mailbox. To ensure uniqueness, use the RequestGuid value from the output of the Get-MailboxImportRequest cmdlet for the value of this parameter.
@@ -120,6 +116,7 @@ The Identity parameter specifies the identity of the import request. By default,
Type: MailboxImportRequestIdParameter
Parameter Sets: IdentityOnPremises, IdentityCloud
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -129,9 +126,6 @@ Accept wildcard characters: False
```
### -MRSInstance
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The MRSInstance parameter specifies the fully qualified domain name (FQDN) of the Client Access server on which the Microsoft Exchange Mailbox Replication service (MRS) resides. When using this parameter, all records are returned for this instance of MRS.
@@ -142,6 +136,7 @@ You can't use this parameter with the Identity or RequestQueue parameters.
Type: Fqdn
Parameter Sets: MigrationMRSInstance
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -151,9 +146,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is for debugging purposes only.
@@ -170,6 +162,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -179,9 +172,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
@@ -192,6 +182,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -201,9 +192,6 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -212,6 +200,7 @@ The DiagnosticArgument parameter modifies the results that are returned by using
Type: String
Parameter Sets: IdentityOnPremises, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -221,9 +210,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -232,6 +218,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -241,9 +228,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -252,6 +236,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: IdentityOnPremises, MigrationRequestQueue, MigrationMRSInstance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -261,15 +246,13 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, IdentityCloud, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -279,9 +262,6 @@ Accept wildcard characters: False
```
### -IncludeSkippedItems
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeSkippedItems Description }}
@@ -290,6 +270,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -299,9 +280,6 @@ Accept wildcard characters: False
```
### -RequestGuid
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RequestGuid parameter (together with the RequestQueue parameter) specifies the unique identifier for the import request. To find the import request GUID, use the Get-MailboxImportRequest cmdlet.
@@ -312,6 +290,7 @@ You can't use this parameter with the Identity parameter.
Type: Guid
Parameter Sets: MigrationMRSInstance, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -321,15 +300,13 @@ Accept wildcard characters: False
```
### -ReportOnly
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, IdentityCloud, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md
rename to exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md
index 2d93050ad9..4f8fe4884f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxJunkEmailConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxjunkemailconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxJunkEmailConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxjunkemailconfiguration
-schema: 2.0.0
-title: Get-MailboxJunkEmailConfiguration
+ms.reviewer:
---
# Get-MailboxJunkEmailConfiguration
@@ -68,9 +67,6 @@ To return all mailboxes where the junk email rule is enabled, change the value $
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -90,6 +86,7 @@ You can use the wildcard character (\*) to identify multiple mailboxes.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -99,9 +96,6 @@ Accept wildcard characters: True
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -110,6 +104,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -119,9 +114,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -130,6 +122,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -139,9 +132,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -152,6 +142,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -161,15 +152,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md b/exchange/exchange-ps/exchange/Get-MailboxLocation.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md
rename to exchange/exchange-ps/exchange/Get-MailboxLocation.md
index 49f45baaaf..ea42b8a024 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxLocation.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxlocation
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxLocation
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxlocation
-schema: 2.0.0
-title: Get-MailboxLocation
+ms.reviewer:
---
# Get-MailboxLocation
@@ -74,9 +73,6 @@ In Exchange Server or Exchange Online, this example returns the mailbox location
## PARAMETERS
### -Database
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Database parameter returns the mailbox location information for all mailboxes on the specified mailbox database. You can use any value that uniquely identifies the database. For example:
@@ -91,6 +87,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: DatabaseSet
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -100,9 +97,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox location object that you want to view. The value uses the either of the following formats:
- TenantGUID\\MailboxGUID
@@ -118,6 +112,7 @@ You can't use this parameter with the User parameter.
Type: MailboxLocationIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -127,9 +122,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The User parameter specifies the user whose mailbox location you want to view. You can use any value that uniquely identifies the user. For example:
@@ -145,6 +137,7 @@ You can't use this parameter with the Identity parameter.
Type: UserIdParameter
Parameter Sets: User
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -154,9 +147,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -166,6 +156,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -175,9 +166,6 @@ Accept wildcard characters: False
```
### -IncludePreviousPrimary
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludePreviousPrimary switch specifies whether to include the previous primary mailbox in the results. You don't need to specify a value with this switch.
@@ -188,6 +176,7 @@ You can only use this switch with the User parameter.
Type: SwitchParameter
Parameter Sets: User
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -197,9 +186,6 @@ Accept wildcard characters: False
```
### -MailboxLocationType
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MailboxLocationType filters the results by the type of mailbox. Valid values are:
- Aggregated
@@ -214,6 +200,7 @@ The MailboxLocationType filters the results by the type of mailbox. Valid values
Type: MailboxLocationType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -223,15 +210,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -241,15 +226,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md
rename to exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md
index 973de8d9f7..fff93d6e2a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxMessageConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxmessageconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxMessageConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxmessageconfiguration
-schema: 2.0.0
-title: Get-MailboxMessageConfiguration
+ms.reviewer:
---
# Get-MailboxMessageConfiguration
@@ -59,9 +58,6 @@ This example returns the Outlook on the web settings for Tony's mailbox and spec
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -79,6 +75,7 @@ The Identity parameter specifies the mailbox. You can use any value that uniquel
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -88,9 +85,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Credential parameter specifies the username and password to use to access the mailbox.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -99,6 +93,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -108,9 +103,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -119,6 +111,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -128,9 +121,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -141,6 +131,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -150,15 +141,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -168,9 +157,6 @@ Accept wildcard characters: False
```
### -SignatureName
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill SignatureName Description }}
@@ -179,6 +165,7 @@ This parameter is available only in the cloud-based service.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -188,9 +175,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -199,6 +183,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md b/exchange/exchange-ps/exchange/Get-MailboxPermission.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md
rename to exchange/exchange-ps/exchange/Get-MailboxPermission.md
index 46b2722ed2..80fc4e6f73 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxpermission
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxpermission
-schema: 2.0.0
-title: Get-MailboxPermission
+ms.reviewer:
---
# Get-MailboxPermission
@@ -98,9 +97,6 @@ This example returns the owner information for the resource mailbox Room222.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -118,6 +114,7 @@ The Identity parameter specifies the mailbox you want to view. You can use any v
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -127,9 +124,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -138,6 +132,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -147,9 +142,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -158,6 +150,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -167,9 +160,6 @@ Accept wildcard characters: False
```
### -GroupMailbox
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The GroupMailbox switch is required to return Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
@@ -178,6 +168,7 @@ The GroupMailbox switch is required to return Microsoft 365 Groups in the result
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -187,9 +178,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedUserPermissions
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeSoftDeletedUserPermissions switch returns permissions from soft-deleted mailbox users in the results. You don't need to specify a value with this switch.
@@ -200,6 +188,7 @@ Soft-deleted mailboxes are mailboxes that have been deleted, but are still recov
Type: SwitchParameter
Parameter Sets: AccessRights
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -209,9 +198,6 @@ Accept wildcard characters: False
```
### -IncludeUnresolvedPermissions
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeUnresolvedPermissions switch returns unresolved permissions in the results. You don't need to specify a value with this switch.
@@ -220,6 +206,7 @@ The IncludeUnresolvedPermissions switch returns unresolved permissions in the re
Type: SwitchParameter
Parameter Sets: AccessRights
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -229,9 +216,6 @@ Accept wildcard characters: False
```
### -IncludeUserWithDisplayName
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeUserWithDisplayName Description }}
@@ -240,6 +224,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -249,9 +234,6 @@ Accept wildcard characters: False
```
### -Owner
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Owner switch returns the owner information for the mailbox that's specified by the Identity parameter. You don't need to specify a value with this switch.
You can't use this switch with the User parameter.
@@ -260,6 +242,7 @@ You can't use this switch with the User parameter.
Type: SwitchParameter
Parameter Sets: Owner
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -269,9 +252,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -282,6 +262,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -291,15 +272,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -309,9 +288,6 @@ Accept wildcard characters: False
```
### -SoftDeletedMailbox
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The SoftDeletedMailbox switch is required to return soft-deleted mailboxes in the results. You don't need to specify a value with this switch.
@@ -322,6 +298,7 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
Type: SwitchParameter
Parameter Sets: AccessRights
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -331,9 +308,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -342,6 +316,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -351,9 +326,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The User parameter filters the results by who has permissions to the mailbox that's specified by the Identity parameter. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -384,6 +356,7 @@ You can't use this parameter with the Owner switch.
Type: SecurityPrincipalIdParameter
Parameter Sets: AccessRights
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md b/exchange/exchange-ps/exchange/Get-MailboxPlan.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md
rename to exchange/exchange-ps/exchange/Get-MailboxPlan.md
index 76da58ae59..c1a6bb560a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxPlan.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxplan
applicable: Exchange Online
+title: Get-MailboxPlan
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxplan
-schema: 2.0.0
-title: Get-MailboxPlan
+ms.reviewer:
---
# Get-MailboxPlan
@@ -56,9 +55,6 @@ This example returns detailed information for the mailbox plan that has the disp
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the mailbox plan that you want to view. You can use any value that uniquely identifies the mailbox plan. For example:
- Name
@@ -71,6 +67,7 @@ The Identity parameter specifies the mailbox plan that you want to view. You can
Type: MailboxPlanIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -80,9 +77,6 @@ Accept wildcard characters: False
```
### -AllMailboxPlanReleases
-
-> Applicable: Exchange Online
-
The AllMailboxPlanReleases switch specifies whether to include mailbox plans that were used in previous versions of the service in the results. You don't need to specify a value with this switch.
If you don't use this switch, the command returns only mailbox plans that are used in the current version of the service. This parameter has meaning only for organizations that were enrolled in previous versions of the service.
@@ -91,6 +85,7 @@ If you don't use this switch, the command returns only mailbox plans that are us
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -100,9 +95,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Online
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -111,6 +103,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -120,9 +113,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -138,6 +128,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -147,15 +138,13 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -165,15 +154,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -183,9 +170,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -200,6 +184,7 @@ You can sort by the following attributes:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md
rename to exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md
index a44a8b5da5..0915467f52 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxRegionalConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxregionalconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxRegionalConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxregionalconfiguration
-schema: 2.0.0
-title: Get-MailboxRegionalConfiguration
+ms.reviewer:
---
# Get-MailboxRegionalConfiguration
@@ -43,7 +42,7 @@ Get-MailboxRegionalConfiguration [-MailboxLocation ]
```
## DESCRIPTION
-To modify the regional settings of a mailbox, use the [Set-MailboxRegionalConfiguration](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxregionalconfiguration) cmdlet.
+To modify the regional settings of a mailbox, use the [Set-MailboxRegionalConfiguration](https://learn.microsoft.com/powershell/module/exchange/set-mailboxregionalconfiguration) cmdlet.
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
@@ -73,9 +72,6 @@ This example returns the regional settings for Alice Jakobsen's mailbox and also
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -91,8 +87,9 @@ The Identity parameter specifies the mailbox that you want to view. You can use
```yaml
Type: MailboxIdParameter
-Parameter Sets: Default, Identity
+Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -101,10 +98,20 @@ Accept pipeline input: True (ByPropertyName, ByValue)
Accept wildcard characters: False
```
-### -Archive
+```yaml
+Type: MailboxIdParameter
+Parameter Sets: Identity
+Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Online
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+### -Archive
This parameter is available only in the cloud-based service.
{{ Fill Archive Description }}
@@ -113,6 +120,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -122,9 +130,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -133,6 +138,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: Default
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -142,9 +148,6 @@ Accept wildcard characters: False
```
### -MailboxLocation
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill MailboxLocation Description }}
@@ -153,6 +156,7 @@ This parameter is available only in the cloud-based service.
Type: MailboxLocationIdParameter
Parameter Sets: MailboxLocation
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -162,9 +166,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -173,6 +174,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, MailboxLocation
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -182,9 +184,6 @@ Accept wildcard characters: False
```
### -VerifyDefaultFolderNameLanguage
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The VerifyDefaultFolderNameLanguage switch verifies that the default folder names are localized in the language that's specified for the mailbox (the Language property value). You don't need to specify a value with this switch.
The results are displayed in the DefaultFolderNameMatchingUserLanguage property. To see this property, you need to pipeline the results of the command to the Format-List or Format-Table cmdlets. For example:
@@ -201,6 +200,7 @@ If you view the DefaultFolderNameMatchingUserLanguage property without using the
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md b/exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md
rename to exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md
index d9224ee757..d247baf12a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxRepairRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxrepairrequest
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MailboxRepairRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxrepairrequest
-schema: 2.0.0
-title: Get-MailboxRepairRequest
+ms.reviewer:
---
# Get-MailboxRepairRequest
@@ -84,9 +83,6 @@ This example uses the Database and StoreMailbox parameters to display the Identi
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox repair request to display information about. Mailbox repair requests are identified by a complex GUID that is created when a new mailbox repair request is created. This GUID consists of a database ID, a Request ID and a job ID. The format is `DatabaseGuid\RequestGuid\JobGuid`.
You can't use this parameter with the Database or Mailbox parameters.
@@ -95,6 +91,7 @@ You can't use this parameter with the Database or Mailbox parameters.
Type: StoreIntegrityCheckJobIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -104,9 +101,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Database parameter returns mailbox repair requests for all mailboxes on the specified database. You can use any value that uniquely identifies the database. For example:
- Name
@@ -119,6 +113,7 @@ You can't use this parameter with the Identity or Mailbox parameters.
Type: DatabaseIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -128,9 +123,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Mailbox parameter specifies the mailbox that you want to get mailbox repair request information about. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -150,6 +142,7 @@ You can't use this parameter with the Database or Identity parameters.
Type: MailboxIdParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -159,9 +152,6 @@ Accept wildcard characters: False
```
### -StoreMailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The StoreMailbox parameter specifies the mailbox GUID of the mailbox that you want to get mailbox repair request information about. Use this parameter with the Database parameter.
Use the Get-MailboxStatistics cmdlet to find the mailbox GUID for a mailbox.
@@ -170,6 +160,7 @@ Use the Get-MailboxStatistics cmdlet to find the mailbox GUID for a mailbox.
Type: StoreMailboxIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 2
@@ -179,9 +170,6 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Archive switch displays information about the associated archive mailbox if the archive mailbox was included when the mailbox repair request was created. You don't need to specify a value with this switch.
If you don't use this switch, only information about the primary mailbox is returned.
@@ -192,6 +180,7 @@ You can't use this switch with the Database parameter.
Type: SwitchParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -201,15 +190,13 @@ Accept wildcard characters: False
```
### -Detailed
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
Use the Detailed parameter to display mailbox-level repair tasks associated with the repair request. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -219,15 +206,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md
rename to exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md
index 91a54258e6..307c4af120 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxrestorerequest
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxRestoreRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxrestorerequest
-schema: 2.0.0
-title: Get-MailboxRestoreRequest
+ms.reviewer:
---
# Get-MailboxRestoreRequest
@@ -81,9 +80,6 @@ This example returns all restore requests that have the name RestoreToMBD01 wher
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the restore request. The Identity parameter consists of the alias of the mailbox to be restored and the name that was specified when the restore request was created. The identity of the restore request uses the following syntax: `Alias\Name`.
If you didn't specify a name for the restore request when it was created, Exchange automatically generated the default name MailboxRestore. Exchange generates up to 10 names, starting with MailboxRestore and then MailboxRestoreX (where X = 1-9).
@@ -94,6 +90,7 @@ You can't use this parameter with the Name parameter.
Type: MailboxRestoreRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -103,9 +100,6 @@ Accept wildcard characters: False
```
### -BatchName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BatchName parameter specifies the name given to a batch of restore requests.
You can't use this parameter with the Identity parameter.
@@ -114,6 +108,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -123,9 +118,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -134,6 +126,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -143,9 +136,6 @@ Accept wildcard characters: False
```
### -HighPriority
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
- $true Returns requests that were created with the Priority value High, Higher, Highest or Emergency.
@@ -157,6 +147,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -166,9 +157,6 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies that any restore request that has the specified name is returned.
Use this parameter to search on the name you provided when you created the restore request.
@@ -181,6 +169,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -190,9 +179,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
@@ -207,6 +193,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -216,15 +203,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -234,9 +219,6 @@ Accept wildcard characters: False
```
### -SourceDatabase
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The SourceDatabase parameter specifies that the cmdlet should only return restore requests for mailboxes that are being restored from the specified source database. You can use any value that uniquely identifies the database. For example:
@@ -251,6 +233,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -260,9 +243,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Status parameter filters the results based on status. You can use the following values:
- AutoSuspended
@@ -282,6 +262,7 @@ You can't use this parameter with the Identity parameter.
Type: RequestStatus
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -291,9 +272,6 @@ Accept wildcard characters: False
```
### -Suspend
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
You can't use this parameter with the Identity parameter.
@@ -302,6 +280,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -311,9 +290,6 @@ Accept wildcard characters: False
```
### -TargetDatabase
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The TargetDatabase parameter specifies that the cmdlet should only return restore requests for mailboxes that reside on the target database. You can use any value that uniquely identifies the database. For example:
@@ -328,6 +304,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -337,9 +314,6 @@ Accept wildcard characters: False
```
### -TargetMailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The TargetMailbox parameter specifies the identity of the target mailbox. You can use the following values:
- GUID
@@ -356,6 +330,7 @@ You can't use this parameter with the Identity parameter.
Type: MailboxOrMailUserIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md
rename to exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md
index cf05e6387b..08a0693b85 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxRestoreRequestStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxrestorerequeststatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxRestoreRequestStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxrestorerequeststatistics
-schema: 2.0.0
-title: Get-MailboxRestoreRequestStatistics
+ms.reviewer:
---
# Get-MailboxRestoreRequestStatistics
@@ -105,9 +104,6 @@ This example returns additional information for all the restore requests that ha
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the restore request. The Identity parameter consists of the alias of the mailbox to be restored and the name that was specified when the restore request was created. The identity of the restore request uses the following syntax: `Alias\Name`.
If you didn't specify a name for the restore request when it was created, Exchange automatically generated the default name MailboxRestore. Exchange generates up to 10 names, starting with MailboxRestore and then MailboxRestoreX (where X = 1-9).
@@ -118,6 +114,7 @@ You can't use this parameter with the MRSInstance or RequestQueue parameters.
Type: MailboxRestoreRequestIdParameter
Parameter Sets: IdentityOnPremises, IdentityCloud
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -127,9 +124,6 @@ Accept wildcard characters: False
```
### -MRSInstance
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The MRSInstance parameter specifies the fully qualified domain name (FQDN) of the Client Access server on which the Microsoft Exchange Mailbox Replication service (MRS) resides. When using this parameter, all records are returned for this instance of MRS.
@@ -140,6 +134,7 @@ You can't use this parameter with the Identity or RequestQueue parameters.
Type: Fqdn
Parameter Sets: MigrationMRSInstance
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -149,9 +144,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is for debugging purposes only.
@@ -168,6 +160,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -177,15 +170,13 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, IdentityCloud, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -195,9 +186,6 @@ Accept wildcard characters: False
```
### -RequestGuid
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RequestGuid parameter specifies the unique identifier for the restore request. To find the GUID, use the Get-MailboxRestoreRequest cmdlet.
@@ -206,6 +194,7 @@ The RequestGuid parameter specifies the unique identifier for the restore reques
Type: Guid
Parameter Sets: MigrationMRSInstance, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -215,9 +204,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
@@ -228,6 +214,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -237,9 +224,6 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -248,6 +232,7 @@ The DiagnosticArgument parameter modifies the results that are returned by using
Type: String
Parameter Sets: IdentityOnPremises, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -257,9 +242,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -268,6 +250,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -277,9 +260,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -288,6 +268,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: IdentityOnPremises, MigrationMRSInstance, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -297,9 +278,6 @@ Accept wildcard characters: False
```
### -IncludeSkippedItems
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeSkippedItems Description }}
@@ -308,6 +286,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -317,15 +296,13 @@ Accept wildcard characters: False
```
### -ReportOnly
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, IdentityCloud, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md b/exchange/exchange-ps/exchange/Get-MailboxSearch.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md
rename to exchange/exchange-ps/exchange/Get-MailboxSearch.md
index 607711b6f8..3051b480ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxSearch.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxsearch
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxSearch
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxsearch
-schema: 2.0.0
-title: Get-MailboxSearch
+ms.reviewer:
---
# Get-MailboxSearch
@@ -84,9 +83,6 @@ This example retrieves the In-Place Holds that a user is placed on. The first co
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name of the search query. If a name isn't provided, all mailbox search queries are returned.
To improve the performance of this cmdlet in Exchange Online, some mailbox search properties aren't returned if you don't specify the name of a mailbox search. These properties are:
@@ -102,8 +98,9 @@ To view these properties, you have to provide the name of a mailbox search.
```yaml
Type: SearchObjectIdParameter
-Parameter Sets: EwsStoreObjectIdentity, SearchObjectIdentity
+Parameter Sets: EwsStoreObjectIdentity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -112,16 +109,27 @@ Accept pipeline input: True
Accept wildcard characters: False
```
-### -InPlaceHoldIdentity
+```yaml
+Type: SearchObjectIdParameter
+Parameter Sets: SearchObjectIdentity
+Aliases:
+Applicable: Exchange Server 2010
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: True
+Accept wildcard characters: False
+```
+### -InPlaceHoldIdentity
The InPlaceHoldIdentity parameter specifies the GUID of an In-Place Hold. Use this parameter to search for an In-Place Hold that a user is placed on. GUIDs of all In-Place Holds that a user is placed on are added to the user's InPlaceHolds property. You can retrieve the property by using the Get-Mailbox cmdlet.
```yaml
Type: String
Parameter Sets: InPlaceHoldIdentity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -131,9 +139,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -142,6 +147,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -151,15 +157,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -169,15 +173,13 @@ Accept wildcard characters: False
```
### -ShowDeletionInProgressSearches
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: EwsStoreObjectIdentity, InPlaceHoldIdentity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md
rename to exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md
index 847a41ef34..0db5f4e4f3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxSentItemsConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxsentitemsconfiguration
applicable: Exchange Server 2010
+title: Get-MailboxSentItemsConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxsentitemsconfiguration
-schema: 2.0.0
-title: Get-MailboxSentItemsConfiguration
+ms.reviewer:
---
# Get-MailboxSentItemsConfiguration
@@ -44,15 +43,13 @@ This example returns the Sent Items configuration for the shared mailbox named "
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -62,9 +59,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the mailbox whose Sent Items configuration you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -82,6 +76,7 @@ The Identity parameter specifies the mailbox whose Sent Items configuration you
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md b/exchange/exchange-ps/exchange/Get-MailboxServer.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md
rename to exchange/exchange-ps/exchange/Get-MailboxServer.md
index 6be71ce89d..7b2886ee8a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxserver
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MailboxServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxserver
-schema: 2.0.0
-title: Get-MailboxServer
+ms.reviewer:
---
# Get-MailboxServer
@@ -52,9 +51,6 @@ This example returns detailed information about the Mailbox server named Server1
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Mailbox server that you want to view. You can use any value that uniquely identifies the Mailbox server. For example:
- Name
@@ -65,6 +61,7 @@ The Identity parameter specifies the Mailbox server that you want to view. You c
Type: MailboxServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -74,15 +71,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -92,9 +87,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Status switch specifies whether to include additional property values in the results, for example, the Locale value. You don't need to specify a value with this switch.
To see the additional values, you need to pipe the output to a formatting cmdlet, for example, the Format-List cmdlet.
@@ -103,6 +95,7 @@ To see the additional values, you need to pipe the output to a formatting cmdlet
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md
rename to exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md
index d132b4950f..711e199b87 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxSpellingConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxspellingconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxSpellingConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxspellingconfiguration
-schema: 2.0.0
-title: Get-MailboxSpellingConfiguration
+ms.reviewer:
---
# Get-MailboxSpellingConfiguration
@@ -63,9 +62,6 @@ This example returns the Outlook on the web spelling checker options for Tony's
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -83,6 +79,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -92,9 +89,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -103,6 +97,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md b/exchange/exchange-ps/exchange/Get-MailboxStatistics.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md
rename to exchange/exchange-ps/exchange/Get-MailboxStatistics.md
index 53dfbc6753..364729d637 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxstatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxstatistics
-schema: 2.0.0
-title: Get-MailboxStatistics
+ms.reviewer:
---
# Get-MailboxStatistics
@@ -149,9 +148,6 @@ This example returns the detailed move history and a verbose detailed move repor
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to return statistics for. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -169,6 +165,7 @@ The Identity parameter specifies the mailbox that you want to return statistics
Type: GeneralMailboxOrMailUserIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -178,9 +175,6 @@ Accept wildcard characters: False
```
### -StoreMailboxIdentity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The StoreMailboxIdentity parameter specifies the mailbox identity when used with the Database parameter to return statistics for a single mailbox on the specified database. You can use one of the following values:
@@ -194,6 +188,7 @@ Use this syntax to retrieve information about disconnected mailboxes, which don'
Type: StoreMailboxIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -203,15 +198,13 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Archive switch specifies whether to return mailbox statistics for the archive mailbox that's associated with the mailbox. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -221,9 +214,6 @@ Accept wildcard characters: False
```
### -CopyOnServer
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The CopyOnServer parameter is used to retrieve statistics from a specific database copy on the specified server.
@@ -241,6 +231,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: Database, Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -250,9 +241,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Database parameter returns statistics for all mailboxes on the specified database. You can use any value that uniquely identifies the database. For example:
@@ -267,6 +255,7 @@ This parameter accepts pipeline input from the Get-MailboxDatabase cmdlet.
Type: DatabaseIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -276,9 +265,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -287,6 +273,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -296,9 +283,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
@@ -318,6 +302,7 @@ For example, to display all disconnected mailboxes on a specific mailbox databas
Type: String
Parameter Sets: Database, Server
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -327,15 +312,13 @@ Accept wildcard characters: False
```
### -IncludeMoveHistory
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeMoveHistory switch specifies whether to return additional information about the mailbox that includes the history of a completed move request, such as status, flags, target database, bad items, start times, end times, duration that the move request was in various stages, and failure codes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -345,9 +328,6 @@ Accept wildcard characters: False
```
### -IncludeMoveReport
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeMoveReport switch specifies whether to return a verbose detailed move report for a completed move request, such as server connections and move stages. You don't need to specify a value with this switch.
Because the output of this command is verbose, you should send the output to a .CSV file for easier analysis.
@@ -356,6 +336,7 @@ Because the output of this command is verbose, you should send the output to a .
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -365,9 +346,6 @@ Accept wildcard characters: False
```
### -IncludePassive
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IncludePassive switch specifies whether to return statistics from all active and passive database copies. You don't need to specify a value with this switch.
@@ -378,6 +356,7 @@ If you don't use this switch, the command retrieves statistics from active datab
Type: SwitchParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -387,9 +366,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedRecipients
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeSoftDeletedRecipients switch specifies whether to include soft deleted mailboxes in the results. You don't need to specify a value with this switch.
@@ -400,6 +376,7 @@ Soft-deleted mailboxes are deleted mailboxes that are still recoverable.
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -409,9 +386,6 @@ Accept wildcard characters: False
```
### -IncludeQuarantineDetails
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IncludeQuarantineDetails switch specifies whether to return additional quarantine details about the mailbox that aren't otherwise included in the results. You can use these details to determine when and why the mailbox was quarantined. You don't need to specify a value with this switch.
@@ -422,6 +396,7 @@ Specifically, this switch returns the values of the QuarantineDescription, Quara
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -431,9 +406,6 @@ Accept wildcard characters: False
```
### -NoADLookup
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The NoADLookup switch specifies that information is retrieved from the mailbox database, and not from Active Directory. You don't need to specify a value with this switch.
@@ -444,6 +416,7 @@ This switch helps improve cmdlet performance when querying a mailbox database th
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -453,9 +426,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Server parameter specifies the server from which you want to obtain mailbox statistics. You can use one of the following values:
@@ -469,6 +439,7 @@ When you specify a value for the Server parameter, the command returns statistic
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -478,9 +449,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -489,6 +457,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md b/exchange/exchange-ps/exchange/Get-MailboxTransportService.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md
rename to exchange/exchange-ps/exchange/Get-MailboxTransportService.md
index 25cb4369a6..4e4beb49a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxTransportService.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxtransportservice
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MailboxTransportService
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxtransportservice
-schema: 2.0.0
-title: Get-MailboxTransportService
+ms.reviewer:
---
# Get-MailboxTransportService
@@ -51,15 +50,13 @@ This example retrieves the detailed transport configuration information for the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the server that you want to view.
```yaml
Type: MailboxTransportServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md b/exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md
rename to exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md
index 961975f2db..6487e6dc0e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-MailboxUserConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailboxuserconfiguration
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MailboxUserConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailboxuserconfiguration
-schema: 2.0.0
-title: Get-MailboxUserConfiguration
+ms.reviewer:
---
# Get-MailboxUserConfiguration
@@ -51,9 +50,6 @@ This example returns detailed information for the specified user configuration i
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the user configuration item that you want to view. This parameter uses the syntax MailboxFolder\ItemName:
- Valid values for MailboxFolder are folder names (for example, Inbox or Calendar), the value Configuration, or the value Root. Wildcards (\*) aren't supported.
@@ -63,6 +59,7 @@ The Identity parameter specifies the user configuration item that you want to vi
Type: MailboxUserConfigurationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that contains the user configuration items you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -92,6 +86,7 @@ The Mailbox parameter specifies the mailbox that contains the user configuration
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -101,15 +96,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -119,9 +112,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -130,6 +120,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -139,15 +130,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md b/exchange/exchange-ps/exchange/Get-MailflowStatusReport.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md
rename to exchange/exchange-ps/exchange/Get-MailflowStatusReport.md
index c9ca311930..fef6949dce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md
+++ b/exchange/exchange-ps/exchange/Get-MailflowStatusReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mailflowstatusreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-MailFlowStatusReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mailflowstatusreport
-schema: 2.0.0
-title: Get-MailFlowStatusReport
+ms.reviewer:
---
# Get-MailFlowStatusReport
@@ -56,9 +55,6 @@ This example returns inbound and outbound messages were classified as GoodMail o
## PARAMETERS
### -Direction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Direction parameter filters the results by the direction of the message. Valid values are:
- Inbound
@@ -71,6 +67,7 @@ You can specify multiple value separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -80,15 +77,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -98,9 +93,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -109,6 +101,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -118,9 +111,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EventType parameter filters the report by the event type. Valid values are:
- EdgeBlockSpam
@@ -136,6 +126,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -145,15 +136,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -163,15 +152,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -181,15 +168,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -199,9 +184,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -210,6 +192,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md b/exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md
rename to exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md
index 5d133ef2fb..077860de6f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-MalwareFilterPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-malwarefilterpolicy
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-MalwareFilterPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-malwarefilterpolicy
-schema: 2.0.0
-title: Get-MalwareFilterPolicy
+ms.reviewer:
---
# Get-MalwareFilterPolicy
@@ -51,15 +50,13 @@ This example retrieves detailed configuration information for the malware filter
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the malware filter policy that you want to view. You can use any value that uniquely identifies the policy. For example, you can use the name, GUID or distinguished name (DN) of the malware filter policy.
```yaml
Type: MalwareFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -80,6 +74,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md b/exchange/exchange-ps/exchange/Get-MalwareFilterRule.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md
rename to exchange/exchange-ps/exchange/Get-MalwareFilterRule.md
index 9dece05188..d8b421d6ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md
+++ b/exchange/exchange-ps/exchange/Get-MalwareFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-malwarefilterrule
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-MalwareFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-malwarefilterrule
-schema: 2.0.0
-title: Get-MalwareFilterRule
+ms.reviewer:
---
# Get-MalwareFilterRule
@@ -50,15 +49,13 @@ This example retrieves detailed configuration information for the malware filter
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the malware filter rule that you want to view. You can use any value that uniquely identifies the rule. For example, you can use the name, GUID or distinguished name (DN) of the malware filter rule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -79,6 +73,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -88,15 +83,13 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The State parameter filters the results by enabled or disabled malware filter rules. Valid input for this parameter is Enabled or Disabled.
```yaml
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md b/exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md
rename to exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md
index 7cdc96ccc4..11a67a8298 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md
+++ b/exchange/exchange-ps/exchange/Get-MalwareFilteringServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-malwarefilteringserver
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MalwareFilteringServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-malwarefilteringserver
-schema: 2.0.0
-title: Get-MalwareFilteringServer
+ms.reviewer:
---
# Get-MalwareFilteringServer
@@ -49,9 +48,6 @@ This example returns the detailed Exchange Malware agent settings on a Mailbox s
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the server where you want to view the anti-malware settings. You can use any value that uniquely identifies the server. For example:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the server where you want to view the anti-malw
Type: MalwareFilteringServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -83,6 +77,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md b/exchange/exchange-ps/exchange/Get-ManagedContentSettings.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md
rename to exchange/exchange-ps/exchange/Get-ManagedContentSettings.md
index 38de7eef3b..543f807e2a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md
+++ b/exchange/exchange-ps/exchange/Get-ManagedContentSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-managedcontentsettings
applicable: Exchange Server 2010
+title: Get-ManagedContentSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-managedcontentsettings
-schema: 2.0.0
-title: Get-ManagedContentSettings
+ms.reviewer:
---
# Get-ManagedContentSettings
@@ -68,9 +67,6 @@ This example retrieves the managed content settings for the managed folder Inbox
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the name, distinguished name (DN), or GUID of the set of managed content settings. When used, this command retrieves the folder content settings and all associated attributes.
This parameter can't be used with the FolderName parameter.
@@ -79,6 +75,7 @@ This parameter can't be used with the FolderName parameter.
Type: ELCContentSettingsIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: 1
@@ -88,15 +85,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -106,9 +101,6 @@ Accept wildcard characters: False
```
### -FolderName
-
-> Applicable: Exchange Server 2010
-
The FolderName parameter specifies the name or GUID of the managed folder to which the managed content settings apply. When used, this command retrieves all the policies that apply to that folder.
This parameter can't be used with the Identity parameter.
@@ -117,6 +109,7 @@ This parameter can't be used with the Identity parameter.
Type: ELCFolderIdParameter
Parameter Sets: FolderName
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md b/exchange/exchange-ps/exchange/Get-ManagedFolder.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md
rename to exchange/exchange-ps/exchange/Get-ManagedFolder.md
index a3984883b9..f7a6302c2b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md
+++ b/exchange/exchange-ps/exchange/Get-ManagedFolder.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-managedfolder
applicable: Exchange Server 2010
+title: Get-ManagedFolder
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-managedfolder
-schema: 2.0.0
-title: Get-ManagedFolder
+ms.reviewer:
---
# Get-ManagedFolder
@@ -58,15 +57,13 @@ This example retrieves information about the managed folder MyManagedFolder. The
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the name, distinguished name (DN), or GUID of the managed folder.
```yaml
Type: ELCFolderIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: 1
@@ -76,15 +73,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -94,9 +89,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010
-
The Mailbox parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -116,6 +108,7 @@ This cmdlet retrieves all the folders that apply to the specified mailbox.
Type: MailboxIdParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md
rename to exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md
index 012ba3077b..773b53f264 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-ManagedFolderMailboxPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-managedfoldermailboxpolicy
applicable: Exchange Server 2010
+title: Get-ManagedFolderMailboxPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-managedfoldermailboxpolicy
-schema: 2.0.0
-title: Get-ManagedFolderMailboxPolicy
+ms.reviewer:
---
# Get-ManagedFolderMailboxPolicy
@@ -46,15 +45,13 @@ The Identity parameter is a positional parameter. Positional parameters can be u
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the name, distinguished name (DN), or GUID of the managed folder mailbox policy.
```yaml
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: 1
@@ -64,15 +61,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md b/exchange/exchange-ps/exchange/Get-ManagementRole.md
similarity index 83%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md
rename to exchange/exchange-ps/exchange/Get-ManagementRole.md
index fc7a39e6d1..72a4c467e8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md
+++ b/exchange/exchange-ps/exchange/Get-ManagementRole.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-managementrole
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-ManagementRole
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-managementrole
-schema: 2.0.0
-title: Get-ManagementRole
+ms.reviewer:
---
# Get-ManagementRole
@@ -113,15 +112,13 @@ This example lists the immediate children of the Mail Recipients role. Only the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the role you want to view. If the role you want to view contains spaces, enclose the name in quotation marks ("). You can use the wildcard character (\*) and a partial role name to match multiple roles.
```yaml
Type: RoleIdParameter
-Parameter Sets: GetChildren, Recurse, Identity, Script
+Parameter Sets: GetChildren, Recurse
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: 1
@@ -130,10 +127,20 @@ Accept pipeline input: True
Accept wildcard characters: False
```
-### -GetChildren
+```yaml
+Type: RoleIdParameter
+Parameter Sets: Identity, Script
+Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: True
+Accept wildcard characters: False
+```
+### -GetChildren
The GetChildren parameter retrieves a list of all the roles that were created based on the parent role specified in the Identity parameter. You don't need to specify a value with this switch.
Only the immediate child roles of the parent role are included in the results.
@@ -144,6 +151,7 @@ You can use this switch only with the Identity and RoleType parameters.
Type: SwitchParameter
Parameter Sets: GetChildren
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -153,9 +161,6 @@ Accept wildcard characters: False
```
### -Recurse
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Recurse parameter retrieves a list of all the roles that were created based on the parent role specified in the Identity parameter. You don't need to specify a value with this switch.
The role specified in the Identity parameter, its child roles, and their children are returned.
@@ -166,6 +171,7 @@ You can use this switch only with the Identity and RoleType parameters.
Type: SwitchParameter
Parameter Sets: Recurse
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -175,15 +181,13 @@ Accept wildcard characters: False
```
### -Cmdlet
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Cmdlet parameter returns a list of all roles that include the specified cmdlet.
```yaml
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -193,15 +197,13 @@ Accept wildcard characters: False
```
### -CmdletParameters
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The CmdletParameters parameter returns a list of all roles that include the specified parameter or parameters. You can specify more than one parameter by separating each parameter with a comma. If you specify multiple parameters, only the roles that include all of the specified parameters are returned.
```yaml
Type: String[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -211,9 +213,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -222,6 +221,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -231,15 +231,13 @@ Accept wildcard characters: False
```
### -RoleType
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The RoleType parameter returns a list of roles that match the specified role type. For a list of valid role types, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
```yaml
Type: RoleType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -249,15 +247,13 @@ Accept wildcard characters: False
```
### -Script
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Script parameter returns a list of all roles that include the specified script.
```yaml
Type: String
Parameter Sets: Script
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -267,15 +263,13 @@ Accept wildcard characters: False
```
### -ScriptParameters
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ScriptParameters parameter returns a list of all roles that include the specified parameter or parameters. You can specify more than one parameter by separating each parameter with a comma. If you specify multiple parameters, only the roles that include all of the specified parameters are returned.
```yaml
Type: String[]
Parameter Sets: Script
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md b/exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md
similarity index 86%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md
rename to exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md
index 31e8e41432..574baae033 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/exchange/Get-ManagementRoleAssignment.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-managementroleassignment
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-ManagementRoleAssignment
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-managementroleassignment
-schema: 2.0.0
-title: Get-ManagementRoleAssignment
+ms.reviewer:
---
# Get-ManagementRoleAssignment
@@ -132,15 +131,13 @@ This example retrieves all the role assignments that can modify the database Con
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the name of the role assignment to retrieve. If the name of the role assignment contains spaces, enclose it in quotation marks ("). If the RoleAssignee parameter is used, you can't use the Identity parameter.
```yaml
Type: RoleAssignmentIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -150,9 +147,6 @@ Accept wildcard characters: False
```
### -AssignmentMethod
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The AssignmentMethod parameter specifies the type of role assignment to include in the results returned by the cmdlet. You can specify one or more of the following values:
- Direct
@@ -168,6 +162,7 @@ You must specify a value with the RoleAssignee parameter if you use the Assignme
Type: AssignmentMethod[]
Parameter Sets: RoleAssignee
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -177,15 +172,13 @@ Accept wildcard characters: False
```
### -ConfigWriteScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConfigWriteScope parameter specifies the type of management configuration scope to include in the results returned by the cmdlet. The valid values are None, OrganizationConfig, CustomConfigScope, and ExclusiveConfigScope.
```yaml
Type: ConfigWriteScopeType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -195,9 +188,6 @@ Accept wildcard characters: False
```
### -CustomConfigWriteScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The CustomConfigWriteScope parameter returns only the regular role assignments that include the specified configuration-based regular scope.
@@ -210,6 +200,7 @@ If the scope name contains spaces, enclose it in quotation marks (").
Type: ManagementScopeIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -219,9 +210,6 @@ Accept wildcard characters: False
```
### -CustomRecipientWriteScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The CustomRecipientWriteScope parameter returns only the regular role assignments that include the specified recipient-based regular scope.
This parameter can only be used to retrieve regular recipient-based scopes. To retrieve a list of exclusive recipient-based scopes, use the ExclusiveRecipientWriteScope parameter instead.
@@ -232,6 +220,7 @@ If the scope name contains spaces, enclose it in quotation marks (").
Type: ManagementScopeIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -241,9 +230,6 @@ Accept wildcard characters: False
```
### -Delegating
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Delegating parameter specifies whether delegating or regular role assignments should be returned.
By default, both delegating and regular scopes are returned. To return only delegating role assignments, specify a value of $true. To return only regular role assignments, specify a value of $false.
@@ -252,6 +238,7 @@ By default, both delegating and regular scopes are returned. To return only dele
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -261,9 +248,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -272,6 +256,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -281,15 +266,13 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Enabled parameter specifies whether enabled or disabled role assignments should be returned. To return enabled role assignments, specify a value of $true. To return disabled role assignments, specify a value of $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -299,9 +282,6 @@ Accept wildcard characters: False
```
### -Exclusive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Exclusive parameter specifies whether exclusive or regular role assignments should be returned.
By default, both exclusive and regular scopes are returned. To return only exclusive role assignments, specify a value of $true. To return only regular role assignments, specify a value of $false.
@@ -310,6 +290,7 @@ By default, both exclusive and regular scopes are returned. To return only exclu
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -319,9 +300,6 @@ Accept wildcard characters: False
```
### -ExclusiveConfigWriteScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ExclusiveConfigWriteScope parameter returns only the exclusive role assignments that include the specified configuration-based exclusive scope.
@@ -334,6 +312,7 @@ If the scope name contains spaces, enclose it in quotation marks (").
Type: ManagementScopeIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -343,9 +322,6 @@ Accept wildcard characters: False
```
### -ExclusiveRecipientWriteScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ExclusiveRecipientWriteScope parameter returns only the exclusive role assignments that include the specified recipient-based exclusive scope.
This parameter can only be used to retrieve exclusive recipient-based scopes. To retrieve a list of regular recipient-based scopes, use the CustomRecipientWriteScope parameter instead.
@@ -356,6 +332,7 @@ If the scope name contains spaces, enclose it in quotation marks (").
Type: ManagementScopeIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -365,9 +342,6 @@ Accept wildcard characters: False
```
### -GetEffectiveUsers
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The GetEffectiveUsers switch specifies that the command should show the list of users in the role groups, role assignment policies, or USGs that are associated with the role assignment. You don't need to specify a value with this switch.
Effectively, users are associated with the role assignment through their role group, role assignment policy, or USG memberships.
@@ -376,6 +350,7 @@ Effectively, users are associated with the role assignment through their role gr
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -385,9 +360,6 @@ Accept wildcard characters: False
```
### -RecipientAdministrativeUnitScope
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is functional only in the cloud-based service.
The RecipientAdministrativeUnitScope parameter returns only the role assignments that include the specified administrative unit.
@@ -398,6 +370,7 @@ Administrative units are Microsoft Entra containers of resources. You can view t
Type: AdministrativeUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -407,9 +380,6 @@ Accept wildcard characters: False
```
### -RecipientGroupScope
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The RecipientGroupScope parameter returns only the role assignments that are scoped to groups. You can use any value that uniquely identifies the group: Name, DistinguishedName, GUID, DisplayName.
@@ -418,6 +388,7 @@ The RecipientGroupScope parameter returns only the role assignments that are sco
Type: GroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -427,15 +398,13 @@ Accept wildcard characters: False
```
### -RecipientOrganizationalUnitScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RecipientOrganizationalUnitScope parameter returns only the role assignments that include the specified organizational unit (OU). If the OU tree contains spaces, enclose it in quotation marks (").
```yaml
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -445,15 +414,13 @@ Accept wildcard characters: False
```
### -RecipientWriteScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RecipientWriteScope parameter returns only the role assignments associated with the recipient scope restriction type specified. The valid values are None, MyGAL, Self, OU, CustomRecipientScope, MyDistributionGroups and ExclusiveRecipientScope.
```yaml
Type: RecipientWriteScopeType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -463,15 +430,13 @@ Accept wildcard characters: False
```
### -Role
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Role parameter returns only the role assignments associated with the specified management role. If the name of the role contains spaces, enclose it in quotation marks (").
```yaml
Type: RoleIdParameter
Parameter Sets: RoleAssignee
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -481,9 +446,6 @@ Accept wildcard characters: False
```
### -RoleAssignee
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RoleAssignee parameter specifies the role group, assignment policy, user, or universal security group (USG) for which you want to view role assignments. If the RoleAssignee parameter is used, you can't use the Identity parameter.
By default, the command returns both direct role assignments to the role assignee and indirect role assignments granted to a role assignee through role groups or assignment policies.
@@ -494,6 +456,7 @@ If the name of the user or USG contains spaces, enclose it in quotation marks ("
Type: RoleAssigneeIdParameter
Parameter Sets: RoleAssignee
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -503,15 +466,13 @@ Accept wildcard characters: False
```
### -RoleAssigneeType
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RoleAssigneeType parameter specifies the type of role assignee to return. The valid values are User, SecurityGroup, RoleAssignmentPolicy, ForeignSecurityPrincipal, RoleGroup, LinkedRoleGroup and Computer.
```yaml
Type: RoleAssigneeType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -521,9 +482,6 @@ Accept wildcard characters: False
```
### -WritableDatabase
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The WritableDatabase parameter specifies the database object you want to test to determine which role assignments allow it to be modified. The command takes into account the roles and scopes associated with each role assignment. You can use any value that uniquely identifies the database. For example:
@@ -538,6 +496,7 @@ If you use this parameter with the GetEffectiveUsers switch, all the users who c
Type: DatabaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -547,9 +506,6 @@ Accept wildcard characters: False
```
### -WritableRecipient
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WritableRecipient parameter specifies the recipient object you want to test to determine which role assignments allow it to be modified. The command takes into account the roles and scopes associated with each role assignment. If the recipient name contains spaces, enclose it in quotation marks (").
If this parameter is used with the GetEffectiveUsers switch, all of the users who can modify the recipient object indirectly through role groups and USGs are also returned. Without the GetEffectiveUsers switch, only the role groups, users and USGs directly assigned the role assignment are returned.
@@ -558,6 +514,7 @@ If this parameter is used with the GetEffectiveUsers switch, all of the users wh
Type: GeneralRecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -567,9 +524,6 @@ Accept wildcard characters: False
```
### -WritableServer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The WritableServer parameter specifies the server object you want to test to determine which role assignments allow it to be modified. The command takes into account the roles and scopes associated with each role assignment.
@@ -587,6 +541,7 @@ If this parameter is used with the GetEffectiveUsers switch, all of the users wh
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md b/exchange/exchange-ps/exchange/Get-ManagementRoleEntry.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md
rename to exchange/exchange-ps/exchange/Get-ManagementRoleEntry.md
index 7c88254dd8..8ba8cccb05 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/exchange/Get-ManagementRoleEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-managementroleentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-ManagementRoleEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-managementroleentry
-schema: 2.0.0
-title: Get-ManagementRoleEntry
+ms.reviewer:
---
# Get-ManagementRoleEntry
@@ -64,9 +63,6 @@ This example retrieves the Tier 2 Help Desk\\Set-Mailbox role entry and pipes th
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the role entry that you want to view. This parameter uses the syntax: `\` (for example, `CustomRole\Set-Mailbox`).
For more information about how management role entries work, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
@@ -79,6 +75,7 @@ If the role entry name contains spaces, enclose the name in quotation marks (").
Type: RoleEntryIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -88,9 +85,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -99,6 +93,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -108,9 +103,6 @@ Accept wildcard characters: False
```
### -Parameters
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Parameters parameter includes only the role entries that contain the parameters specified. You can specify multiple parameters, separated by commas. You can use the wildcard character (\*) with partial parameter names to retrieve all parameters that match the value you specify.
This parameter is useful when you use the wildcard character (\*) with the value you specify in the Identity parameter.
@@ -119,6 +111,7 @@ This parameter is useful when you use the wildcard character (\*) with the value
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -128,15 +121,13 @@ Accept wildcard characters: False
```
### -PSSnapinName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The PSSnapinName parameter specifies the Windows PowerShell snap-in that contains the role entry to return. Use the Get-PSSnapin cmdlet to retrieve a list of available Windows PowerShell snap-ins.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -146,9 +137,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -157,6 +145,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -166,15 +155,13 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Type parameter specifies the type of role entry to return. The valid values for the Type parameter are any combination of the following parameters, separated by commas: Cmdlet, Script and ApplicationPermission.
```yaml
Type: ManagementRoleEntryType[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md b/exchange/exchange-ps/exchange/Get-ManagementScope.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md
rename to exchange/exchange-ps/exchange/Get-ManagementScope.md
index cc67cda634..38673e7eda 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md
+++ b/exchange/exchange-ps/exchange/Get-ManagementScope.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-managementscope
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-ManagementScope
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-managementscope
-schema: 2.0.0
-title: Get-ManagementScope
+ms.reviewer:
---
# Get-ManagementScope
@@ -69,15 +68,13 @@ This example retrieves a list of exclusive scopes.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the name of the management scope to return. If the management scope name contains spaces, enclose it in quotation marks (").
```yaml
Type: ManagementScopeIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -87,9 +84,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -98,6 +92,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -107,15 +102,13 @@ Accept wildcard characters: False
```
### -Exclusive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Exclusive parameter specifies whether exclusive scopes should be returned. If the Exclusive parameter isn't specified, regular scopes and exclusive scopes are returned. If the Exclusive parameter is set to $True, only exclusive scopes are returned. If the Exclusive parameter is set to $False, only regular scopes are returned. The valid values are $True and $False.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -125,15 +118,13 @@ Accept wildcard characters: False
```
### -Orphan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Orphan switch specifies whether to return only management scopes that aren't associated with role assignments. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md
rename to exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md
index 72586d4075..77a025f2c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mapivirtualdirectory
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MapiVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mapivirtualdirectory
-schema: 2.0.0
-title: Get-MapiVirtualDirectory
+ms.reviewer:
---
# Get-MapiVirtualDirectory
@@ -72,9 +71,6 @@ This example returns a summary list of all MAPI virtual directories in the clien
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the MAPI virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -89,6 +85,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -98,9 +95,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -114,6 +108,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -123,9 +118,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -134,6 +126,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -143,15 +136,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -161,9 +152,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013
-
This parameter is available only in Exchange Server 2013.
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
@@ -176,6 +164,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Message.md b/exchange/exchange-ps/exchange/Get-Message.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Message.md
rename to exchange/exchange-ps/exchange/Get-Message.md
index f9c313b9b5..634425d077 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Message.md
+++ b/exchange/exchange-ps/exchange/Get-Message.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-message
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-Message
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-message
-schema: 2.0.0
-title: Get-Message
+ms.reviewer:
---
# Get-Message
@@ -98,15 +97,13 @@ This example displays all messages queued on the server named Server01. The resu
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the message. Valid input for this parameter uses the syntax Server\\Queue\\MessageInteger or Queue\\MessageInteger or MessageInteger, for example, Mailbox01\\contoso.com\\5 or 10. For details about message identity, see [Message identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity).
```yaml
Type: MessageIdentity
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -116,15 +113,13 @@ Accept wildcard characters: False
```
### -BookmarkIndex
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BookmarkIndex parameter specifies the position in the result set where the displayed results start. The value of this parameter is a 1-based index in the total result set. The BookmarkIndex parameter can't be used with the BookmarkObject parameter.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -134,15 +129,13 @@ Accept wildcard characters: False
```
### -BookmarkObject
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BookmarkObject parameter specifies the object in the result set where the displayed results start. The BookmarkObject parameter can't be used with the BookmarkIndex parameter.
```yaml
Type: ExtensibleMessageInfo
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -152,9 +145,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Filter parameter specifies one or more messages by using OPATH filter syntax. The OPATH filter includes a message property name followed by a comparison operator and value (for example, `"FromAddress -like '*@contoso.com'"`). For details about filterable message properties and comparison operators, see [Properties of messages in queues](https://learn.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
You can specify multiple criteria by using the and comparison operator. Property values that aren't expressed as an integer must be enclosed in quotation marks (").
@@ -163,6 +153,7 @@ You can specify multiple criteria by using the and comparison operator. Property
Type: String
Parameter Sets: Filter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -172,15 +163,13 @@ Accept wildcard characters: False
```
### -IncludeBookmark
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeBookmark parameter specifies whether to include the bookmark object when the query results are displayed. The IncludeBookmark parameter is valid when it's used with the BookmarkObject or BookmarkIndex parameters. If you don't specify a value for the IncludeBookmark parameter, the default value of $true is used.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -190,9 +179,6 @@ Accept wildcard characters: False
```
### -IncludeComponentLatencyInfo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeComponentLatencyInfo switch specifies whether the information about component latency is included in the message properties. You don't need to specify a value with this switch.
If you include this switch, the message objects returned will include latency measurements for each Transport component that has contributed to the local server latency for each queued message.
@@ -201,6 +187,7 @@ If you include this switch, the message objects returned will include latency me
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -210,9 +197,6 @@ Accept wildcard characters: False
```
### -IncludeRecipientInfo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeRecipientInfo switch specifies whether to display the message recipients in the Recipients field. You don't need to specify a value with this switch.
If you don't include the IncludeRecipientInfo switch, the Recipients field is blank.
@@ -233,6 +217,7 @@ To display the extended recipient properties that are now stored in the $x varia
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -242,9 +227,6 @@ Accept wildcard characters: False
```
### -Queue
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Queue parameter specifies the identity of the queue that contains the messages that you want to display. Valid input for this parameter uses the syntax `\` or ``, for example, Mailbox01\\contoso.com or Unreachable. For details about queue identity, see the "Queue identity" section in [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity).
If you use the Queue parameter, you can't use the Identity, Filter or Server parameters.
@@ -253,6 +235,7 @@ If you use the Queue parameter, you can't use the Identity, Filter or Server par
Type: QueueIdentity
Parameter Sets: Queue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -262,15 +245,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -280,15 +261,13 @@ Accept wildcard characters: False
```
### -ReturnPageInfo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReturnPageInfo parameter is a hidden parameter. Use it to return information about the total number of results and the index of the first object of the current page. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -298,15 +277,13 @@ Accept wildcard characters: False
```
### -SearchForward
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SearchForward parameter specifies whether to search forward or backward in the result set. The default value is $true. This value causes the result page to be calculated forward from either the start of the result set or forward from a bookmark if specified.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -316,9 +293,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -334,6 +308,7 @@ You can use the Server parameter and the Filter parameter in the same command. Y
Type: ServerIdParameter
Parameter Sets: Filter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -343,9 +318,6 @@ Accept wildcard characters: False
```
### -SortOrder
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SortOrder parameter specifies an array of message properties used to control the sort order of the result set. Separate each property by using a comma. Prepend a plus sign (+) symbol to the beginning of the property name to display the results in ascending order. Prepend a minus sign (-) symbol to the beginning of the property name to display the results in descending order.
If you don't specify a sort order, the result set is displayed in ascending order by MessageIdentity integer.
@@ -354,6 +326,7 @@ If you don't specify a sort order, the result set is displayed in ascending orde
Type: QueueViewerSortOrderEntry[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md b/exchange/exchange-ps/exchange/Get-MessageCategory.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md
rename to exchange/exchange-ps/exchange/Get-MessageCategory.md
index b459f539f4..6cebfc35f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md
+++ b/exchange/exchange-ps/exchange/Get-MessageCategory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-messagecategory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MessageCategory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagecategory
-schema: 2.0.0
-title: Get-MessageCategory
+ms.reviewer:
---
# Get-MessageCategory
@@ -45,15 +44,13 @@ This example retrieves message categories from the mailbox User1.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name of the message category to be retrieved.
```yaml
Type: MessageCategoryIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -63,9 +60,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -74,6 +68,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -83,9 +78,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -103,6 +95,7 @@ The Mailbox parameter specifies the mailbox that you want to view. You can use a
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md b/exchange/exchange-ps/exchange/Get-MessageClassification.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md
rename to exchange/exchange-ps/exchange/Get-MessageClassification.md
index c2c3594d87..bfb6750a16 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md
+++ b/exchange/exchange-ps/exchange/Get-MessageClassification.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-messageclassification
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MessageClassification
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-messageclassification
-schema: 2.0.0
-title: Get-MessageClassification
+ms.reviewer:
---
# Get-MessageClassification
@@ -43,9 +42,6 @@ This example lists all message classifications in your organization.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the message classification that you want to view. You can use any value that uniquely identifies the message classification. For example:
- Name
@@ -56,6 +52,7 @@ The Identity parameter specifies the message classification that you want to vie
Type: MessageClassificationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -78,6 +72,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -87,15 +82,13 @@ Accept wildcard characters: False
```
### -IncludeLocales
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeLocales switch specifies whether to return message classification locale information in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md b/exchange/exchange-ps/exchange/Get-MessageTrace.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md
rename to exchange/exchange-ps/exchange/Get-MessageTrace.md
index a364e80569..fa030fd3a1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md
+++ b/exchange/exchange-ps/exchange/Get-MessageTrace.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetrace
applicable: Exchange Online, Exchange Online Protection
+title: Get-MessageTrace
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetrace
-schema: 2.0.0
-title: Get-MessageTrace
+ms.reviewer:
---
# Get-MessageTrace
@@ -16,7 +15,7 @@ title: Get-MessageTrace
This cmdlet is available only in the cloud-based service.
> [!NOTE]
-> This cmdlet is replaced by the [Get-MessageTraceV2](https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetracev2) cmdlet and will eventually be deprecated.
+> This cmdlet is replaced by the [Get-MessageTraceV2](https://learn.microsoft.com/powershell/module/exchange/get-messagetracev2) cmdlet and will eventually be deprecated.
Use the Get-MessageTrace cmdlet to trace messages as they pass through the cloud-based organization.
@@ -66,9 +65,6 @@ This example retrieves message trace information for messages sent by john@conto
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -77,6 +73,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -86,15 +83,13 @@ Accept wildcard characters: False
```
### -FromIP
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The FromIP parameter filters the results by the source IP address. For incoming messages, the value of FromIP is the public IP address of the SMTP email server that sent the message.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -104,15 +99,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -122,9 +115,6 @@ Accept wildcard characters: False
```
### -MessageTraceId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1).
The MessageTraceId value is also available in the output of the following cmdlets:
@@ -139,6 +129,7 @@ The MessageTraceId value is also available in the output of the following cmdlet
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -148,15 +139,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -166,15 +155,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -184,15 +171,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -202,15 +187,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -220,15 +203,13 @@ Accept wildcard characters: False
```
### -SenderAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -238,9 +219,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -249,6 +227,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -258,9 +237,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Status parameter filters the results by the delivery status of the message. Valid values for this parameter are:
- None: The message has no delivery status because it was rejected or redirected to a different recipient.
@@ -276,6 +252,7 @@ The Status parameter filters the results by the delivery status of the message.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -285,15 +262,13 @@ Accept wildcard characters: False
```
### -ToIP
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ToIP parameter filters the results by the destination IP address. For outgoing messages, the value of ToIP is the public IP address in the resolved MX record for the destination domain. For incoming messages to Exchange Online, the value is blank.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md b/exchange/exchange-ps/exchange/Get-MessageTraceDetail.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md
rename to exchange/exchange-ps/exchange/Get-MessageTraceDetail.md
index 86ce5348b6..2053d79a67 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md
+++ b/exchange/exchange-ps/exchange/Get-MessageTraceDetail.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetracedetail
applicable: Exchange Online, Exchange Online Protection
+title: Get-MessageTraceDetail
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetracedetail
-schema: 2.0.0
-title: Get-MessageTraceDetail
+ms.reviewer:
---
# Get-MessageTraceDetail
@@ -16,7 +15,7 @@ title: Get-MessageTraceDetail
This cmdlet is available only in the cloud-based service.
> [!NOTE]
-> This cmdlet is replaced by the [Get-MessageTraceDetailV2](https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetracedetailv2) cmdlet and will eventually be deprecated.
+> This cmdlet is replaced by the [Get-MessageTraceDetailV2](https://learn.microsoft.com/powershell/module/exchange/get-messagetracedetailv2) cmdlet and will eventually be deprecated.
Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message. Note that these detailed results are returned less quickly than the Get-MessageTrace results.
@@ -64,9 +63,6 @@ This example uses the Get-MessageTrace cmdlet to retrieve message trace informat
## PARAMETERS
### -MessageTraceId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1).
The MessageTraceId value is also available in the output of the following cmdlets:
@@ -81,6 +77,7 @@ The MessageTraceId value is also available in the output of the following cmdlet
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -90,15 +87,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientAddress parameter filters the results by the recipient's email address.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -108,9 +103,6 @@ Accept wildcard characters: False
```
### -Action
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -119,6 +111,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -128,9 +121,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -141,6 +131,7 @@ If don't use the StartDate and EndDate parameters, only data from the last 48 ho
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -150,9 +141,6 @@ Accept wildcard characters: False
```
### -Event
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Event parameter filters the report by the message event. The following are examples of common events:
- RECEIVE: The message was received by the service.
@@ -169,6 +157,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -178,15 +167,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -196,15 +183,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -214,15 +199,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -232,15 +215,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -250,15 +231,13 @@ Accept wildcard characters: False
```
### -SenderAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -268,9 +247,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -281,6 +257,7 @@ If don't use the StartDate and EndDate parameters, only data from the last 48 ho
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md b/exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md
rename to exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md
index 0c9ae55a19..78e1a37969 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md
+++ b/exchange/exchange-ps/exchange/Get-MessageTraceDetailV2.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetracedetailv2
applicable: Exchange Online
+title: Get-MessageTraceDetailV2
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetracedetailv2
-schema: 2.0.0
-title: Get-MessageTraceDetailV2
+ms.reviewer:
---
# Get-MessageTraceDetailV2
@@ -53,15 +52,13 @@ This example uses the Get-MessageTraceV2 cmdlet to retrieve message trace inform
## PARAMETERS
### -MessageTraceId
-
-> Applicable: Exchange Online
-
The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1).
```yaml
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 5
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online
-
The RecipientAddress parameter filters the results by the recipient's email address.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 6
@@ -89,9 +84,6 @@ Accept wildcard characters: False
```
### -Action
-
-> Applicable: Exchange Online
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -100,6 +92,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -109,9 +102,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2025 to specify September 1, 2025. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2025 5:00 PM".
@@ -122,6 +112,7 @@ If don't use the StartDate and EndDate parameters, only data from the last 48 ho
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 2
@@ -131,9 +122,6 @@ Accept wildcard characters: False
```
### -Event
-
-> Applicable: Exchange Online
-
The Event parameter filters the report by the message event. The following are examples of common events:
- RECEIVE: The message was received by the service.
@@ -150,6 +138,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 3
@@ -159,15 +148,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 4
@@ -177,15 +164,13 @@ Accept wildcard characters: False
```
### -SenderAddress
-
-> Applicable: Exchange Online
-
The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 7
@@ -195,9 +180,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2025 to specify September 1, 2025. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2025 5:00 PM".
@@ -208,6 +190,7 @@ If don't use the StartDate and EndDate parameters, only data from the last 48 ho
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 8
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md b/exchange/exchange-ps/exchange/Get-MessageTraceV2.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md
rename to exchange/exchange-ps/exchange/Get-MessageTraceV2.md
index 066f328ae0..f356876da6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md
+++ b/exchange/exchange-ps/exchange/Get-MessageTraceV2.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetracev2
applicable: Exchange Online
+title: Get-MessageTraceV2
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetracev2
-schema: 2.0.0
-title: Get-MessageTraceV2
+ms.reviewer:
---
# Get-MessageTraceV2
@@ -70,9 +69,6 @@ This example retrieves message trace information for messages sent by `john@cont
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2025 to specify September 1, 2025. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2025 5:00 PM".
@@ -81,6 +77,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -90,15 +87,13 @@ Accept wildcard characters: False
```
### -FromIP
-
-> Applicable: Exchange Online
-
The FromIP parameter filters the results by the source IP address. For incoming messages, the value of FromIP is the public IP address of the SMTP email server that sent the message.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 2
@@ -108,15 +103,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 3
@@ -126,9 +119,6 @@ Accept wildcard characters: False
```
### -MessageTraceId
-
-> Applicable: Exchange Online
-
The MessageTraceId parameter filters the results by the message trace ID value of the message. This GUID value is generated for every message that's processed by the system (for example, c20e0f7a-f06b-41df-fe33-08d9da155ac1).
The MessageTraceId value is also available in the output of the following cmdlets:
@@ -143,6 +133,7 @@ The MessageTraceId value is also available in the output of the following cmdlet
Type: System.Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 4
@@ -152,15 +143,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 5
@@ -170,9 +159,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. A valid value is from 1 to 5000. The default value is 1000.
**Note**: This parameter replaces the PageSize parameter that was available on the Get-MessageTrace cmdlet.
@@ -181,6 +167,7 @@ The ResultSize parameter specifies the maximum number of results to return. A va
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 6
@@ -190,15 +177,13 @@ Accept wildcard characters: False
```
### -SenderAddress
-
-> Applicable: Exchange Online
-
The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 7
@@ -208,9 +193,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2025 to specify September 1, 2025. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2025 5:00 PM".
@@ -219,6 +201,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 8
@@ -228,15 +211,13 @@ Accept wildcard characters: False
```
### -StartingRecipientAddress
-
-> Applicable: Exchange Online
-
The StartingRecipientAddress parameter is used with the EndDate parameter to query subsequent data for partial results while avoiding duplication. Query subsequent data by taking the **Recipient address** and **Received Time** values of the last record of the partial results and using them as the values for the StartingRecipientAddress and EndDate parameters respectively in the next query.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 9
@@ -246,9 +227,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Online
-
The Status parameter filters the results by the delivery status of the message. Valid values are:
- Delivered: The message was delivered to its destination.
@@ -266,6 +244,7 @@ You can separate multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 10
@@ -275,9 +254,6 @@ Accept wildcard characters: False
```
### -Subject
-
-> Applicable: Exchange Online
-
The Subject parameter filters the results by the subject of the message. If the value contains spaces, enclose the value in quotation marks (").
You specify how the value is evaluated in the message subject by using the SubjectFilterType parameter.
@@ -286,6 +262,7 @@ You specify how the value is evaluated in the message subject by using the Subje
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 11
@@ -295,9 +272,6 @@ Accept wildcard characters: False
```
### -SubjectFilterType
-
-> Applicable: Exchange Online
-
The SubjectFilterType parameter specifies how the value of the Subject parameter is evaluated. Valid values are:
- Contains
@@ -310,6 +284,7 @@ We recommend using StartsWith or EndsWith instead of Contains whenever possible.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 12
@@ -319,15 +294,13 @@ Accept wildcard characters: False
```
### -ToIP
-
-> Applicable: Exchange Online
-
The ToIP parameter filters the results by the destination IP address. For outgoing messages, the value of ToIP is the public IP address in the resolved MX record for the destination domain. For incoming messages to Exchange Online, the value is blank.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 13
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md b/exchange/exchange-ps/exchange/Get-MessageTrackingLog.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md
rename to exchange/exchange-ps/exchange/Get-MessageTrackingLog.md
index b31a70814c..877d2fd0a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md
+++ b/exchange/exchange-ps/exchange/Get-MessageTrackingLog.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetrackinglog
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MessageTrackingLog
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetrackinglog
-schema: 2.0.0
-title: Get-MessageTrackingLog
+ms.reviewer:
---
# Get-MessageTrackingLog
@@ -75,9 +74,6 @@ This example searches the message tracking logs on the Mailbox server named Mail
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -86,6 +82,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -95,9 +92,6 @@ Accept wildcard characters: False
```
### -End
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The End parameter specifies the end date and time of the date range. Message delivery information is returned up to, but not including, the specified date and time.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -106,6 +100,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -115,15 +110,13 @@ Accept wildcard characters: False
```
### -EventId
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The EventId parameter filters the message tracking log entries by the value of the EventId field. The EventId value classifies each message event. Example values include DSN, Defer, Deliver, Send, or Receive.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -133,9 +126,6 @@ Accept wildcard characters: False
```
### -InternalMessageId
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The InternalMessageId parameter filters the message tracking log entries by the value of the InternalMessageId field. The InternalMessageId value is a message identifier that's assigned by the Exchange server that's currently processing the message.
The value of the internal-message-id for a specific message is different in the message tracking log of every Exchange server that's involved in the delivery of the message.
@@ -144,6 +134,7 @@ The value of the internal-message-id for a specific message is different in the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -153,15 +144,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MessageId parameter filters the message tracking log entries by the value of the MessageId field. The value of MessageId corresponds to the value of the Message-Id: header field in the message. If the Message-ID header field is blank or doesn't exist, an arbitrary value is assigned. Be sure to include the full MessageId string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -171,15 +160,13 @@ Accept wildcard characters: False
```
### -MessageSubject
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MessageSubject parameter filters the message tracking log entries by the value of the message subject. The value of the MessageSubject parameter automatically supports partial matches without using wildcards or special characters. For example, if you specify the MessageSubject value sea, the results include messages with Seattle in the subject. By default, message subjects are stored in the message tracking logs.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -189,15 +176,13 @@ Accept wildcard characters: False
```
### -Recipients
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Recipients parameter filters the message tracking log entries by the SMTP email address of the message recipients. Multiple recipients in a single message are logged in a single message tracking log entry. Unexpanded distribution group recipients are logged by using the group's SMTP email address. You can specify multiple recipients using an array of email addresses.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -207,15 +192,13 @@ Accept wildcard characters: False
```
### -Reference
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Reference parameter filters the message tracking log entries by the value of the Reference field. The Reference field contains additional information for specific types of events. For example, the Reference field value for a DSN message tracking entry contains the InternalMessageId value of the message that caused the DSN. For many types of events, the value of Reference is blank.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -225,15 +208,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -243,15 +224,13 @@ Accept wildcard characters: False
```
### -Sender
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Sender parameter filters the message tracking log entries by the sender's SMTP email address.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -261,9 +240,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -277,6 +253,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -286,9 +263,6 @@ Accept wildcard characters: False
```
### -Start
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Start parameter specifies the start date and time of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -297,6 +271,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -306,15 +281,13 @@ Accept wildcard characters: False
```
### -NetworkMessageId
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The NetworkMessageId parameter filters the message tracking log entries by the value of the NetworkMessageId field. This field contains a unique message ID value that persists across copies of the message that may be created due to bifurcation or distribution group expansion. An example value is 1341ac7b13fb42ab4d4408cf7f55890f.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -324,15 +297,13 @@ Accept wildcard characters: False
```
### -Source
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Source parameter filters the message tracking log entries by the value of the Source field. These values indicate the transport component that's responsible for the message tracking event. For more information, see [Source values in the message tracking log](https://learn.microsoft.com/Exchange/mail-flow/transport-logs/message-tracking#source-values-in-the-message-tracking-log).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -342,15 +313,13 @@ Accept wildcard characters: False
```
### -TransportTrafficType
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The TransportTrafficType parameter filters the message tracking log entries by the value of the TransportTrafficType field. However, this field isn't interesting for on-premises Exchange organizations.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md b/exchange/exchange-ps/exchange/Get-MessageTrackingReport.md
similarity index 86%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md
rename to exchange/exchange-ps/exchange/Get-MessageTrackingReport.md
index 6ab8dab4b6..fe0eb16c93 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md
+++ b/exchange/exchange-ps/exchange/Get-MessageTrackingReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-messagetrackingreport
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MessageTrackingReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetrackingreport
-schema: 2.0.0
-title: Get-MessageTrackingReport
+ms.reviewer:
---
# Get-MessageTrackingReport
@@ -39,7 +38,7 @@ Get-MessageTrackingReport [-Identity]
```
## DESCRIPTION
-This cmdlet requires the ID for the message tracking report that you want to view. Therefore, first you need to use the Search-MessageTrackingReport cmdlet to find the message tracking report ID for a specific message, and then pass the results to this cmdlet. For more information, see [Search-MessageTrackingReport](https://learn.microsoft.com/powershell/module/exchangepowershell/search-messagetrackingreport).
+This cmdlet requires the ID for the message tracking report that you want to view. Therefore, first you need to use the Search-MessageTrackingReport cmdlet to find the message tracking report ID for a specific message, and then pass the results to this cmdlet. For more information, see [Search-MessageTrackingReport](https://learn.microsoft.com/powershell/module/exchange/search-messagetrackingreport).
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
@@ -68,9 +67,6 @@ This example searches the message tracking data for the specific message trackin
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the message tracking report ID that you want to view.
You need to run the Search-MessageTrackingReport cmdlet to find the message tracking report ID for the specific message that you're tracking, and then pass the value of the MessageTrackingReportID field to this parameter.
@@ -79,6 +75,7 @@ You need to run the Search-MessageTrackingReport cmdlet to find the message trac
Type: MessageTrackingReportId
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -88,9 +85,6 @@ Accept wildcard characters: False
```
### -BypassDelegateChecking
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BypassDelegateChecking switch allows Help desk staff and administrators to retrieve message tracking reports for any user. You don't need to specify a value with this switch.
By default, each user can only see the message tracking reports for messages that they send or receive from their own mailbox. When you use this switch, you can view the message tracking reports for message exchanges among other users.
@@ -99,6 +93,7 @@ By default, each user can only see the message tracking reports for messages tha
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -108,9 +103,6 @@ Accept wildcard characters: False
```
### -DetailLevel
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DetailLevel parameter specifies the amount of detail to return in the results. Valid values are:
- Basic: Simple delivery report information is returned, which is more appropriate for users.
@@ -120,6 +112,7 @@ The DetailLevel parameter specifies the amount of detail to return in the result
Type: MessageTrackingDetailLevel
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -129,15 +122,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -147,9 +138,6 @@ Accept wildcard characters: False
```
### -DoNotResolve
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DoNotResolve switch specifies whether to prevent the resolution of email addresses to display names. You don't need to specify a value with this switch.
Using this switch improves performance, but the lack of display names might make the results more difficult to interpret.
@@ -158,6 +146,7 @@ Using this switch improves performance, but the lack of display names might make
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -167,15 +156,13 @@ Accept wildcard characters: False
```
### -RecipientPathFilter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RecipientPathFilter parameter specifies the email address of the recipient when you use the ReportTemplate parameter with the value RecipientPath.
```yaml
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -185,15 +172,13 @@ Accept wildcard characters: False
```
### -Recipients
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Recipients parameter specifies the email addresses of the recipients when you use the ReportTemplate parameter with the value Summary. You can specify multiple email addresses separated by commas.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -203,9 +188,6 @@ Accept wildcard characters: False
```
### -ReportTemplate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReportTemplate parameter specifies a predefined format for the output. Valid values are:
- RecipientPath: Returns a detailed tracking report for one recipient of the message. You specify the recipient by using the RecipientPathFilter parameter.
@@ -215,6 +197,7 @@ The ReportTemplate parameter specifies a predefined format for the output. Valid
Type: ReportTemplate
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -224,15 +207,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -242,9 +223,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Status parameter filters the results by the specified delivery status codes. Valid values are:
- Delivered
@@ -257,6 +235,7 @@ The Status parameter filters the results by the specified delivery status codes.
Type: _DeliveryStatus
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -266,9 +245,6 @@ Accept wildcard characters: False
```
### -TraceLevel
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TraceLevel parameter specifies the details to include in the results. Valid values are:
- Low: Minimal additional data is returned, including servers that were accessed, timing, message tracking search result counts and any error information.
@@ -281,6 +257,7 @@ You only need to use this parameter for troubleshooting message tracking issues.
Type: TraceLevel
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md b/exchange/exchange-ps/exchange/Get-MigrationBatch.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md
rename to exchange/exchange-ps/exchange/Get-MigrationBatch.md
index 0739a81f91..ecc0d0aa97 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md
+++ b/exchange/exchange-ps/exchange/Get-MigrationBatch.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationbatch
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MigrationBatch
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-migrationbatch
-schema: 2.0.0
-title: Get-MigrationBatch
+ms.reviewer:
---
# Get-MigrationBatch
@@ -101,9 +100,6 @@ This example displays information about all migration batches associated with th
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter identifies the name of the current migration batch. The value for this parameter is specified by the Name parameter of the New-MigrationBatch cmdlet.
If you use this parameter, you can't include the Endpoint parameter.
@@ -112,6 +108,7 @@ If you use this parameter, you can't include the Endpoint parameter.
Type: MigrationBatchIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -121,9 +118,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
@@ -134,6 +128,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: Identity, BatchesFromEndpoint
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -143,9 +138,6 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -154,6 +146,7 @@ The DiagnosticArgument parameter modifies the results that are returned by using
Type: String
Parameter Sets: Identity, BatchesFromEndpoint
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -163,9 +156,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems. Valid values are:
@@ -194,6 +184,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: Identity, BatchesByEndpoint, BatchesByStatus
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -203,9 +194,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -214,6 +202,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: Identity, BatchesFromEndpoint
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -223,9 +212,6 @@ Accept wildcard characters: False
```
### -Endpoint
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Endpoint parameter returns a list of migration batches associated with the specified migration endpoint.
If you use this parameter, you can't include the Identity parameter.
@@ -234,6 +220,7 @@ If you use this parameter, you can't include the Identity parameter.
Type: MigrationEndpointIdParameter
Parameter Sets: BatchesFromEndpoint, BatchesByEndpoint
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -243,9 +230,6 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeReport switch returns additional information about the specified migration batch. You don't need to specify a value with this switch.
This information is displayed in the Report field.
@@ -254,6 +238,7 @@ This information is displayed in the Report field.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -263,9 +248,6 @@ Accept wildcard characters: False
```
### -Partition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -274,6 +256,7 @@ This parameter is reserved for internal Microsoft use.
Type: MailboxIdParameter
Parameter Sets: Identity, BatchesByEndpoint, BatchesByStatus
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -283,9 +266,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -294,6 +274,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: Identity, BatchesByEndpoint, BatchesByStatus
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -303,9 +284,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Status parameter returns a list of migration batches that have the specified status state. Use one of the following values:
- Completed
@@ -328,6 +306,7 @@ The Status parameter returns a list of migration batches that have the specified
Type: MMigrationBatchStatus
Parameter Sets: Identity, BatchesFromEndpoint, BatchesByStatus
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md b/exchange/exchange-ps/exchange/Get-MigrationConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
rename to exchange/exchange-ps/exchange/Get-MigrationConfig.md
index 6129685733..1d8997faf8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
+++ b/exchange/exchange-ps/exchange/Get-MigrationConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationconfig
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MigrationConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-migrationconfig
-schema: 2.0.0
-title: Get-MigrationConfig
+ms.reviewer:
---
# Get-MigrationConfig
@@ -56,9 +55,6 @@ This example retrieves the settings for the migration configuration.
## PARAMETERS
### -AllPartitions
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill AllPartitions Description }}
@@ -67,6 +63,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: AllPartitions
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -76,9 +73,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -87,6 +81,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: Default
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -96,9 +91,6 @@ Accept wildcard characters: False
```
### -IncludeSimplifiedGmailMigrationData
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeSimplifiedGmailMigrationData Description }}
@@ -107,6 +99,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Partition, AllPartitions
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -Partition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -127,6 +117,7 @@ This parameter is reserved for internal Microsoft use.
Type: MailboxIdParameter
Parameter Sets: Partition
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md b/exchange/exchange-ps/exchange/Get-MigrationEndpoint.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md
rename to exchange/exchange-ps/exchange/Get-MigrationEndpoint.md
index 44e621ed39..8f8f5dd3c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md
+++ b/exchange/exchange-ps/exchange/Get-MigrationEndpoint.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationendpoint
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MigrationEndpoint
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-migrationendpoint
-schema: 2.0.0
-title: Get-MigrationEndpoint
+ms.reviewer:
---
# Get-MigrationEndpoint
@@ -81,15 +80,13 @@ This example retrieves the settings for the migration endpoint, OnboardingME01.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name of the migration endpoint you want to retrieve settings for.
```yaml
Type: MigrationEndpointIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -99,9 +96,6 @@ Accept wildcard characters: False
```
### -ConnectionSettings
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConnectionSettings parameter specifies the configuration settings of source or target servers for which you want to find a matching endpoint.
@@ -110,6 +104,7 @@ The ConnectionSettings parameter specifies the configuration settings of source
Type: ExchangeConnectionSettings
Parameter Sets: ConnectionSettingsFilter
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -119,9 +114,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
@@ -132,6 +124,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,9 +134,6 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -152,6 +142,7 @@ The DiagnosticArgument parameter modifies the results that are returned by using
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -161,9 +152,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems. Valid values are:
@@ -192,6 +180,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -201,9 +190,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -212,6 +198,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -221,9 +208,6 @@ Accept wildcard characters: False
```
### -Partition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -232,6 +216,7 @@ This parameter is reserved for internal Microsoft use.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -241,9 +226,6 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Type parameter filters the results by the type of migration. Valid values for this parameter are:
- ExchangeOutlookAnywhere: Cutover or staged Exchange migrations
@@ -255,6 +237,7 @@ The Type parameter filters the results by the type of migration. Valid values fo
Type: MigrationType
Parameter Sets: TypeFilter
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md b/exchange/exchange-ps/exchange/Get-MigrationStatistics.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md
rename to exchange/exchange-ps/exchange/Get-MigrationStatistics.md
index a039591098..c397c884ee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MigrationStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationstatistics
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MigrationStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-migrationstatistics
-schema: 2.0.0
-title: Get-MigrationStatistics
+ms.reviewer:
---
# Get-MigrationStatistics
@@ -45,9 +44,6 @@ This example returns the default statistics for the migration batches.
## PARAMETERS
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
@@ -58,6 +54,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -78,6 +72,7 @@ The DiagnosticArgument parameter modifies the results that are returned by using
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -87,9 +82,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems. Valid values are:
@@ -118,6 +110,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -127,9 +120,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -138,6 +128,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -147,9 +138,6 @@ Accept wildcard characters: False
```
### -Partition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -158,6 +146,7 @@ This parameter is reserved for internal Microsoft use.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md b/exchange/exchange-ps/exchange/Get-MigrationUser.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md
rename to exchange/exchange-ps/exchange/Get-MigrationUser.md
index 3539caf558..e379851050 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md
+++ b/exchange/exchange-ps/exchange/Get-MigrationUser.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationuser
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MigrationUser
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-migrationuser
-schema: 2.0.0
-title: Get-MigrationUser
+ms.reviewer:
---
# Get-MigrationUser
@@ -97,15 +96,13 @@ This example retrieves more detailed information about any ongoing migration for
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the particular ongoing migration that you want to retrieve information about. The Identity parameter is usually represented as an email address.
```yaml
Type: MigrationUserIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -115,15 +112,13 @@ Accept wildcard characters: False
```
### -MailboxGuid
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MailboxGuid parameter specifies the GUID of a mailbox for which you want to view the migration information.
```yaml
Type: Guid
Parameter Sets: MailboxGuid
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -133,15 +128,13 @@ Accept wildcard characters: False
```
### -BatchId
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BatchId parameter specifies the name of the migration batch for which you want to return users.
```yaml
Type: MigrationBatchIdParameter
Parameter Sets: StatusAndBatchId
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -151,9 +144,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -162,6 +152,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -171,15 +162,13 @@ Accept wildcard characters: False
```
### -EmailAddress
-
-> Applicable: Exchange Online
-
The EmailAddress parameter specifies the particular user that you want to retrieve information about. The EmailAddress parameter is represented as an email address. This parameter is available only in the cloud-based service.
```yaml
Type: EmailAddress
Parameter Sets: EmailAddress
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -189,9 +178,6 @@ Accept wildcard characters: False
```
### -IncludeAssociatedUsers
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeAssociatedUsers Description }}
@@ -200,6 +186,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -209,9 +196,6 @@ Accept wildcard characters: False
```
### -Partition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -220,6 +204,7 @@ This parameter is reserved for internal Microsoft use.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -229,15 +214,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -247,9 +230,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Status parameter returns information about migration users that have the specified status state. Use one of the following values:
- Completed
@@ -278,6 +258,7 @@ The Status parameter returns information about migration users that have the spe
Type: MigrationUserStatus
Parameter Sets: StatusAndBatchId
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -287,9 +268,6 @@ Accept wildcard characters: False
```
### -StatusSummary
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The StatusSummary parameter returns abbreviated information about migration users that have the specified status value. Use one of the following values:
- Active
@@ -302,6 +280,7 @@ The StatusSummary parameter returns abbreviated information about migration user
Type: MigrationUserStatusSummary
Parameter Sets: StatusAndBatchId
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md b/exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md
rename to exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md
index 98b51272c1..5e64b3de72 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-migrationuserstatistics
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MigrationUserStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-migrationuserstatistics
-schema: 2.0.0
-title: Get-MigrationUserStatistics
+ms.reviewer:
---
# Get-MigrationUserStatistics
@@ -86,15 +85,13 @@ In on-premises Exchange, this example uses the Diagnostic parameter to display d
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the user that you want to retrieve migration information about. Use an email address as the value for this parameter.
```yaml
Type: MigrationUserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -104,9 +101,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
@@ -117,6 +111,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -126,9 +121,6 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -137,6 +129,7 @@ The DiagnosticArgument parameter modifies the results that are returned by using
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -146,9 +139,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -157,6 +147,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -166,9 +157,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -177,6 +165,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -186,9 +175,6 @@ Accept wildcard characters: False
```
### -IncludeCopilotReport
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeCopilotReport Description }}
@@ -197,6 +183,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -206,15 +193,13 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -224,15 +209,13 @@ Accept wildcard characters: False
```
### -IncludeSkippedItems
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeSkippedItems switch specifies whether to include skipped items for the user. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -242,15 +225,13 @@ Accept wildcard characters: False
```
### -LimitSkippedItemsTo
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The LimitSkippedItemsTo parameter specifies the maximum number of skipped items to display information about in the SkippedItems property in command output. For example, if this parameter is set to 5, the cmdlet returns information for up to five skipped items for the specified user, even if there are more than five skipped items.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -260,9 +241,6 @@ Accept wildcard characters: False
```
### -Partition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -271,6 +249,7 @@ This parameter is reserved for internal Microsoft use.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -280,15 +259,13 @@ Accept wildcard characters: False
```
### -SkipSubscription
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SkipSubscription switch specifies whether to skip loading the subscription for the user. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md b/exchange/exchange-ps/exchange/Get-MobileDevice.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md
rename to exchange/exchange-ps/exchange/Get-MobileDevice.md
index f0dcc63610..7da6e04fbb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md
+++ b/exchange/exchange-ps/exchange/Get-MobileDevice.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mobiledevice
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MobileDevice
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mobiledevice
-schema: 2.0.0
-title: Get-MobileDevice
+ms.reviewer:
---
# Get-MobileDevice
@@ -84,9 +83,6 @@ This example returns detailed information about the specified device on Lila's m
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mobile device that you want to view. You can use the following values that uniquely identifies the mobile device:
- Identity (`\ExchangeActiveSyncDevices\` for example, `CarlosM\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac`)
@@ -97,6 +93,7 @@ The Identity parameter specifies the mobile device that you want to view. You ca
Type: MobileDeviceIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -106,9 +103,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter filters the results by mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -128,6 +122,7 @@ You can't use this parameter with the Identity parameter.
Type: MailboxIdParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -137,15 +132,13 @@ Accept wildcard characters: False
```
### -ActiveSync
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ActiveSync switch filters the results by Exchange ActiveSync devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -155,9 +148,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -166,6 +156,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -175,9 +166,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -214,6 +202,7 @@ You can filter by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -223,9 +212,6 @@ Accept wildcard characters: False
```
### -Monitoring
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Monitoring switch is required to return monitoring mailboxes in the results. You don't need to specify a value with this switch.
@@ -236,6 +222,7 @@ Monitoring mailboxes are associated with managed availability and the Exchange H
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -245,9 +232,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -259,6 +243,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -268,15 +253,13 @@ Accept wildcard characters: False
```
### -OWAforDevices
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OWAforDevices switch filters the results by whether Outlook on the web for devices is enabled for the device. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -286,15 +269,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -304,9 +285,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -333,6 +311,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -342,15 +321,13 @@ Accept wildcard characters: False
```
### -RestApi
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RestApi switch filters the results by REST API devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -360,15 +337,13 @@ Accept wildcard characters: False
```
### -UniversalOutlook
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The UniversalOutlook switch filters the results by Mail and Calendar devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md
rename to exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md
index 61bdb004a8..5a1d4c078b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mobiledevicemailboxpolicy
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MobileDeviceMailboxPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mobiledevicemailboxpolicy
-schema: 2.0.0
-title: Get-MobileDeviceMailboxPolicy
+ms.reviewer:
---
# Get-MobileDeviceMailboxPolicy
@@ -51,15 +50,13 @@ This example returns the policy settings for the Mobile Device mailbox policy De
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the policy name.
```yaml
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -80,6 +74,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md b/exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md
rename to exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md
index 9e800bcd46..d493f60367 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mobiledevicestatistics
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MobileDeviceStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mobiledevicestatistics
-schema: 2.0.0
-title: Get-MobileDeviceStatistics
+ms.reviewer:
---
# Get-MobileDeviceStatistics
@@ -88,9 +87,6 @@ This example retrieves the statistics for the mobile phone that's configured to
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mobile device that you want to view. You can use the following values that uniquely identifies the mobile device:
- Identity (`\ExchangeActiveSyncDevices\` for example, `CarlosM\ExchangeActiveSyncDevices\REST§Outlook§5eec4e941e0748a264512fd83770d5ac`)
@@ -103,6 +99,7 @@ You can't use this parameter with the Mailbox parameter.
Type: MobileDeviceIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -112,9 +109,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter filters the results by the user mailbox that's associated with the mobile device. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -134,6 +128,7 @@ You can't use this parameter with the Identity parameter.
Type: MailboxIdParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -143,15 +138,13 @@ Accept wildcard characters: False
```
### -ActiveSync
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ActiveSync switch filters the results by Exchange ActiveSync devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -161,9 +154,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -172,6 +162,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -181,15 +172,13 @@ Accept wildcard characters: False
```
### -GetMailboxLog
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The GetMailboxLog switch specifies whether to send the mobile device statistics to the email addresses that are specified by the NotificationEmailAddresses parameter. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -199,9 +188,6 @@ Accept wildcard characters: False
```
### -NotificationEmailAddresses
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The NotificationEmailAddresses parameter specifies a comma-separated list of email addresses to receive the mobile device statistics when you use the GetMailboxLog switch.
This parameter is meaningful only if you also use the GetMailboxLog switch in the same command.
@@ -210,6 +196,7 @@ This parameter is meaningful only if you also use the GetMailboxLog switch in th
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -219,15 +206,13 @@ Accept wildcard characters: False
```
### -OWAforDevices
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OWAforDevices switch filters the results by devices where Outlook on the web for devices is enabled. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -237,15 +222,13 @@ Accept wildcard characters: False
```
### -ShowRecoveryPassword
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ShowRecoveryPassword switch specifies whether to return the recovery password for the mobile device as one of the displayed statistics. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -255,15 +238,13 @@ Accept wildcard characters: False
```
### -RestApi
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RestApi switch filters the results by REST API devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -273,15 +254,13 @@ Accept wildcard characters: False
```
### -UniversalOutlook
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The UniversalOutlook switch filters the results by Mail and Calendar devices. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -291,9 +270,6 @@ Accept wildcard characters: False
```
### -UseCustomRouting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UseCustomRouting Description }}
@@ -302,6 +278,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md b/exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md
rename to exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md
index d7d517597e..b720090806 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md
+++ b/exchange/exchange-ps/exchange/Get-MonitoringItemHelp.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-monitoringitemhelp
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MonitoringItemHelp
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-monitoringitemhelp
-schema: 2.0.0
-title: Get-MonitoringItemHelp
+ms.reviewer:
---
# Get-MonitoringItemHelp
@@ -41,15 +40,13 @@ This example retrieves health set information for a monitoring item on the serve
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the monitoring item. The parameter uses the syntax: `\[\]`. You can find the available values in the Identity property of the output of the Get-MonitoringItem cmdlet.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -59,9 +56,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that contains the monitoring item. You can use any value that uniquely identifies the server. For example:
- Name
@@ -73,6 +67,7 @@ The Server parameter specifies the Exchange server that contains the monitoring
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md b/exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md
rename to exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md
index ca5cfa71ed..993413da94 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md
+++ b/exchange/exchange-ps/exchange/Get-MonitoringItemIdentity.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-monitoringitemidentity
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-MonitoringItemIdentity
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-monitoringitemidentity
-schema: 2.0.0
-title: Get-MonitoringItemIdentity
+ms.reviewer:
---
# Get-MonitoringItemIdentity
@@ -41,15 +40,13 @@ This example returns information about the health set named OutlookMapiHttp.Prox
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the health set that you want to view. To see the list of available health sets, you can use the Get-ServerHealth or Get-HealthReport cmdlets.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -59,9 +56,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that contains the health set. You can use any value that uniquely identifies the server. For example:
- Name
@@ -73,6 +67,7 @@ The Server parameter specifies the Exchange server that contains the health set.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md b/exchange/exchange-ps/exchange/Get-MoveRequest.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md
rename to exchange/exchange-ps/exchange/Get-MoveRequest.md
index b38430ed75..9bd1b19333 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md
+++ b/exchange/exchange-ps/exchange/Get-MoveRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-moverequest
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MoveRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-moverequest
-schema: 2.0.0
-title: Get-MoveRequest
+ms.reviewer:
---
# Get-MoveRequest
@@ -89,9 +88,6 @@ This example retrieves the status of move requests in the FromDB01ToDB02 batch t
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the move request, which is the identity of the mailbox or mail user. You can use any value that uniquely identifies the mailbox or mail user. For example:
- Name
@@ -122,6 +118,7 @@ You can use this parameter with the following parameters:
Type: MoveRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -131,9 +128,6 @@ Accept wildcard characters: False
```
### -BatchName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BatchName parameter specifies the name that was given to a batch move request.
You can't use this parameter with the Identity parameter.
@@ -142,6 +136,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -151,9 +146,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -164,6 +156,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -173,9 +166,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -184,6 +174,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -193,9 +184,6 @@ Accept wildcard characters: False
```
### -Flags
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Flags parameter specifies the move type to retrieve information for. The following values may be used:
- CrossOrg
@@ -219,6 +207,7 @@ The Flags parameter specifies the move type to retrieve information for. The fol
Type: RequestFlags
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -228,9 +217,6 @@ Accept wildcard characters: False
```
### -HighPriority
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The HighPriority parameter specifies that the cmdlet returns requests that were created with the HighPriority flag. The HighPriority flag indicates that the request should be processed before other lower priority requests in the queue.
@@ -241,6 +227,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -250,9 +237,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedObjects
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IncludeSoftDeletedObjects parameter specifies whether to return mailboxes that have been soft deleted. This parameter accepts $true or $false.
@@ -261,6 +245,7 @@ The IncludeSoftDeletedObjects parameter specifies whether to return mailboxes th
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -270,9 +255,6 @@ Accept wildcard characters: False
```
### -MoveStatus
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MoveStatus parameter returns move requests in the specified status. You can use the following values:
- AutoSuspended
@@ -291,6 +273,7 @@ You can't use this parameter with the Identity parameter.
Type: RequestStatus
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -300,9 +283,6 @@ Accept wildcard characters: False
```
### -Offline
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Offline parameter specifies whether to return mailboxes that are being moved in offline mode. This parameter accepts $true or $false.
You can't use this parameter with the Identity parameter.
@@ -311,6 +291,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -320,9 +301,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -334,6 +312,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -343,9 +322,6 @@ Accept wildcard characters: False
```
### -Protect
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Protect parameter returns mailboxes being moved in protected mode. This parameter accepts $true or $false.
@@ -356,6 +332,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -365,9 +342,6 @@ Accept wildcard characters: False
```
### -ProxyToMailbox
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The ProxyToMailbox parameter filters the results by the location of the specified mailbox (also known as proxying). You can use any value that uniquely identifies the mailbox. For example:
@@ -387,6 +361,7 @@ The ProxyToMailbox parameter filters the results by the location of the specifie
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -396,9 +371,6 @@ Accept wildcard characters: False
```
### -RemoteHostName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RemoteHostName parameter specifies the FQDN of the cross-forest organization from which you're moving the mailbox.
You can't use this parameter with the Identity parameter.
@@ -407,6 +379,7 @@ You can't use this parameter with the Identity parameter.
Type: Fqdn
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -416,15 +389,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -434,9 +405,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -451,6 +419,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -460,9 +429,6 @@ Accept wildcard characters: False
```
### -SourceDatabase
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The SourceDatabase parameter returns all mailboxes that are being moved from the specified source mailbox database. You can use any value that uniquely identifies the database. For example:
@@ -477,6 +443,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -486,9 +453,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The Status parameter filters the results by status. Valid values are:
@@ -509,6 +473,7 @@ The Status parameter filters the results by status. Valid values are:
Type: RequestStatus
Parameter Sets: Filtering
Aliases: MoveStatus
+Applicable: Exchange Online
Required: False
Position: Named
@@ -518,9 +483,6 @@ Accept wildcard characters: False
```
### -Suspend
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Suspend parameter specifies whether to return mailboxes with moves that have been suspended. This parameter accepts $true or $false.
You can't use this parameter with the Identity parameter.
@@ -529,6 +491,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -538,9 +501,6 @@ Accept wildcard characters: False
```
### -SuspendWhenReadyToComplete
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SuspendWhenReadytoComplete parameter specifies whether to return mailboxes that have been moved with the New-MoveRequest command and its SuspendWhenReadyToComplete switch. This parameter accepts $true or $false.
You can't use this parameter with the Identity parameter.
@@ -549,6 +509,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -558,9 +519,6 @@ Accept wildcard characters: False
```
### -TargetDatabase
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The TargetDatabase parameter returns all mailboxes that are being moved to the specified target mailbox database. You can use any value that uniquely identifies the database. For example:
@@ -575,6 +533,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md b/exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md
rename to exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md
index 68320eaf70..8f312cf0ae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-moverequeststatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-MoveRequestStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-moverequeststatistics
-schema: 2.0.0
-title: Get-MoveRequestStatistics
+ms.reviewer:
---
# Get-MoveRequestStatistics
@@ -116,9 +115,6 @@ This example exports the move request information so you can later import it int
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the mailbox or mail user. You can use one of the following values:
- GUID
@@ -135,6 +131,7 @@ You can use this parameter with the MoveRequestQueue or MailboxGuid parameters.
Type: MoveRequestIdParameter
Parameter Sets: IdentityOnPremises, IdentityCloud
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -144,9 +141,6 @@ Accept wildcard characters: False
```
### -MoveRequestQueue
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is for debugging purposes only.
@@ -163,6 +157,7 @@ You can't use this parameter with the Identity or MRSInstance parameters.
Type: DatabaseIdParameter
Parameter Sets: MigrationMoveRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -172,9 +167,6 @@ Accept wildcard characters: False
```
### -MRSInstance
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The MRSInstance parameter specifies the fully qualified domain name (FQDN) of the Client Access server on which the Microsoft Exchange Mailbox Replication service (MRS) resides. When using this parameter, all records are returned for this instance of MRS.
@@ -185,6 +177,7 @@ You can't use this parameter with the Identity or MoveRequestQueue parameters.
Type: Fqdn
Parameter Sets: MigrationMRSInstance
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -194,9 +187,6 @@ Accept wildcard characters: False
```
### -Analysis
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill Analysis Description }}
@@ -205,6 +195,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -214,9 +205,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
@@ -227,6 +215,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, MigrationMoveRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -236,9 +225,6 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -247,6 +233,7 @@ The DiagnosticArgument parameter modifies the results that are returned by using
Type: String
Parameter Sets: IdentityOnPremises, MigrationMoveRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -256,9 +243,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems. Valid values are:
@@ -271,6 +255,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -280,9 +265,6 @@ Accept wildcard characters: False
```
### -DiagnosticOnly
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill DiagnosticOnly Description }}
@@ -291,6 +273,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -300,9 +283,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -311,6 +291,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: IdentityOnPremises, MigrationMoveRequestQueue, MigrationMRSInstance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -320,15 +301,13 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, IdentityCloud, MigrationMoveRequestQueue
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -338,9 +317,6 @@ Accept wildcard characters: False
```
### -MailboxGuid
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The MailboxGuid parameter specifies the GUID of a mailbox for which you want to view the move request statistics.
@@ -351,6 +327,7 @@ You can't use this parameter with the Identity parameter.
Type: Guid
Parameter Sets: MigrationMoveRequestQueue, MigrationMRSInstance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -360,9 +337,6 @@ Accept wildcard characters: False
```
### -ProxyToMailbox
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The ProxyToMailbox parameter filters the results by the location of the specified mailbox (also known as proxying). You can use any value that uniquely identifies the mailbox. For example:
@@ -382,6 +356,7 @@ The ProxyToMailbox parameter filters the results by the location of the specifie
Type: MailboxIdParameter
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -391,15 +366,13 @@ Accept wildcard characters: False
```
### -ReportOnly
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, IdentityCloud, MigrationMoveRequestQueue
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md b/exchange/exchange-ps/exchange/Get-MxRecordReport.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md
rename to exchange/exchange-ps/exchange/Get-MxRecordReport.md
index 381a4bd6ca..1600495130 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md
+++ b/exchange/exchange-ps/exchange/Get-MxRecordReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-mxrecordreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-MxRecordReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-mxrecordreport
-schema: 2.0.0
-title: Get-MxRecordReport
+ms.reviewer:
---
# Get-MxRecordReport
@@ -42,15 +41,13 @@ This example shows the MX record information for the contoso.com domain.
## PARAMETERS
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Domain parameter specifies the domain you want to test.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -60,15 +57,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MyAnalyticsFeatureConfig.md b/exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-MyAnalyticsFeatureConfig.md
rename to exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md
index 9e84a9bb8b..ad5461513b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MyAnalyticsFeatureConfig.md
+++ b/exchange/exchange-ps/exchange/Get-MyAnalyticsFeatureConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-myanalyticsfeatureconfig
applicable: Exchange Online
+title: Get-MyAnalyticsFeatureConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig
-schema: 2.0.0
-title: Get-MyAnalyticsFeatureConfig
---
# Get-MyAnalyticsFeatureConfig
@@ -61,15 +60,13 @@ This example and the corresponding output shows the MyAnalytics configuration fo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the user you want to view. You identify the user by their email address.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md b/exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md
rename to exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md
index f7b4de2bb8..3b753febcb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md
+++ b/exchange/exchange-ps/exchange/Get-NetworkConnectionInfo.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-networkconnectioninfo
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-NetworkConnectionInfo
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-networkconnectioninfo
-schema: 2.0.0
-title: Get-NetworkConnectionInfo
+ms.reviewer:
---
# Get-NetworkConnectionInfo
@@ -50,9 +49,6 @@ This example retrieves network configuration information for all network adapter
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the server you want to query. You can use any value that uniquely identifies the server. For example:
- Name
@@ -66,6 +62,7 @@ If you don't use the Identity parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -86,6 +80,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md b/exchange/exchange-ps/exchange/Get-Notification.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Notification.md
rename to exchange/exchange-ps/exchange/Get-Notification.md
index 56c6a50bb9..a354e891db 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md
+++ b/exchange/exchange-ps/exchange/Get-Notification.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-notification
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-Notification
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-notification
-schema: 2.0.0
-title: Get-Notification
+ms.reviewer:
---
# Get-Notification
@@ -84,15 +83,13 @@ This example displays detailed information for the specified notification event.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the notification event that you want to view. You identify the notification event by its AlternativeID property value (a GUID). You can find this value by running the command Get-Notification | Format-List DisplayName,AlternateID,StartTime,Status,Type.
```yaml
Type: EwsStoreObjectIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -102,9 +99,6 @@ Accept wildcard characters: False
```
### -Settings
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Settings switch includes the ProcessType and NotificationEmail property values in the results. You don't need to specify a value with this switch.
@@ -117,6 +111,7 @@ You can't use this switch with the Summary switch.
Type: SwitchParameter
Parameter Sets: Settings
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -126,9 +121,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -137,6 +129,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -146,9 +139,6 @@ Accept wildcard characters: False
```
### -ProcessType
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ProcessType parameter filters the results by the type of notification event. Valid values are:
- CertExpiry
@@ -159,8 +149,9 @@ The ProcessType parameter filters the results by the type of notification event.
```yaml
Type: AsyncOperationType
-Parameter Sets: Settings, Filter
+Parameter Sets: Settings
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -169,16 +160,27 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -ResultSize
+```yaml
+Type: AsyncOperationType
+Parameter Sets: Filter
+Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -ResultSize
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: Filter
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -188,9 +190,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -199,6 +198,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: Filter
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -208,9 +208,6 @@ Accept wildcard characters: False
```
### -Summary
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Summary switch includes only the ProcessType and Status property values in the results. You don't need to specify a value with this switch.
You can't use this switch with the Settings switch.
@@ -219,6 +216,7 @@ You can't use this switch with the Settings switch.
Type: SwitchParameter
Parameter Sets: Identity, Filter
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md b/exchange/exchange-ps/exchange/Get-OMEConfiguration.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md
rename to exchange/exchange-ps/exchange/Get-OMEConfiguration.md
index a949238598..801c20e7db 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-OMEConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-omeconfiguration
applicable: Exchange Online, Exchange Online Protection
+title: Get-OMEConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-omeconfiguration
-schema: 2.0.0
-title: Get-OMEConfiguration
+ms.reviewer:
---
# Get-OMEConfiguration
@@ -48,15 +47,13 @@ This example returns detailed information for all OME configurations in the orga
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the OME configuration that you want to get. The default OME configuration has the Identity value "OME Configuration".
```yaml
Type: OMEConfigurationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md b/exchange/exchange-ps/exchange/Get-OMEMessageStatus.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md
rename to exchange/exchange-ps/exchange/Get-OMEMessageStatus.md
index 336fa65242..1162642bbb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md
+++ b/exchange/exchange-ps/exchange/Get-OMEMessageStatus.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-omemessagestatus
applicable: Exchange Online
+title: Get-OMEMessageStatus
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-omemessagestatus
-schema: 2.0.0
-title: Get-OMEMessageStatus
+ms.reviewer:
---
# Get-OMEMessageStatus
@@ -43,9 +42,6 @@ This example returns the encryption revocation status for the specified message.
## PARAMETERS
### -MessageId
-
-> Applicable: Exchange Online
-
The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "").
You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Microsoft Purview compliance portal.
@@ -54,6 +50,7 @@ You can find the Message ID for a message in Message Trace or the Message Encryp
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md
rename to exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md
index 7833b1e3f6..274bd7b330 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/Get-OabVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-oabvirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-OabVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-oabvirtualdirectory
-schema: 2.0.0
-title: Get-OabVirtualDirectory
+ms.reviewer:
---
# Get-OabVirtualDirectory
@@ -68,9 +67,6 @@ This example returns detailed information for the OAB virtual directory named "O
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the OAB virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -85,6 +81,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -94,9 +91,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -110,6 +104,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -119,9 +114,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -130,6 +122,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -139,15 +132,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -157,9 +148,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
By default, this cmdlet shows information about virtual directories in the Client Access services on Mailbox servers. Client connections are proxied from the Client Access services on Mailbox servers to the backend services on Mailbox servers. Clients don't connect directly to the backend services.
@@ -170,6 +158,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md b/exchange/exchange-ps/exchange/Get-OfflineAddressBook.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md
rename to exchange/exchange-ps/exchange/Get-OfflineAddressBook.md
index ff9c978f2a..dbf02a696b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md
+++ b/exchange/exchange-ps/exchange/Get-OfflineAddressBook.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-offlineaddressbook
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-OfflineAddressBook
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-offlineaddressbook
-schema: 2.0.0
-title: Get-OfflineAddressBook
+ms.reviewer:
---
# Get-OfflineAddressBook
@@ -66,9 +65,6 @@ This example returns specific properties for all existing OABs, including the Ge
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the OAB that you want to view. You can use any value that uniquely identifies the OAB. For example:
- Name or \\Name
@@ -81,6 +77,7 @@ You can't use this parameter with the Server parameter.
Type: OfflineAddressBookIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -90,9 +87,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
**Note**: This parameter isn't relevant in Exchange 2013 or later. The Server property for an OAB is blank, because the OAB is generated by an arbitration mailbox.
@@ -111,6 +105,7 @@ You can't use this parameter with the Identity parameter.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -120,9 +115,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -131,6 +123,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md b/exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md
rename to exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md
index 14db290342..18d268514c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md
+++ b/exchange/exchange-ps/exchange/Get-OnPremisesOrganization.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-onpremisesorganization
applicable: Exchange Online, Exchange Online Protection
+title: Get-OnPremisesOrganization
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-onpremisesorganization
-schema: 2.0.0
-title: Get-OnPremisesOrganization
+ms.reviewer:
---
# Get-OnPremisesOrganization
@@ -52,9 +51,6 @@ This example retrieves the on-premises organization settings by using the FQDN o
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the identity of the on-premises organization object. You can use the following values:
- Canonical name
@@ -65,6 +61,7 @@ The Identity parameter specifies the identity of the on-premises organization ob
Type: OnPremisesOrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md b/exchange/exchange-ps/exchange/Get-OnlineMeetingConfiguration.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md
rename to exchange/exchange-ps/exchange/Get-OnlineMeetingConfiguration.md
index 7a988d46c5..57d2252911 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md
+++ b/exchange/exchange-ps/exchange/Get-OnlineMeetingConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-onlinemeetingconfiguration
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-OnlineMeetingConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-onlinemeetingconfiguration
-schema: 2.0.0
-title: Get-OnlineMeetingConfiguration
+ms.reviewer:
---
# Get-OnlineMeetingConfiguration
@@ -49,9 +48,6 @@ This example gets the Skype Meetings configuration for the specified mailbox.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -69,6 +65,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -78,15 +75,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md b/exchange/exchange-ps/exchange/Get-OrganizationConfig.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md
rename to exchange/exchange-ps/exchange/Get-OrganizationConfig.md
index 002af611d2..0d00218842 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md
+++ b/exchange/exchange-ps/exchange/Get-OrganizationConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-organizationconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-OrganizationConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-organizationconfig
-schema: 2.0.0
-title: Get-OrganizationConfig
+ms.reviewer:
---
# Get-OrganizationConfig
@@ -61,9 +60,6 @@ If the value of EwsApplicationAccessPolicy is EnforceBlockList, all applications
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -74,6 +70,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md b/exchange/exchange-ps/exchange/Get-OrganizationRelationship.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md
rename to exchange/exchange-ps/exchange/Get-OrganizationRelationship.md
index 3207111a9e..0c2f80f334 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md
+++ b/exchange/exchange-ps/exchange/Get-OrganizationRelationship.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-organizationrelationship
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-OrganizationRelationship
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-organizationrelationship
-schema: 2.0.0
-title: Get-OrganizationRelationship
+ms.reviewer:
---
# Get-OrganizationRelationship
@@ -49,9 +48,6 @@ This example retrieves the organization relationship settings by using the FQDN
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the identity of the organizational relationship. You can use the following values:
- Canonical name
@@ -62,6 +58,7 @@ The Identity parameter specifies the identity of the organizational relationship
Type: OrganizationRelationshipIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -82,6 +76,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationSegment.md b/exchange/exchange-ps/exchange/Get-OrganizationSegment.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OrganizationSegment.md
rename to exchange/exchange-ps/exchange/Get-OrganizationSegment.md
index 3d309fe6b7..12687a5a45 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationSegment.md
+++ b/exchange/exchange-ps/exchange/Get-OrganizationSegment.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-organizationsegment
applicable: Security & Compliance
+title: Get-OrganizationSegment
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-organizationsegment
-schema: 2.0.0
-title: Get-OrganizationSegment
+ms.reviewer:
---
# Get-OrganizationSegment
@@ -56,9 +55,6 @@ This example returns detailed information about the organization segment named E
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the organization segment that you want to view. You can use a value that uniquely identifies the segment. For example:
- Name
@@ -69,6 +65,7 @@ The Identity parameter specifies the organization segment that you want to view.
Type: PolicyIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
@@ -92,4 +89,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
[Define policies for information barriers](https://learn.microsoft.com/purview/information-barriers-policies)
-[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchangepowershell/new-informationbarrierpolicy)
+[New-InformationBarrierPolicy](https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md b/exchange/exchange-ps/exchange/Get-OrganizationalUnit.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md
rename to exchange/exchange-ps/exchange/Get-OrganizationalUnit.md
index b624cd2c69..01e951b29f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md
+++ b/exchange/exchange-ps/exchange/Get-OrganizationalUnit.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-organizationalunit
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-OrganizationalUnit
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-organizationalunit
-schema: 2.0.0
-title: Get-OrganizationalUnit
+ms.reviewer:
---
# Get-OrganizationalUnit
@@ -68,9 +67,6 @@ For more information about pipelining and the Format-Table cmdlet, see [About Pi
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the OU or domain that you want to view. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -84,6 +80,7 @@ You can use this parameter with the SearchText parameter.
Type: ExtendedOrganizationalUnitIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -93,9 +90,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -104,6 +98,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,15 +108,13 @@ Accept wildcard characters: False
```
### -IncludeContainers
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeContainers switch instructs the command to return containers in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -131,15 +124,13 @@ Accept wildcard characters: False
```
### -SingleNodeOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SingleNodeOnly switch instructs the command to return only the first level child OUs beneath the OU specified in the Identity parameter. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -149,15 +140,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -167,9 +156,6 @@ Accept wildcard characters: False
```
### -SearchText
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SearchText parameter enables you to search the names of all OUs in your organization for the specified string. Only the OUs that match the string you specify are returned. If the string you specify contains spaces, enclose it in quotation marks (").
You can't use this parameter with the Identity parameter.
@@ -178,6 +164,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Search
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md b/exchange/exchange-ps/exchange/Get-OutboundConnector.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md
rename to exchange/exchange-ps/exchange/Get-OutboundConnector.md
index 49cbedd76e..ef832c3069 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md
+++ b/exchange/exchange-ps/exchange/Get-OutboundConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-outboundconnector
applicable: Exchange Online, Exchange Online Protection
+title: Get-OutboundConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-outboundconnector
-schema: 2.0.0
-title: Get-OutboundConnector
+ms.reviewer:
---
# Get-OutboundConnector
@@ -46,9 +45,6 @@ This example displays detailed information about the Outbound connector named Co
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the Outbound connector that you want to view. You can use any value that uniquely identifies the connector. For example:
- Name
@@ -59,6 +55,7 @@ The Identity parameter specifies the Outbound connector that you want to view. Y
Type: OutboundConnectorIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -IncludeTestModeConnectors
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeTestModeConnectors parameter filters the results by Outbound connectors that are in test mode. Valid values are:
- $true: Only Outbound connectors that are in test mode are returned in the results.
@@ -82,6 +76,7 @@ You configure an Outbound connector in test mode by using the TestMode parameter
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -91,9 +86,6 @@ Accept wildcard characters: False
```
### -IsTransportRuleScoped
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IsTransportRuleScoped parameter filters the results by Outbound connectors that are scoped to transport rules (also known as mail flow rules). Valid values are:
- $true: Only Outbound connectors that are scoped to transport rules are returned in the results.
@@ -105,6 +97,7 @@ You scope a transport rule to a specific Outbound connector by using the RouteMe
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -114,15 +107,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md b/exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md
rename to exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md
index 17040b63b4..a111c53994 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md
+++ b/exchange/exchange-ps/exchange/Get-OutboundConnectorReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-outboundconnectorreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-OutboundConnectorReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-outboundconnectorreport
-schema: 2.0.0
-title: Get-OutboundConnectorReport
+ms.reviewer:
---
# Get-OutboundConnectorReport
@@ -42,15 +41,13 @@ This example shows the Outbound connector that's used to deliver mail to the con
## PARAMETERS
### -Domain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Domain parameter specifies the domain you want to test.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -60,15 +57,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md b/exchange/exchange-ps/exchange/Get-OutlookAnywhere.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md
rename to exchange/exchange-ps/exchange/Get-OutlookAnywhere.md
index 28d5d37d26..e2189d867d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md
+++ b/exchange/exchange-ps/exchange/Get-OutlookAnywhere.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-outlookanywhere
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-OutlookAnywhere
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-outlookanywhere
-schema: 2.0.0
-title: Get-OutlookAnywhere
+ms.reviewer:
---
# Get-OutlookAnywhere
@@ -61,9 +60,6 @@ This example returns information about the Outlook Anywhere virtual directory na
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Outlook Anywhere virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -78,6 +74,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -87,9 +84,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -103,6 +97,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -112,9 +107,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -123,6 +115,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -132,15 +125,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -150,9 +141,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
By default, this cmdlet shows information about virtual directories in the Client Access services on Mailbox servers. Client connections are proxied from the Client Access services on Mailbox servers to the backend services on Mailbox servers. Clients don't connect directly to the backend services.
@@ -163,6 +151,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md b/exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md
rename to exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md
index 30ab2649a2..ed2ad0aa94 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-outlookprotectionrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-OutlookProtectionRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-outlookprotectionrule
-schema: 2.0.0
-title: Get-OutlookProtectionRule
+ms.reviewer:
---
# Get-OutlookProtectionRule
@@ -55,15 +54,13 @@ The Identity parameter is positional. When used after the cmdlet name, the param
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter identifies an Outlook protection rule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -84,6 +78,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md b/exchange/exchange-ps/exchange/Get-OutlookProvider.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md
rename to exchange/exchange-ps/exchange/Get-OutlookProvider.md
index e73ad25a0a..72b2e977b7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md
+++ b/exchange/exchange-ps/exchange/Get-OutlookProvider.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-outlookprovider
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-OutlookProvider
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-outlookprovider
-schema: 2.0.0
-title: Get-OutlookProvider
+ms.reviewer:
---
# Get-OutlookProvider
@@ -51,9 +50,6 @@ This example returns detailed information for the Outlook provider named WEB.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the ADIDParameter value of the MAPI protocol that you want to view. Typical values are:
- EXCH
@@ -64,6 +60,7 @@ The Identity parameter specifies the ADIDParameter value of the MAPI protocol th
Type: OutlookProviderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md
rename to exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md
index b282c856fa..d3d81a63ed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-OwaMailboxPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-owamailboxpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-OwaMailboxPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-owamailboxpolicy
-schema: 2.0.0
-title: Get-OwaMailboxPolicy
+ms.reviewer:
---
# Get-OwaMailboxPolicy
@@ -56,9 +55,6 @@ This example retrieves the information for the mailbox policy named Corporate fo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -69,6 +65,7 @@ The Identity parameter specifies the mailbox policy that you want to view. You c
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -89,6 +83,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md
rename to exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md
index 255f7385df..6087a13fe7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/Get-OwaVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-owavirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-OwaVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-owavirtualdirectory
-schema: 2.0.0
-title: Get-OwaVirtualDirectory
+ms.reviewer:
---
# Get-OwaVirtualDirectory
@@ -72,9 +71,6 @@ This example returns a summary list of all Outlook on the web virtual directorie
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the OWA virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -89,6 +85,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -98,9 +95,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -114,6 +108,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -123,9 +118,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -134,6 +126,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -143,15 +136,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -161,9 +152,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
By default, this cmdlet shows information about virtual directories in the Client Access services on Mailbox servers. Client connections are proxied from the Client Access services on Mailbox servers to the backend services on Mailbox servers. Clients don't connect directly to the backend services.
@@ -174,6 +162,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md b/exchange/exchange-ps/exchange/Get-PartnerApplication.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md
rename to exchange/exchange-ps/exchange/Get-PartnerApplication.md
index d445571b81..1e1e76f5db 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md
+++ b/exchange/exchange-ps/exchange/Get-PartnerApplication.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-partnerapplication
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PartnerApplication
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-partnerapplication
-schema: 2.0.0
-title: Get-PartnerApplication
+ms.reviewer:
---
# Get-PartnerApplication
@@ -45,15 +44,13 @@ This example retrieves settings for all partner applications configured in Excha
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of a partner application.
```yaml
Type: PartnerApplicationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -63,9 +60,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -74,6 +68,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -83,9 +78,6 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -94,6 +86,7 @@ This parameter is reserved for internal Microsoft use.
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md b/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md
rename to exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md
index dac9418166..ca13e8b6fa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md
+++ b/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-pendingdelicenseuser
applicable: Exchange Online, Exchange Online Protection
+title: Get-PendingDelicenseUser
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-pendingdelicenseuser
-schema: 2.0.0
-title: Get-PendingDelicenseUser
+ms.reviewer:
---
# Get-PendingDelicenseUser
@@ -62,9 +61,6 @@ This example returns a summary list of all mailboxes where the 30 day delay for
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the mailbox with a pending mailbox license removal request.
You can use any value that uniquely identifies the mailbox. For example:
@@ -83,6 +79,7 @@ You can't use this parameter with the ShowDueObjectsOnly switch.
Type: RecipientIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -92,15 +89,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: TenantLevelParameterSet
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -ShowDueObjectsOnly
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ShowDueObjectsOnly switch filters the results by mailboxes where the 30 day delay for removing the license has ended, and the license can be removed from the mailbox at any time. You don't need to specify a value with this switch.
You can't use this switch with the Identity parameter.
@@ -121,6 +113,7 @@ You can't use this switch with the Identity parameter.
Type: SwitchParameter
Parameter Sets: TenantLevelParameterSet
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md b/exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md
rename to exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md
index 67b746dcbc..e646d32251 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md
+++ b/exchange/exchange-ps/exchange/Get-PendingFederatedDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-pendingfederateddomain
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-PendingFederatedDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-pendingfederateddomain
-schema: 2.0.0
-title: Get-PendingFederatedDomain
+ms.reviewer:
---
# Get-PendingFederatedDomain
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PerimeterConfig.md b/exchange/exchange-ps/exchange/Get-PerimeterConfig.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PerimeterConfig.md
rename to exchange/exchange-ps/exchange/Get-PerimeterConfig.md
index 84bfae4905..0559a00b0d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PerimeterConfig.md
+++ b/exchange/exchange-ps/exchange/Get-PerimeterConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-perimeterconfig
applicable: Exchange Online
+title: Get-PerimeterConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-perimeterconfig
-schema: 2.0.0
-title: Get-PerimeterConfig
+ms.reviewer:
---
# Get-PerimeterConfig
@@ -41,15 +40,13 @@ This example returns the list of gateway servers and internal email servers in y
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md b/exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md
rename to exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md
index c782ae2639..7e1d8bcf8e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-PhishSimOverridePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-phishsimoverridepolicy
applicable: Exchange Online
+title: Get-PhishSimOverridePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-phishsimoverridepolicy
-schema: 2.0.0
-title: Get-PhishSimOverridePolicy
+ms.reviewer:
---
# Get-PhishSimOverridePolicy
@@ -40,9 +39,6 @@ This example returns detailed information about the one and only phishing simula
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the phishing simulation override policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -54,6 +50,7 @@ The Identity parameter specifies the phishing simulation override policy that yo
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -63,15 +60,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Place.md b/exchange/exchange-ps/exchange/Get-Place.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Place.md
rename to exchange/exchange-ps/exchange/Get-Place.md
index 0d99aef484..c13137555b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Place.md
+++ b/exchange/exchange-ps/exchange/Get-Place.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-place
applicable: Exchange Online
+title: Get-Place
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-place
-schema: 2.0.0
-title: Get-Place
+ms.reviewer:
---
# Get-Place
@@ -68,9 +67,6 @@ This example returns all room mailboxes.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the room mailbox that you want to view. You can use any value that uniquely identifies the room. For example:
- Name
@@ -86,6 +82,7 @@ You can't use this parameter with the Type parameter.
Type: RecipientIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -95,15 +92,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -113,15 +108,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -131,9 +124,6 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Online
-
The Type parameter filters the results by the type of room mailbox. Valid values are:
- Room
@@ -146,6 +136,7 @@ You can't use this parameter with the Identity parameter.
Type: GetPlaceType
Parameter Sets: AllPlaces
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -155,15 +146,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyConfig.md b/exchange/exchange-ps/exchange/Get-PolicyConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PolicyConfig.md
rename to exchange/exchange-ps/exchange/Get-PolicyConfig.md
index 56021327f8..7b985e28c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyConfig.md
+++ b/exchange/exchange-ps/exchange/Get-PolicyConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-policyconfig
applicable: Security & Compliance
+title: Get-PolicyConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-policyconfig
-schema: 2.0.0
-title: Get-PolicyConfig
+ms.reviewer:
---
# Get-PolicyConfig
@@ -40,15 +39,13 @@ This example returns the endpoint restrictions that are available in the organiz
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
You don't need to use this parameter. The only endpoint restrictions object in the organization is named Settings.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md b/exchange/exchange-ps/exchange/Get-PolicyTipConfig.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md
rename to exchange/exchange-ps/exchange/Get-PolicyTipConfig.md
index 0f66e454dd..0704474cc3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md
+++ b/exchange/exchange-ps/exchange/Get-PolicyTipConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-policytipconfig
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PolicyTipConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-policytipconfig
-schema: 2.0.0
-title: Get-PolicyTipConfig
+ms.reviewer:
---
# Get-PolicyTipConfig
@@ -66,9 +65,6 @@ This example returns details about the custom English Policy Tip for the action
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the custom Policy Tip you want to view. You can use any value that uniquely identifies the custom Policy Tip. For example:
- `Locale\Action`: Locale is a supported locale code. For example, en for English or fr for French. For more information about supported locales, see [Supported languages for NDRs](https://learn.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs). Action is one of the following Policy Tip actions: NotifyOnly, RejectOverride or Reject.
@@ -82,6 +78,7 @@ You can't use the Identity parameter with the Action, Locale or Original paramet
Type: PolicyTipConfigIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -91,9 +88,6 @@ Accept wildcard characters: False
```
### -Action
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Action parameter filters the Policy Tips by action. Valid values for this parameter are:
- NotifyOnly
@@ -108,6 +102,7 @@ You can't use the Action parameter with the Identity parameter.
Type: PolicyTipMessageConfigAction
Parameter Sets: Parameters
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -117,9 +112,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -128,6 +120,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -137,9 +130,6 @@ Accept wildcard characters: False
```
### -Locale
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Locale parameter specifies a locale-specific version of the Policy Tip.
Valid values for this parameter are supported locale codes. For example, en for English or fr for French. For more information about supported locales, see [Supported languages for NDRs](https://learn.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs).
@@ -150,6 +140,7 @@ You can't use the Locale parameter with the Identity parameter.
Type: CultureInfo
Parameter Sets: Parameters
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -159,9 +150,6 @@ Accept wildcard characters: False
```
### -Original
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Original switch specifies whether to include built-in Policy Tips in the results. You don't need to specify a value with this switch.
You can't use the Original switch with the Identity parameter.
@@ -170,6 +158,7 @@ You can't use the Original switch with the Identity parameter.
Type: SwitchParameter
Parameter Sets: Parameters
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md b/exchange/exchange-ps/exchange/Get-PopSettings.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md
rename to exchange/exchange-ps/exchange/Get-PopSettings.md
index fdf0c23826..4223b39960 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md
+++ b/exchange/exchange-ps/exchange/Get-PopSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-popsettings
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-PopSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-popsettings
-schema: 2.0.0
-title: Get-PopSettings
+ms.reviewer:
---
# Get-PopSettings
@@ -49,15 +48,13 @@ This example returns detailed information for the Microsoft Exchange POP3 servic
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -83,6 +77,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md
rename to exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md
index a5bc976d2e..b46a6dbd1e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/Get-PowerShellVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-powershellvirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-PowerShellVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-powershellvirtualdirectory
-schema: 2.0.0
-title: Get-PowerShellVirtualDirectory
+ms.reviewer:
---
# Get-PowerShellVirtualDirectory
@@ -68,9 +67,6 @@ This example returns a summary list of all PowerShell virtual directories in the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the PowerShell virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -85,6 +81,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -94,9 +91,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -110,6 +104,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -119,9 +114,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -130,6 +122,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -139,15 +132,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -157,9 +148,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
By default, this cmdlet shows information about virtual directories in the Client Access services on Mailbox servers. Client connections are proxied from the Client Access services on Mailbox servers to the backend services on Mailbox servers. Clients don't connect directly to the backend services.
@@ -170,6 +158,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ProtectionAlert.md b/exchange/exchange-ps/exchange/Get-ProtectionAlert.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ProtectionAlert.md
rename to exchange/exchange-ps/exchange/Get-ProtectionAlert.md
index 2085c02ebd..2e99bc420c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ProtectionAlert.md
+++ b/exchange/exchange-ps/exchange/Get-ProtectionAlert.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-protectionalert
applicable: Security & Compliance
+title: Get-ProtectionAlert
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-protectionalert
-schema: 2.0.0
-title: Get-ProtectionAlert
+ms.reviewer:
---
# Get-ProtectionAlert
@@ -49,9 +48,6 @@ This example returns detailed information about the specified alert policy.
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the alert policy that you want to view. You can use any value that uniquely identifies the alert policy. For example:
- Name
@@ -62,6 +58,7 @@ The Identity parameter specifies the alert policy that you want to view. You can
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -IncludeRuleXml
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeRuleXml Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md b/exchange/exchange-ps/exchange/Get-PublicFolder.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md
rename to exchange/exchange-ps/exchange/Get-PublicFolder.md
index 299fc5a598..6236c3d432 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolder.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolder
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolder
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfolder
-schema: 2.0.0
-title: Get-PublicFolder
+ms.reviewer:
---
# Get-PublicFolder
@@ -119,15 +118,13 @@ This example returns the public folders that reside in the public folder content
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name and path of the public folder you want to view. A valid value uses the syntax: `\Level1\Level2\...\LevenN\PublicFolder`. For example, `"\Customer Discussion"` or `"\Engineering\Customer Discussion"`.
```yaml
Type: PublicFolderIdParameter
Parameter Sets: GetChildren, Recurse, Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -137,9 +134,6 @@ Accept wildcard characters: False
```
### -GetChildren
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The GetChildren switch specifies whether to return only the children of the folder specified by the Identity parameter. You don't need to specify a value with this switch.
You can't use this switch with the Recurse or LostAndFound switches.
@@ -148,6 +142,7 @@ You can't use this switch with the Recurse or LostAndFound switches.
Type: SwitchParameter
Parameter Sets: GetChildren
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -157,9 +152,6 @@ Accept wildcard characters: False
```
### -Recurse
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Recurse switch specifies whether to return the specified public folder and all its children. You don't need to specify a value with this switch.
You can't use this switch with the GetChildren or LostAndFound switches.
@@ -168,6 +160,7 @@ You can't use this switch with the GetChildren or LostAndFound switches.
Type: SwitchParameter
Parameter Sets: Recurse
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -177,9 +170,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -188,6 +178,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -197,9 +188,6 @@ Accept wildcard characters: False
```
### -LostAndFound
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The LostAndFound switch specifies whether to return only orphaned folders that are located in \\NON\_IPM\_SUBTREE\\LOST\_AND\_FOUND. You don't need to specify a value with this switch.
The LOST\_AND\_FOUND folder holds missing folders that are recreated by the public folder hierarchy reconciliation process when the folder exists in a secondary public folder mailbox, but not in the primary.
@@ -210,6 +198,7 @@ You can't use this switch with the Identity parameter or the Recurse or LostAndF
Type: SwitchParameter
Parameter Sets: LostAndFound
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -219,9 +208,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the identity of the hierarchy public folder mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -239,6 +225,7 @@ The Mailbox parameter specifies the identity of the hierarchy public folder mail
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -248,9 +235,6 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -259,6 +243,7 @@ This parameter is reserved for internal Microsoft use.
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -268,9 +253,6 @@ Accept wildcard characters: False
```
### -ResidentFolders
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResidentFolders switch specifies whether to return public folders that reside in a specific content public folder mailbox. You don't need to specify a value with this switch.
If you don't use this switch, the command will return only public folders whose contents reside in the primary hierarchy public folder mailbox.
@@ -279,6 +261,7 @@ If you don't use this switch, the command will return only public folders whose
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -288,15 +271,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. The default maximum is 10,000. For no limit on the returned results, set this parameter to Unlimited. This parameter can only be passed in combination with the Recurse or GetChildren parameters.
```yaml
Type: Unlimited
Parameter Sets: GetChildren, Recurse, LostAndFound
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -306,9 +287,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example:
@@ -322,6 +300,7 @@ The Server parameter filters the results by the specified Exchange server. You c
Type: ServerIdParameter
Parameter Sets: GetChildren, Recurse, Identity
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md
index 841f2e7c5e..8827234280 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderAdministrativePermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderadministrativepermission
applicable: Exchange Server 2010
+title: Get-PublicFolderAdministrativePermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfolderadministrativepermission
-schema: 2.0.0
-title: Get-PublicFolderAdministrativePermission
+ms.reviewer:
---
# Get-PublicFolderAdministrativePermission
@@ -66,9 +65,6 @@ This example retrieves the owner of the public folder My Public Folder.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\\PublicFolder.
You can omit the parameter label so that only the public folder name or GUID is supplied.
@@ -77,6 +73,7 @@ You can omit the parameter label so that only the public folder name or GUID is
Type: PublicFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: 1
@@ -86,15 +83,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -104,9 +99,6 @@ Accept wildcard characters: False
```
### -Owner
-
-> Applicable: Exchange Server 2010
-
The Owner switch returns the owner of the public folder object. You don't need to specify a value with this switch.
You can't use this switch with the User parameter.
@@ -115,6 +107,7 @@ You can't use this switch with the User parameter.
Type: SwitchParameter
Parameter Sets: Owner
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -124,9 +117,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example:
- Name
@@ -138,6 +128,7 @@ The Server parameter filters the results by the specified Exchange server. You c
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -147,9 +138,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010
-
The User parameter filters the results by who has admin permissions on the specified public folder. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -175,6 +163,7 @@ You can't use this parameter with the Owner switch.
Type: SecurityPrincipalIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md b/exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md
index e72bcbe253..a78eb99b9f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderClientPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderclientpermission
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolderClientPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfolderclientpermission
-schema: 2.0.0
-title: Get-PublicFolderClientPermission
+ms.reviewer:
---
# Get-PublicFolderClientPermission
@@ -55,9 +54,6 @@ This example retrieves the permissions for the public folder My Public Folder, f
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder.
You can omit the parameter label so that only the public folder name or GUID is supplied.
@@ -66,6 +62,7 @@ You can omit the parameter label so that only the public folder name or GUID is
Type: PublicFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -86,6 +80,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -106,6 +98,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All))
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example:
@@ -131,6 +121,7 @@ The Server parameter filters the results by the specified Exchange server. You c
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -140,9 +131,6 @@ Accept wildcard characters: False
```
### -User
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The User parameter specifies the user for whom you want to view the permissions on the public folder.
For the best results, we recommend using the following values:
@@ -154,6 +142,7 @@ For the best results, we recommend using the following values:
Type: PublicFolderUserIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -163,9 +152,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the public folder mailbox that you want to view the permissions for. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -185,6 +171,7 @@ By default, the permissions are returned from the primary public folder mailbox.
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md b/exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md
index 9850b9ee99..163d873ee4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderDatabase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderdatabase
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-PublicFolderDatabase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfolderdatabase
-schema: 2.0.0
-title: Get-PublicFolderDatabase
+ms.reviewer:
---
# Get-PublicFolderDatabase
@@ -74,9 +73,6 @@ This example returns information about all public folders on Server01.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the public folder database that you want to view. You can use any value that uniquely identifies the database. For example:
- Name
@@ -91,6 +87,7 @@ If you have multiple databases with the same name, the cmdlet retrieves all data
Type: DatabaseIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -100,9 +97,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example:
- Name
@@ -116,6 +110,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -125,15 +120,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -143,9 +136,6 @@ Accept wildcard characters: False
```
### -IncludePreExchange2010
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The IncludePreExchange2010 switch specifies whether to include information about Exchange 2003 or Exchange 2007 public folders in the results. You don't need to specify a value with this switch.
@@ -156,6 +146,7 @@ This switch isn't useful in commands where you use the Server or Identity parame
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -165,15 +156,13 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Status switch specifies whether to include additional backup and mount status information for servers running Exchange 2010. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -183,15 +172,13 @@ Accept wildcard characters: False
```
### -IncludeCorrupted
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md
index 291f4e40cc..7e8d13e1d4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderItemStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderitemstatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolderItemStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfolderitemstatistics
-schema: 2.0.0
-title: Get-PublicFolderItemStatistics
+ms.reviewer:
---
# Get-PublicFolderItemStatistics
@@ -65,15 +64,13 @@ This example exports the output of the Get-PublicFolderItemStatistics command to
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the following format: \\TopLevelPublicFolder\\PublicFolder
```yaml
Type: PublicFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -83,9 +80,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -94,6 +88,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -103,9 +98,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the identity of the hierarchy public folder mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -123,6 +115,7 @@ The Mailbox parameter specifies the identity of the hierarchy public folder mail
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -132,9 +125,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -143,6 +133,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All))
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -152,9 +143,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example:
@@ -168,6 +156,7 @@ The Server parameter filters the results by the specified Exchange server. You c
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md
index 066a6a5076..d7b0c82238 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxDiagnostics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermailboxdiagnostics
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolderMailboxDiagnostics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfoldermailboxdiagnostics
-schema: 2.0.0
-title: Get-PublicFolderMailboxDiagnostics
+ms.reviewer:
---
# Get-PublicFolderMailboxDiagnostics
@@ -53,9 +52,6 @@ This example returns the diagnostic information for the public folder mailbox Sa
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the public folder mailbox. The public folder mailbox is where the content of the public folder resides.
You can use any value that uniquely identifies the mailbox. For example:
@@ -75,6 +71,7 @@ You can use any value that uniquely identifies the mailbox. For example:
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -84,9 +81,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -96,6 +90,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -105,9 +100,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -116,6 +108,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -125,15 +118,13 @@ Accept wildcard characters: False
```
### -IncludeDumpsterInfo
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeDumpsterInfo specifies whether to include diagnostic information for the \\NON\_IPM\_TREE\\DUMPSTER\_ROOT folder (the dumpster for public folder mailboxes is included in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -143,9 +134,6 @@ Accept wildcard characters: False
```
### -IncludeHierarchyInfo
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeHierarchyInfo switch specifies whether to include folder hierarchy information in the results. You don't need to specify a value with this switch.
Using this switch returns the following information:
@@ -165,6 +153,7 @@ Using this switch returns the following information:
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -174,15 +163,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md
index ec4334625e..4fe2797ff4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermailboxmigrationrequest
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolderMailboxMigrationRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfoldermailboxmigrationrequest
-schema: 2.0.0
-title: Get-PublicFolderMailboxMigrationRequest
+ms.reviewer:
---
# Get-PublicFolderMailboxMigrationRequest
@@ -84,9 +83,6 @@ This example returns duplicate public folder migration requests (requests create
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the public folder mailbox migration request that you want to view. The value uses the syntax: `\PublicFolderMailboxMigration` (for example, `\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`).
You can't use this parameter with the following parameters:
@@ -102,6 +98,7 @@ You can't use this parameter with the following parameters:
Type: PublicFolderMailboxMigrationRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -111,9 +108,6 @@ Accept wildcard characters: False
```
### -BatchName
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BatchName parameter filters the results by the friendly BatchName value that was assigned when the batch job was created. The format of this value is: `MigrationService:`.
You can't use this parameter with the Identity parameter.
@@ -122,6 +116,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -131,9 +126,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -142,6 +134,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -151,9 +144,6 @@ Accept wildcard characters: False
```
### -HighPriority
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
@@ -167,6 +157,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -176,9 +167,6 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies the name of the public folder mailbox migration request. If the name was not specified at creation, the default value is `PublicFolderMailboxMigration` (for example, `PublicFolderMailboxMigration2ffdef13-01b9-4586-af2b-d5a5482010a8`).
You can't use this parameter with the Identity parameter.
@@ -187,6 +175,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -196,9 +185,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
@@ -213,6 +199,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -222,15 +209,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -240,9 +225,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Status parameter filters the results based on status. You can use the following values:
- AutoSuspended
@@ -262,6 +244,7 @@ You can't use this parameter with the Identity parameter.
Type: RequestStatus
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -271,9 +254,6 @@ Accept wildcard characters: False
```
### -Suspend
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
You can't use this parameter with the Identity parameter.
@@ -282,6 +262,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md
index a29a4656ab..cb164285ad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderMailboxMigrationRequestStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermailboxmigrationrequeststatistics
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolderMailboxMigrationRequestStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfoldermailboxmigrationrequeststatistics
-schema: 2.0.0
-title: Get-PublicFolderMailboxMigrationRequestStatistics
+ms.reviewer:
---
# Get-PublicFolderMailboxMigrationRequestStatistics
@@ -76,9 +75,6 @@ This example uses the Identity parameter to return information about the specifi
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the public folder mailbox migration request. The default identity value is `\PublicFolderMailboxMigration` (for example, `PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`).
You can't use this parameter with the RequestQueue and RequestGuid parameters.
@@ -87,6 +83,7 @@ You can't use this parameter with the RequestQueue and RequestGuid parameters.
Type: PublicFolderMailboxMigrationRequestIdParameter
Parameter Sets: IdentityOnPremises, IdentityCloud
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -96,9 +93,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is for debugging purposes only.
@@ -115,6 +109,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -124,9 +119,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
@@ -137,6 +129,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: IdentityOnPremises, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -146,9 +139,6 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -157,6 +147,7 @@ The DiagnosticArgument parameter modifies the results that are returned by using
Type: String
Parameter Sets: IdentityOnPremises, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -166,9 +157,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
Typically, you use the DiagnosticInfo parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -177,6 +165,7 @@ Typically, you use the DiagnosticInfo parameter only at the request of Microsoft
Type: String
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -186,9 +175,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -197,6 +183,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: IdentityOnPremises, MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -206,15 +193,13 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -224,9 +209,6 @@ Accept wildcard characters: False
```
### -IncludeSkippedItems
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeSkippedItems Description }}
@@ -235,6 +217,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: IdentityCloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -244,15 +227,13 @@ Accept wildcard characters: False
```
### -ReportOnly
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -262,9 +243,6 @@ Accept wildcard characters: False
```
### -RequestGuid
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RequestGuid parameter specifies the unique RequestGuid identifier of the request that you want to view. To find the RequestGuid value, use the Get-PublicFolderMailboxMigrationRequest cmdlet.
@@ -275,6 +253,7 @@ If you use this parameter, you also need to use the RequestQueue parameter. You
Type: Guid
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md
index 14a3d3411d..c001744a6d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermigrationrequest
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-PublicFolderMigrationRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfoldermigrationrequest
-schema: 2.0.0
-title: Get-PublicFolderMigrationRequest
+ms.reviewer:
---
# Get-PublicFolderMigrationRequest
@@ -67,9 +66,6 @@ This example returns all migration requests that have the name PFMigrate10\_11\_
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the public folder migration request that you want to view. You can use the following values:
- GUID
@@ -81,6 +77,7 @@ You can't use this parameter with other filtering parameters (BatchName, HighPri
Type: PublicFolderMigrationRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -90,9 +87,6 @@ Accept wildcard characters: False
```
### -BatchName
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BatchName parameter specifies the name that was given to a batch migration request.
You can't use this parameter with the Identity parameter.
@@ -101,6 +95,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -110,15 +105,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -128,9 +121,6 @@ Accept wildcard characters: False
```
### -HighPriority
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
- $true Returns requests that were created with the Priority value High, Higher, Highest or Emergency.
@@ -142,6 +132,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -151,9 +142,6 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter filters the results by the name of the public folder migration request.
You can't use this parameter with the Identity parameter.
@@ -162,6 +150,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -171,9 +160,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
- Name
@@ -186,6 +172,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -195,15 +182,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -213,9 +198,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Status parameter filters the results based on status. You can use the following values:
- AutoSuspended
@@ -235,6 +217,7 @@ You can't use this parameter with the Identity parameter.
Type: RequestStatus
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -244,9 +227,6 @@ Accept wildcard characters: False
```
### -Suspend
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
You can't use this parameter with the Identity parameter.
@@ -255,6 +235,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequestStatistics.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequestStatistics.md
index 3a70bb487b..2ef492d5cb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderMigrationRequestStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermigrationrequeststatistics
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-PublicFolderMigrationRequestStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfoldermigrationrequeststatistics
-schema: 2.0.0
-title: Get-PublicFolderMigrationRequestStatistics
+ms.reviewer:
---
# Get-PublicFolderMigrationRequestStatistics
@@ -69,9 +68,6 @@ This example returns additional information about the migration request and expo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the migration request that you want to view. You can use the following values:
- Name
@@ -83,6 +79,7 @@ You can't use this parameter with the RequestQueue or RequestGuid parameter.
Type: PublicFolderMigrationRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -92,9 +89,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is for debugging purposes only.
The RequestQueue parameter filters the results by the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
@@ -109,6 +103,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -118,9 +113,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -129,6 +121,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -138,15 +131,13 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -156,15 +147,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -174,15 +163,13 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -192,15 +179,13 @@ Accept wildcard characters: False
```
### -ReportOnly
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -210,9 +195,6 @@ Accept wildcard characters: False
```
### -RequestGuid
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RequestGuid parameter specifies the GUID of a migration request.
You can't use this parameter with the Identity parameter.
@@ -221,6 +203,7 @@ You can't use this parameter with the Identity parameter.
Type: Guid
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md
index e1f09381b8..5d234a047b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermoverequest
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolderMoveRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfoldermoverequest
-schema: 2.0.0
-title: Get-PublicFolderMoveRequest
+ms.reviewer:
---
# Get-PublicFolderMoveRequest
@@ -65,9 +64,6 @@ This example returns the status of in-progress and queued requests that are on t
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the public folder move request. The default identity assigned to public folder move requests is \\PublicFolderMove.
You can't use this parameter with the following parameters:
@@ -83,6 +79,7 @@ You can't use this parameter with the following parameters:
Type: PublicFolderMoveRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -92,9 +89,6 @@ Accept wildcard characters: False
```
### -AccountPartition
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill AccountPartition Description }}
@@ -103,6 +97,7 @@ This parameter is available only in the cloud-based service.
Type: AccountPartitionIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -112,9 +107,6 @@ Accept wildcard characters: False
```
### -BatchName
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BatchName parameter specifies the name that was given to a batch public folder move request.
You can't use this parameter with the Identity parameter.
@@ -123,6 +115,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -132,9 +125,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is functional only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -143,6 +133,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -152,9 +143,6 @@ Accept wildcard characters: False
```
### -HighPriority
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
- $true Returns requests that were created with the Priority value High, Higher, Highest or Emergency.
@@ -166,6 +154,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -175,9 +164,6 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies the name of the public folder move request. If you didn't specify a name when creating the move request, PublicFolderMove will be the default name assigned to the request.
You can't use this parameter with the Identity parameter.
@@ -186,6 +172,7 @@ You can't use this parameter with the Identity parameter.
Type: String
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -195,9 +182,6 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill Organization Description }}
@@ -206,6 +190,7 @@ This parameter is available only in the cloud-based service.
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -215,9 +200,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
- Name
@@ -230,6 +212,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -239,15 +222,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -257,9 +238,6 @@ Accept wildcard characters: False
```
### -Status
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Status parameter filters the results based on status. You can use the following values:
- AutoSuspended
@@ -279,6 +257,7 @@ You can't use this parameter with the Identity parameter.
Type: RequestStatus
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -288,9 +267,6 @@ Accept wildcard characters: False
```
### -Suspend
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
You can't use this parameter with the Identity parameter.
@@ -299,6 +275,7 @@ You can't use this parameter with the Identity parameter.
Type: Boolean
Parameter Sets: Filtering
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md
index bce7688ee7..475fc29578 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderMoveRequestStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfoldermoverequeststatistics
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolderMoveRequestStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfoldermoverequeststatistics
-schema: 2.0.0
-title: Get-PublicFolderMoveRequestStatistics
+ms.reviewer:
---
# Get-PublicFolderMoveRequestStatistics
@@ -69,9 +68,6 @@ This example returns the detailed statistics for the move request \\PublicFolder
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of the public folder move request. The default public folder move request identity is \\PublicFolderMove.
This parameter can't be used with the RequestQueue parameter.
@@ -80,6 +76,7 @@ This parameter can't be used with the RequestQueue parameter.
Type: PublicFolderMoveRequestIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -89,9 +86,6 @@ Accept wildcard characters: False
```
### -RequestQueue
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is for debugging purposes only.
The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
@@ -106,6 +100,7 @@ You can't use this parameter with the Identity parameter.
Type: DatabaseIdParameter
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -115,9 +110,6 @@ Accept wildcard characters: False
```
### -Diagnostic
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
Typically, you use this switch only at the request of Microsoft Customer Service and Support to troubleshoot problems.
@@ -126,6 +118,7 @@ Typically, you use this switch only at the request of Microsoft Customer Service
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -135,15 +128,13 @@ Accept wildcard characters: False
```
### -DiagnosticArgument
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -153,9 +144,6 @@ Accept wildcard characters: False
```
### -DiagnosticInfo
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill DiagnosticInfo Description }}
@@ -164,6 +152,7 @@ This parameter is available only in the cloud-based service.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -173,9 +162,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is functional only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -184,6 +170,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -193,15 +180,13 @@ Accept wildcard characters: False
```
### -IncludeReport
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -211,9 +196,6 @@ Accept wildcard characters: False
```
### -IncludeSkippedItems
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeSkippedItems Description }}
@@ -222,6 +204,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -231,15 +214,13 @@ Accept wildcard characters: False
```
### -ReportOnly
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -249,9 +230,6 @@ Accept wildcard characters: False
```
### -RequestGuid
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequestGuid parameter specifies the GUID of the public folder move request for which you want to view the request statistics.
This parameter can't be used with the Identity parameter.
@@ -260,6 +238,7 @@ This parameter can't be used with the Identity parameter.
Type: Guid
Parameter Sets: MigrationRequestQueue
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md b/exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md
rename to exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md
index e7fb830203..023a6d31c0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-PublicFolderStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-publicfolderstatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-PublicFolderStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-publicfolderstatistics
-schema: 2.0.0
-title: Get-PublicFolderStatistics
+ms.reviewer:
---
# Get-PublicFolderStatistics
@@ -45,9 +44,6 @@ This example retrieves statistics about the public folder Marketing\\2013\\Pamph
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder.
You can omit the parameter label so that only the public folder name or GUID is supplied.
@@ -56,6 +52,7 @@ You can omit the parameter label so that only the public folder name or GUID is
Type: PublicFolderIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -76,6 +70,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -85,9 +80,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the identity of the hierarchy public folder mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -105,6 +97,7 @@ The Mailbox parameter specifies the identity of the hierarchy public folder mail
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -114,9 +107,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is available only in on-premises Exchange.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -125,6 +115,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -134,9 +125,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example:
@@ -150,6 +138,7 @@ The Server parameter filters the results by the specified Exchange server. You c
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md b/exchange/exchange-ps/exchange/Get-QuarantineMessage.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md
rename to exchange/exchange-ps/exchange/Get-QuarantineMessage.md
index 06e5a73791..afa39b7a2e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md
+++ b/exchange/exchange-ps/exchange/Get-QuarantineMessage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-quarantinemessage
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-QuarantineMessage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-quarantinemessage
-schema: 2.0.0
-title: Get-QuarantineMessage
+ms.reviewer:
---
# Get-QuarantineMessage
@@ -103,9 +102,6 @@ This example returns detailed information for the files protected by Safe Attach
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the quarantined message that you want to view. The value is a unique quarantined message identifier in the format `GUID1\GUID2` (for example `c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7`).
When you identify the quarantine message by using this parameter, the RecipientAddress, QuarantineUser, and ReleasedUser properties are available. To see these values, you need to use a formatting cmdlet. For example, `Get-QuarantineMessage -Identity | Format-List`.
@@ -114,6 +110,7 @@ When you identify the quarantine message by using this parameter, the RecipientA
Type: QuarantineMessageIdentity
Parameter Sets: Details
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -123,9 +120,6 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Direction parameter filters the results by incoming or outgoing messages. Valid values are:
- Inbound
@@ -137,6 +131,7 @@ You can specify multiple values separated by commas.
Type: Microsoft.Exchange.Management.FfoQuarantine.QuarantineMessageDirectionEnum
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -146,15 +141,13 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String[]
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -164,9 +157,6 @@ Accept wildcard characters: False
```
### -EndExpiresDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EndExpiresDate parameter specifies the latest messages that will automatically be deleted from the quarantine. Use this parameter with the StartExpiresDate parameter.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -177,6 +167,7 @@ For example, if you specify the StartExpiresDate value of today's date and the E
Type: System.DateTime
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -186,9 +177,6 @@ Accept wildcard characters: False
```
### -EndReceivedDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EndReceivedDate parameter specifies the latest messages to return in the results. Use this parameter with the StartReceivedDate parameter.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -197,6 +185,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -206,9 +195,6 @@ Accept wildcard characters: False
```
### -EntityType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EntityType parameter filters the results by EntityType. Valid values are:
- Email
@@ -220,6 +206,7 @@ The EntityType parameter filters the results by EntityType. Valid values are:
Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -229,15 +216,13 @@ Accept wildcard characters: False
```
### -IncludeMessagesFromBlockedSenderAddress
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The IncludeMessagesFromBlockedSenderAddress switch specifies whether to include quarantined messages from blocked senders in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -247,15 +232,13 @@ Accept wildcard characters: False
```
### -MessageId
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, `""`).
```yaml
Type: String
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -265,15 +248,13 @@ Accept wildcard characters: False
```
### -MyItems
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The MyItems switch filters the results by messages where you (the user that's running the command) are the recipient. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -283,15 +264,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -301,15 +280,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 1000. The default value is 100.
```yaml
Type: Int32
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -319,9 +296,6 @@ Accept wildcard characters: False
```
### -PolicyName
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The PolicyName parameter filters the results by the threat policy that quarantined the message (for example, an anti-malware policy or an anti-spam policy). You can use any value that uniquely identifies the policy. For example:
- Name
@@ -332,6 +306,7 @@ The PolicyName parameter filters the results by the threat policy that quarantin
Type: String
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -341,9 +316,6 @@ Accept wildcard characters: False
```
### -PolicyTypes
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The PolicyTypes parameter filters the results by the type of threat policy that quarantined the message. Valid values are:
- AntiMalwarePolicy
@@ -359,6 +331,7 @@ You can specify multiple values separated by commas.
Type: QuarantinePolicyTypeEnum[]
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -368,9 +341,6 @@ Accept wildcard characters: False
```
### -QuarantineTypes
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The QuarantineTypes parameter filters the results by what caused the message to be quarantined. Valid values are:
- Bulk
@@ -393,6 +363,7 @@ For files quarantined by Safe Attachments for SharePoint, OneDrive, and Microsof
Type: QuarantineMessageTypeEnum[]
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -402,15 +373,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: String[]
Parameter Sets: All
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -420,9 +389,6 @@ Accept wildcard characters: False
```
### -RecipientTag
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientTag parameter filters the results by the recipient's user tag value (for example, `Priority Account`). For more information about user tags, see [User tags in Defender for Office 365](https://learn.microsoft.com/defender-office-365/user-tags-about).
You can specify multiple values separated by commas.
@@ -431,6 +397,7 @@ You can specify multiple values separated by commas.
Type: String[]
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -440,9 +407,6 @@ Accept wildcard characters: False
```
### -ReleaseStatus
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The ReleaseStatus parameter filters the results by the release status of the message. Valid values are:
- Approved
@@ -461,6 +425,7 @@ You can specify multiple values separated by commas.
Type: ReleaseStatus[]
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -470,9 +435,6 @@ Accept wildcard characters: False
```
### -Reported
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Reported parameter filters the results by messages that have already been reported as false positives. Valid values are:
- $true: The command only returns quarantined messages that have already been reported as false positives.
@@ -482,6 +444,7 @@ The Reported parameter filters the results by messages that have already been re
Type: Boolean
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -491,15 +454,13 @@ Accept wildcard characters: False
```
### -SenderAddress
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The SenderAddress parameter filters the results by the sender's email address. You can specify multiple values separated by commas.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -509,9 +470,6 @@ Accept wildcard characters: False
```
### -StartExpiresDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The StartExpiresDate parameter specifies the earliest messages that will automatically be deleted from the quarantine. Use this parameter with the EndExpiresDate parameter.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -522,6 +480,7 @@ For example, if you specify the StartExpiresDate value of today's date and the E
Type: System.DateTime
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -531,9 +490,6 @@ Accept wildcard characters: False
```
### -StartReceivedDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The StartReceivedDate parameter specifies the earliest messages to return in the results. Use this parameter with the EndReceivedDate parameter.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -544,6 +500,7 @@ By default, if you don't use the StartReceivedDate and EndReceivedDate parameter
Type: System.DateTime
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -553,15 +510,13 @@ Accept wildcard characters: False
```
### -Subject
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Subject parameter filters the results by the subject field of the message. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -571,9 +526,6 @@ Accept wildcard characters: False
```
### -TeamsConversationTypes
-
-> Applicable: Security & Compliance
-
This parameter is available only in Security & Compliance PowerShell.
The TeamsConversationTypes parameters filters the results by Microsoft Teams conversation types. Valid values are:
@@ -587,6 +539,7 @@ You can specify multiple values separated by commas.
Type: Microsoft.Exchange.Management.FfoQuarantine.TeamsConversationType[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -596,9 +549,6 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Type parameter filters the results by what caused the message to be quarantined. Valid values are:
- Bulk
@@ -618,6 +568,7 @@ For files protected by Safe Attachments for SharePoint, OneDrive, and Microsoft
Type: Microsoft.Exchange.Management.FfoQuarantine.QuarantineMessageTypeEnum
Parameter Sets: Summary
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md b/exchange/exchange-ps/exchange/Get-QuarantineMessageHeader.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md
rename to exchange/exchange-ps/exchange/Get-QuarantineMessageHeader.md
index c7f2ec7c00..9dac21f945 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md
+++ b/exchange/exchange-ps/exchange/Get-QuarantineMessageHeader.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-quarantinemessageheader
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-QuarantineMessageHeader
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-quarantinemessageheader
-schema: 2.0.0
-title: Get-QuarantineMessageHeader
+ms.reviewer:
---
# Get-QuarantineMessageHeader
@@ -54,9 +53,6 @@ This example displays the message header of the first message that's returned by
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the quarantined message that you want to view the header for. The value is a unique quarantined message identifier in the format `GUID1\GUID2` (for example `c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7`).
You can find the Identity value for a quarantined message by using the Get-QuarantineMessage cmdlet.
@@ -65,6 +61,7 @@ You can find the Identity value for a quarantined message by using the Get-Quara
Type: QuarantineMessageIdentity
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -EntityType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EntityType parameter filters the results by EntityType. Valid values are:
- Email
@@ -88,6 +82,7 @@ The EntityType parameter filters the results by EntityType. Valid values are:
Type: Microsoft.Exchange.Management.FfoQuarantine.EntityType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientAddress parameter filters the results by the recipient's email address. You can specify multiple values separated by commas.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md b/exchange/exchange-ps/exchange/Get-QuarantinePolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md
rename to exchange/exchange-ps/exchange/Get-QuarantinePolicy.md
index b36d1fde0f..93177a8f2a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-QuarantinePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-quarantinepolicy
applicable: Exchange Online, Exchange Online Protection
+title: Get-QuarantinePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-quarantinepolicy
-schema: 2.0.0
-title: Get-QuarantinePolicy
+ms.reviewer:
---
# Get-QuarantinePolicy
@@ -58,9 +57,6 @@ This example returns detailed information about the default quarantine policy na
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the quarantine policy you want to view. You can use any value that uniquely identifies the quarantine policy. For example:
- Name
@@ -71,6 +67,7 @@ The Identity parameter specifies the quarantine policy you want to view. You can
Type: QuarantineTagIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 0
@@ -80,9 +77,6 @@ Accept wildcard characters: False
```
### -QuarantinePolicyType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The QuarantinePolicyType parameter filters the results by the specified quarantine policy type. Valid values are:
- QuarantinePolicy: This is the default value, and returns built-in and custom quarantine policies.
@@ -93,6 +87,7 @@ Type: QuarantinePolicyType
Parameter Sets: (All)
Aliases:
Accepted values: QuarantinePolicy, GlobalQuarantinePolicy
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md b/exchange/exchange-ps/exchange/Get-Queue.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Queue.md
rename to exchange/exchange-ps/exchange/Get-Queue.md
index a05d1686df..1b83dcd4a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md
+++ b/exchange/exchange-ps/exchange/Get-Queue.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-queue
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-Queue
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-queue
-schema: 2.0.0
-title: Get-Queue
+ms.reviewer:
---
# Get-Queue
@@ -88,15 +87,13 @@ This example lists only the external queues.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the queue. Valid input for this parameter uses the syntax Server\\Queue or Queue, for example, Mailbox01\\contoso.com or Unreachable. For details about queue identity, see [Queue identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity).
```yaml
Type: QueueIdentity
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -106,15 +103,13 @@ Accept wildcard characters: False
```
### -BookmarkIndex
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BookmarkIndex parameter specifies the position in the result set where the displayed results start. The value of this parameter is a 1-based index in the total result set. The BookmarkIndex parameter can't be used with the BookmarkObject parameter.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -124,15 +119,13 @@ Accept wildcard characters: False
```
### -BookmarkObject
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BookmarkObject parameter specifies the object in the result set where the displayed results start. The BookmarkObject parameter can't be used with the BookmarkIndex parameter.
```yaml
Type: ExtensibleQueueInfo
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -142,9 +135,6 @@ Accept wildcard characters: False
```
### -Exclude
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Exclude parameter specifies the types of queues you want to exclude from the results. Valid values for this parameter are:
- Internal
@@ -155,6 +145,7 @@ The Exclude parameter specifies the types of queues you want to exclude from the
Type: QueueViewerIncludesAndExcludes
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -164,9 +155,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Filter parameter specifies one or more queues by using OPATH filter syntax. The OPATH filter includes a queue property name followed by a comparison operator and value (for example, `"NextHopDomain -eq 'contoso.com'"`). For details about filterable queue properties and comparison operators, see [Queue properties in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
You can specify multiple criteria by using the and comparison operator. Property values that aren't expressed as an integer must be enclosed in quotation marks (").
@@ -175,6 +163,7 @@ You can specify multiple criteria by using the and comparison operator. Property
Type: String
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -184,9 +173,6 @@ Accept wildcard characters: False
```
### -Include
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Include parameter specifies the types of queues you want to include the results. Valid values for this parameter are:
- Internal
@@ -197,6 +183,7 @@ The Include parameter specifies the types of queues you want to include the resu
Type: QueueViewerIncludesAndExcludes
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -206,15 +193,13 @@ Accept wildcard characters: False
```
### -IncludeBookmark
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeBookmark parameter specifies whether to include the bookmark object when the query results are displayed. The IncludeBookmark parameter is valid when it's used with the BookmarkObject or BookmarkIndex parameters. If you don't specify a value for the IncludeBookmark parameter, the default value of $true is used.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -224,15 +209,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -242,15 +225,13 @@ Accept wildcard characters: False
```
### -ReturnPageInfo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReturnPageInfo parameter is a hidden parameter. Use it to return information about the total number of results and the index of the first object of the current page. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -260,15 +241,13 @@ Accept wildcard characters: False
```
### -SearchForward
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SearchForward parameter specifies whether to search forward or backward in the result set. The default value is $true. This value causes the result page to be calculated forward from either the start of the result set or forward from a bookmark if specified.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -278,9 +257,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -296,6 +272,7 @@ You can use the Server parameter and the Filter parameter in the same command. Y
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -305,9 +282,6 @@ Accept wildcard characters: False
```
### -SortOrder
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SortOrder parameter specifies an array of message properties used to control the sort order of the result set. Separate each property by using a comma. Prepend a plus sign (+) symbol to the beginning of the property name to display the results in ascending order. Prepend a minus sign (-) symbol to the beginning of the property name to display the results in descending order.
If you don't specify a sort order, the result set is displayed in ascending order by QueueIdentity.
@@ -316,6 +290,7 @@ If you don't specify a sort order, the result set is displayed in ascending orde
Type: QueueViewerSortOrderEntry[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md b/exchange/exchange-ps/exchange/Get-QueueDigest.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md
rename to exchange/exchange-ps/exchange/Get-QueueDigest.md
index c4277836aa..a45a074bd3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md
+++ b/exchange/exchange-ps/exchange/Get-QueueDigest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-queuedigest
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-QueueDigest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-queuedigest
-schema: 2.0.0
-title: Get-QueueDigest
+ms.reviewer:
---
# Get-QueueDigest
@@ -89,9 +88,6 @@ This example returns information about all queues in the DAG named DAG01.
## PARAMETERS
### -Dag
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Dag parameter filters the delivery queue results by DAG. You can specify any value that uniquely identifies the DAG. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
You can't use the Dag parameter with the Server, Site or Forest parameters.
@@ -100,6 +96,7 @@ You can't use the Dag parameter with the Server, Site or Forest parameters.
Type: MultiValuedProperty
Parameter Sets: Dag
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -109,9 +106,6 @@ Accept wildcard characters: False
```
### -Forest
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Forest switch filters the delivery queue results by Active Directory forest. You don't need to specify a value with the Forest switch.
You can't use the Forest switch with the Server, Site or Dag parameters.
@@ -120,6 +114,7 @@ You can't use the Forest switch with the Server, Site or Dag parameters.
Type: SwitchParameter
Parameter Sets: Forest
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -129,9 +124,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter filters the delivery queue results by Exchange server. You can specify any value that uniquely identifies the server. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
You can't use the Server parameter with the Dag, Site or Forest parameters.
@@ -140,6 +132,7 @@ You can't use the Server parameter with the Dag, Site or Forest parameters.
Type: MultiValuedProperty
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -149,9 +142,6 @@ Accept wildcard characters: False
```
### -Site
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Site parameter filters the delivery queue results by Active Directory site. You can specify any value that uniquely identifies the site. You can specify multiple sites separated by commas.
You can't use the Site parameter with the Server, Dag or Forest parameters.
@@ -160,6 +150,7 @@ You can't use the Site parameter with the Server, Dag or Forest parameters.
Type: MultiValuedProperty
Parameter Sets: Site
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -169,15 +160,13 @@ Accept wildcard characters: False
```
### -DetailsLevel
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DetailsLevel parameter specifies the level of detail to display in the results. Valid values for this parameter are None, Normal and Verbose. The default value is Normal.
```yaml
Type: DetailsLevel
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -187,9 +176,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Filter parameter specifies one or more queues by using OPATH filter syntax. The OPATH filter includes a queue property name followed by a comparison operator and value (for example, `"NextHopDomain -eq 'contoso.com'"`). For details about filterable queue properties and comparison operators, see [Queue properties in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
You can specify multiple criteria by using the and comparison operator. Property values that aren't expressed as an integer must be enclosed in quotation marks (").
@@ -198,6 +184,7 @@ You can specify multiple criteria by using the and comparison operator. Property
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -207,9 +194,6 @@ Accept wildcard characters: False
```
### -GroupBy
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The GroupedBy parameter sorts the messages in the delivery queue results. Valid values are:
- DeliveryType
@@ -226,6 +210,7 @@ The GroupedBy parameter sorts the messages in the delivery queue results. Valid
Type: QueueDigestGroupBy
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -235,15 +220,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter filters the delivery queue results by the number of messages in the queue. Valid input for this parameter is an integer. The default value is 1000. For example, if you specify the value 50, the command displays the 50 queues that contain the most messages.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -253,9 +236,6 @@ Accept wildcard characters: False
```
### -Timeout
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Timeout parameter specifies the number of seconds before the operation times out. The default value is 10 seconds.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -264,6 +244,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md b/exchange/exchange-ps/exchange/Get-RMSTemplate.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md
rename to exchange/exchange-ps/exchange/Get-RMSTemplate.md
index a4ee2746eb..e495368203 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md
+++ b/exchange/exchange-ps/exchange/Get-RMSTemplate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-rmstemplate
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-RMSTemplate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-rmstemplate
-schema: 2.0.0
-title: Get-RMSTemplate
+ms.reviewer:
---
# Get-RMSTemplate
@@ -54,15 +53,13 @@ This example retrieves the Company Confidential RMS template.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the name of the RMS template.
```yaml
Type: RmsTemplateIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -83,6 +77,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -110,9 +103,6 @@ Accept wildcard characters: False
```
### -TrustedPublishingDomain
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The TrustedPublishingDomain parameter specifies the trusted publishing domain you want to search for RMS templates. You can use any value that uniquely identifies the trusted publishing domain, for example:
@@ -125,6 +115,7 @@ The TrustedPublishingDomain parameter specifies the trusted publishing domain yo
Type: RmsTrustedPublishingDomainIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -134,9 +125,6 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The Type parameter specifies the type of RMS template. Use one of the following values:
@@ -149,6 +137,7 @@ The Type parameter specifies the type of RMS template. Use one of the following
Type: RmsTemplateType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md b/exchange/exchange-ps/exchange/Get-ReceiveConnector.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md
rename to exchange/exchange-ps/exchange/Get-ReceiveConnector.md
index fe560729f4..f34ec98584 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md
+++ b/exchange/exchange-ps/exchange/Get-ReceiveConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-receiveconnector
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ReceiveConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-receiveconnector
-schema: 2.0.0
-title: Get-ReceiveConnector
+ms.reviewer:
---
# Get-ReceiveConnector
@@ -59,9 +58,6 @@ This example displays detailed information for the Receive connector named Recei
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Receive connector that you want to view. You can use any value that uniquely identifies the Receive connector. For example:
- Name
@@ -75,6 +71,7 @@ You can't use this parameter with the Server parameter.
Type: ReceiveConnectorIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -84,9 +81,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -95,6 +89,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -104,9 +99,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter filters the results by the specified Mailbox server or Edge Transport server. You can use any value that uniquely identifies the server. For example:
- Name
@@ -120,6 +112,7 @@ You can't use this parameter with the Identity parameter.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md b/exchange/exchange-ps/exchange/Get-Recipient.md
similarity index 86%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md
rename to exchange/exchange-ps/exchange/Get-Recipient.md
index 4497518c48..4b5a71f8b1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md
+++ b/exchange/exchange-ps/exchange/Get-Recipient.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-recipient
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-Recipient
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-recipient
-schema: 2.0.0
-title: Get-Recipient
+ms.reviewer:
---
# Get-Recipient
@@ -145,9 +144,6 @@ This example retrieves information about all the mail contacts in your organizat
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the recipient object that you want to view. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -161,6 +157,7 @@ The Identity parameter specifies the recipient object that you want to view. You
Type: RecipientIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: 1
@@ -170,9 +167,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -185,6 +179,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -194,9 +189,6 @@ Accept wildcard characters: False
```
### -AuthenticationType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AuthenticationType parameter specifies the recipient by authentication type. Use one of the following values:
@@ -208,6 +200,7 @@ The AuthenticationType parameter specifies the recipient by authentication type.
Type: AuthenticationType
Parameter Sets: AnrSet, Identity, RecipientPreviewFilterSet
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -217,15 +210,13 @@ Accept wildcard characters: False
```
### -BookmarkDisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -235,9 +226,6 @@ Accept wildcard characters: False
```
### -Capabilities
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -246,6 +234,7 @@ This parameter is reserved for internal Microsoft use.
Type: MultiValuedProperty
Parameter Sets: AnrSet, Identity, RecipientPreviewFilterSet
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -255,9 +244,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -268,6 +254,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -277,9 +264,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Database parameter return all recipients stored on the specified mailbox database. You can use any value that uniquely identifies the database. For example:
@@ -292,6 +276,7 @@ The Database parameter return all recipients stored on the specified mailbox dat
Type: DatabaseIdParameter
Parameter Sets: DatabaseSet
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -301,9 +286,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -312,6 +294,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -321,9 +304,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -339,6 +319,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -348,9 +329,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -364,6 +342,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -373,15 +352,13 @@ Accept wildcard characters: False
```
### -IncludeBookmarkObject
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -391,9 +368,6 @@ Accept wildcard characters: False
```
### -IncludeManagerWithDisplayName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeManagerWithDisplayName Description }}
@@ -402,6 +376,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, AnrSet, RecipientPreviewFilterSet
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -411,9 +386,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedRecipients
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The IncludeSoftDeletedRecipients switch specifies whether to include soft deleted recipients in the results. You don't need to specify a value with this switch.
Soft-deleted recipients are deleted recipients that are still recoverable.
@@ -424,6 +396,7 @@ Soft-deleted recipients are deleted recipients that are still recoverable.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -433,9 +406,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -447,6 +417,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -456,15 +427,13 @@ Accept wildcard characters: False
```
### -Properties
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -474,15 +443,13 @@ Accept wildcard characters: False
```
### -PropertySet
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: PropertySet
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -492,9 +459,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -507,6 +471,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -516,15 +481,13 @@ Accept wildcard characters: False
```
### -RecipientPreviewFilter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientPreviewFilter parameter tests a recipient filter that you would use in a dynamic distribution group, address list, or email address policy. This parameter uses the LDAP filter syntax.
```yaml
Type: String
Parameter Sets: RecipientPreviewFilterSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -534,9 +497,6 @@ Accept wildcard characters: False
```
### -RecipientType
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientType parameter filters the results by the specified recipient type. Valid values are:
- DynamicDistributionGroup
@@ -554,6 +514,7 @@ You can specify multiple values separated by commas.
Type: RecipientType[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -563,9 +524,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are:
- DiscoveryMailbox
@@ -605,6 +563,7 @@ The value of the RecipientType parameter affects the values that you can use for
Type: RecipientTypeDetails[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -614,15 +573,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -632,9 +589,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -654,6 +608,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md b/exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md
rename to exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md
index 050feb8da1..76a02ece24 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md
+++ b/exchange/exchange-ps/exchange/Get-RecipientFilterConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-recipientfilterconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-RecipientFilterConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-recipientfilterconfig
-schema: 2.0.0
-title: Get-RecipientFilterConfig
+ms.reviewer:
---
# Get-RecipientFilterConfig
@@ -42,15 +41,13 @@ This example returns detailed information about the recipient filter configurati
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -60,9 +57,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -71,6 +65,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md b/exchange/exchange-ps/exchange/Get-RecipientPermission.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md
rename to exchange/exchange-ps/exchange/Get-RecipientPermission.md
index 65d31fe008..985fc7ff66 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md
+++ b/exchange/exchange-ps/exchange/Get-RecipientPermission.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-recipientpermission
applicable: Exchange Online
+title: Get-RecipientPermission
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-recipientpermission
-schema: 2.0.0
-title: Get-RecipientPermission
+ms.reviewer:
---
# Get-RecipientPermission
@@ -59,9 +58,6 @@ This example lists the users who have SendAs permission on the mailbox Help Desk
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter identifies the recipient that you want to view. The user or group specified by the Trustee parameter has Send As permissions on this recipient. You can specify any type of recipient, for example:
- Mailboxes
@@ -83,6 +79,7 @@ You can use any value that uniquely identifies the recipient. For example:
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -92,15 +89,13 @@ Accept wildcard characters: False
```
### -AccessRights
-
-> Applicable: Exchange Online
-
The AccessRights parameter filters the results by permission. The only valid value for this parameter is SendAs.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -110,15 +105,13 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Online
-
The ReadFromDomainController parameter specifies that the user information is read from a domain controller in the user's domain. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -128,15 +121,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -146,9 +137,6 @@ Accept wildcard characters: False
```
### -Trustee
-
-> Applicable: Exchange Online
-
The Trustee parameter filters the results by who has Send As permissions on the specified recipient. You can specify the following types of users or groups (security principals) for this parameter:
- Mailbox users
@@ -172,6 +160,7 @@ You can use any value that uniquely identifies the user or group. For example:
Type: SecurityPrincipalIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md b/exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md
rename to exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md
index e11d4e6142..8f2d888cba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md
+++ b/exchange/exchange-ps/exchange/Get-RecipientStatisticsReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-recipientstatisticsreport
applicable: Exchange Online
+title: Get-RecipientStatisticsReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-recipientstatisticsreport
-schema: 2.0.0
-title: Get-RecipientStatisticsReport
+ms.reviewer:
---
# Get-RecipientStatisticsReport
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecordReviewNotificationTemplateConfig.md b/exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RecordReviewNotificationTemplateConfig.md
rename to exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md
index a6dfb25f93..4f413a8bf3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecordReviewNotificationTemplateConfig.md
+++ b/exchange/exchange-ps/exchange/Get-RecordReviewNotificationTemplateConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-recordreviewnotificationtemplateconfig
applicable: Security & Compliance
+title: Get-RecordReviewNotificationTemplateConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-recordreviewnotificationtemplateconfig
-schema: 2.0.0
-title: Get-RecordReviewNotificationTemplateConfig
+ms.reviewer:
---
# Get-RecordReviewNotificationTemplateConfig
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md b/exchange/exchange-ps/exchange/Get-RecoverableItems.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md
rename to exchange/exchange-ps/exchange/Get-RecoverableItems.md
index 796b999fed..aebb11746e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md
+++ b/exchange/exchange-ps/exchange/Get-RecoverableItems.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-recoverableitems
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-RecoverableItems
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-recoverableitems
-schema: 2.0.0
-title: Get-RecoverableItems
+ms.reviewer:
---
# Get-RecoverableItems
@@ -75,9 +74,6 @@ This example returns all of the available recoverable deleted messages with the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox that contains the deleted items that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -95,8 +91,9 @@ In Exchange Online, you can specify multiple mailboxes separated by commas. If t
```yaml
Type: GeneralMailboxOrMailUserIdParameter
-Parameter Sets: OnPremises, Cloud
+Parameter Sets: OnPremises
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -105,10 +102,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -EntryID
+```yaml
+Type: GeneralMailboxOrMailUserIdParameter[]
+Parameter Sets: Cloud
+Aliases:
+Applicable: Exchange Online
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+Required: False
+Position: 1
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -EntryID
The EntryID parameter specifies the deleted item that you want to restore. The EntryID value for the deleted item is unique in the mailbox.
You can find the EntryID for specific items by using other search filters on the Get-RecoverableItems cmdlet (subject, date range, etc.).
@@ -117,6 +124,7 @@ You can find the EntryID for specific items by using other search filters on the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -126,9 +134,6 @@ Accept wildcard characters: False
```
### -FilterEndTime
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FilterEndTime specifies the end date/time of the date range. This parameter uses the LastModifiedTime value of the item.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -137,6 +142,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -146,9 +152,6 @@ Accept wildcard characters: False
```
### -FilterItemType
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FilterItemType parameter filters the results by the specified MessageClass (ItemClass) property value of the deleted item. For example:
- IPM.Appointment (Meetings and appointments)
@@ -161,6 +164,7 @@ The FilterItemType parameter filters the results by the specified MessageClass (
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -170,9 +174,6 @@ Accept wildcard characters: False
```
### -FilterStartTime
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FilterStartTime specifies the start date/time of the date range. This parameter uses the LastModifiedTime value of the item.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -181,6 +182,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -190,15 +192,13 @@ Accept wildcard characters: False
```
### -LastParentFolderID
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The LastParentFolderID parameter specifies the FolderID value of the item before it was deleted. For example, 53B93149989CA54DBC9702AE619B9CCA000062CE9397.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -208,9 +208,6 @@ Accept wildcard characters: False
```
### -MaxParallelSize
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The MaxParallelSize parameter specifies the maximum number of mailboxes that are processed by the command in parallel. A valid value is an integer from 1 to 10. Typically, a higher value decreases the amount of time it takes to complete the command on multiple mailboxes.
@@ -221,6 +218,7 @@ The value of this parameter has no effect when the Identity parameter specifies
Type: Int32
Parameter Sets: Cloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -230,9 +228,6 @@ Accept wildcard characters: False
```
### -PolicyTag
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill PolicyTag Description }}
@@ -241,6 +236,7 @@ This parameter is available only in the cloud-based service.
Type: String[]
Parameter Sets: Cloud
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -250,15 +246,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -268,9 +262,6 @@ Accept wildcard characters: False
```
### -SkipCount
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill SkipCount Description }}
@@ -279,6 +270,7 @@ This parameter is available only in the cloud-based service.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -288,9 +280,6 @@ Accept wildcard characters: False
```
### -SourceFolder
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SourceFolder parameter specifies where to search for deleted items in the mailbox. Valid values are:
- DeletedItems: The Deleted Items folder.
@@ -305,6 +294,7 @@ If you don't use this parameter, the command searches those three folders.
Type: RecoverableItemsFolderType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -314,15 +304,13 @@ Accept wildcard characters: False
```
### -SubjectContains
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SubjectContains parameter filters the items by the specified text value in the Subject field. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RegulatoryComplianceUI.md b/exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RegulatoryComplianceUI.md
rename to exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md
index 3b3f107381..69ceb96099 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RegulatoryComplianceUI.md
+++ b/exchange/exchange-ps/exchange/Get-RegulatoryComplianceUI.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-regulatorycomplianceui
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/get-regulatorycomplianceui
+applicable: Security & Compliance
title: Get-RegulatoryComplianceUI
+schema: 2.0.0
---
# Get-RegulatoryComplianceUI
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md b/exchange/exchange-ps/exchange/Get-RemoteDomain.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md
rename to exchange/exchange-ps/exchange/Get-RemoteDomain.md
index 8fa4cd2d7e..ea01811a75 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md
+++ b/exchange/exchange-ps/exchange/Get-RemoteDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-remotedomain
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-RemoteDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-remotedomain
-schema: 2.0.0
-title: Get-RemoteDomain
+ms.reviewer:
---
# Get-RemoteDomain
@@ -57,9 +56,6 @@ This example returns all domains where Transport Neutral Encapsulation Format (T
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the remote domain that you want to view. You can use any value that uniquely identifies the remote domain. For example:
- Name
@@ -70,6 +66,7 @@ The Identity parameter specifies the remote domain that you want to view. You ca
Type: RemoteDomainIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -92,6 +86,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -101,9 +96,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -112,6 +104,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md b/exchange/exchange-ps/exchange/Get-RemoteMailbox.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md
rename to exchange/exchange-ps/exchange/Get-RemoteMailbox.md
index 288f6d8327..f40415ec08 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md
+++ b/exchange/exchange-ps/exchange/Get-RemoteMailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-remotemailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-RemoteMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-remotemailbox
-schema: 2.0.0
-title: Get-RemoteMailbox
+ms.reviewer:
---
# Get-RemoteMailbox
@@ -84,9 +83,6 @@ First, run the following command to prompt you for your credentials and then sto
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the remote mailbox that you want to view. You can use any value that uniquely identifies the remote mailbox. For example:
- Name
@@ -104,6 +100,7 @@ The Identity parameter specifies the remote mailbox that you want to view. You c
Type: RemoteMailboxIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -113,9 +110,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -128,6 +122,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -137,15 +132,13 @@ Accept wildcard characters: False
```
### -Archive
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Archive switch is required to return the user's archive mailbox in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -155,9 +148,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -166,6 +156,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -175,15 +166,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -193,9 +182,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -211,6 +197,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -220,9 +207,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -234,6 +218,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -243,9 +228,6 @@ Accept wildcard characters: False
```
### -OnPremisesOrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OnPremisesOrganizationalUnit parameter filters the results by the object's location in Active Directory.
Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
@@ -259,6 +241,7 @@ Valid input for this parameter is an organizational unit (OU) or domain that's r
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -268,9 +251,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -281,6 +261,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -290,9 +271,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
**Note**: Limitations on domain controllers might affect the number of results returned for the value unlimited. For more information, see [this article](https://learn.microsoft.com/troubleshoot/windows-server/identity/domain-controller-returns-500-values-ldap-response).
@@ -301,6 +279,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -310,9 +289,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -327,6 +303,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md b/exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md
rename to exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md
index 8c2a4481b7..134a709559 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md
+++ b/exchange/exchange-ps/exchange/Get-ReportExecutionInstance.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-reportexecutioninstance
applicable: Exchange Online, Exchange Online Protection
+title: Get-ReportExecutionInstance
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-reportexecutioninstance
-schema: 2.0.0
-title: Get-ReportExecutionInstance
+ms.reviewer:
---
# Get-ReportExecutionInstance
@@ -49,15 +48,13 @@ This example returns detailed information for the specified report execution ins
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the report execution instance that you want to view. The identity of the instance is a unique GUID value.
```yaml
Type: InstanceIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -67,15 +64,13 @@ Accept wildcard characters: False
```
### -ScheduleId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ScheduleId parameter filters the results by the specified ScheduleId property value, which is a GUID. Note that multiple report execution instances can have the same ScheduleId value.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md b/exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md
rename to exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md
index 5e6ea078a9..483f073460 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-ReportSubmissionPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-reportsubmissionpolicy
applicable: Exchange Online
+title: Get-ReportSubmissionPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-reportsubmissionpolicy
-schema: 2.0.0
-title: Get-ReportSubmissionPolicy
+ms.reviewer:
---
# Get-ReportSubmissionPolicy
@@ -44,15 +43,13 @@ This example returns the settings of the report submission policy in your organi
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the report submission policy that you want to view. The only available policy is named DefaultReportSubmissionPolicy.
```yaml
Type: ReportSubmissionPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md b/exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md
rename to exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md
index 90b8ad8b50..f64f8d899b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/exchange/Get-ReportSubmissionRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-reportsubmissionrule
applicable: Exchange Online
+title: Get-ReportSubmissionRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-reportsubmissionrule
-schema: 2.0.0
-title: Get-ReportSubmissionRule
+ms.reviewer:
---
# Get-ReportSubmissionRule
@@ -40,15 +39,13 @@ This example returns detailed information about the report submission rule in yo
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the report submission rule that you want to view. The default rule is named DefaultReportSubmissionRule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -58,9 +55,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online
-
The State parameter filters the results by whether the report submission rule is enabled or disabled. Valid values are:
- Disabled
@@ -73,6 +67,7 @@ Type: RuleState
Parameter Sets: (All)
Aliases:
Accepted values: Enabled, Disabled
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md b/exchange/exchange-ps/exchange/Get-ResourceConfig.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md
rename to exchange/exchange-ps/exchange/Get-ResourceConfig.md
index fc626e15b6..e5087116d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md
+++ b/exchange/exchange-ps/exchange/Get-ResourceConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-resourceconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-ResourceConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-resourceconfig
-schema: 2.0.0
-title: Get-ResourceConfig
+ms.reviewer:
---
# Get-ResourceConfig
@@ -42,9 +41,6 @@ This example returns all of the available custom room and equipment mailbox prop
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -53,6 +49,7 @@ This parameter is reserved for internal Microsoft use.
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -62,9 +59,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -73,6 +67,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md b/exchange/exchange-ps/exchange/Get-ResubmitRequest.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md
rename to exchange/exchange-ps/exchange/Get-ResubmitRequest.md
index aa641f4105..e6837d4223 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md
+++ b/exchange/exchange-ps/exchange/Get-ResubmitRequest.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-resubmitrequest
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ResubmitRequest
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-resubmitrequest
-schema: 2.0.0
-title: Get-ResubmitRequest
+ms.reviewer:
---
# Get-ResubmitRequest
@@ -49,15 +48,13 @@ This example returns details about the resubmit request with the identity 1.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the resubmit request you want to view. Each resubmit request is identified by an incremented integer value.
```yaml
Type: ResubmitRequestIdentityParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -83,6 +77,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md
rename to exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md
index 6f0edb31bd..fbb20052f5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-retentioncompliancepolicy
applicable: Security & Compliance
+title: Get-RetentionCompliancePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-retentioncompliancepolicy
-schema: 2.0.0
-title: Get-RetentionCompliancePolicy
+ms.reviewer:
---
# Get-RetentionCompliancePolicy
@@ -62,9 +61,6 @@ This example displays detailed information for the policy named "Regulation 123
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the retention policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -75,6 +71,7 @@ The Identity parameter specifies the retention policy that you want to view. You
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -84,9 +81,6 @@ Accept wildcard characters: False
```
### -DistributionDetail
-
-> Applicable: Security & Compliance
-
The DistributionDetail switch returns detailed policy distribution information in the DistributionResults property. You don't need to specify a value with this switch.
If you don't use this switch, the values of the DistributionStatus and \*Location property values will be inaccurate.
@@ -95,6 +89,7 @@ If you don't use this switch, the values of the DistributionStatus and \*Locatio
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -104,15 +99,13 @@ Accept wildcard characters: False
```
### -ErrorPolicyOnly
-
-> Applicable: Security & Compliance
-
The ErrorPolicyOnly switch specifies whether to show only policies that have distribution errors in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -122,15 +115,13 @@ Accept wildcard characters: False
```
### -ExcludeTeamsPolicy
-
-> Applicable: Security & Compliance
-
The ExcludeTeamsPolicy switch specifies whether to exclude Teams policies from the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -140,9 +131,6 @@ Accept wildcard characters: False
```
### -IncludeTestModeResults
-
-> Applicable: Security & Compliance
-
The IncludeTestModeResults switch specifies whether to include the status of test mode in the policy details. You don't need to specify a value with this switch.
For more information about simulation mode, see [Learn about simulation mode](https://learn.microsoft.com/purview/apply-retention-labels-automatically#learn-about-simulation-mo).
@@ -151,6 +139,7 @@ For more information about simulation mode, see [Learn about simulation mode](ht
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -160,15 +149,13 @@ Accept wildcard characters: False
```
### -PriorityCleanup
-
-> Applicable: Security & Compliance
-
{{ Fill PriorityCleanup Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -178,9 +165,6 @@ Accept wildcard characters: False
```
### -RetentionRuleTypes
-
-> Applicable: Security & Compliance
-
The RetentionRuleTypes switch specifies whether to return the value of the RetentionRuleTypes and HasRules properties in the results. You don't need to specify a value with this switch.
To see the RetentionRuleTypes property, you need to pipe the command to a formatting cmdlet. For example, `Get-RetentionCompliancePolicy -RetentionRuleTypes | Format-Table -Auto Name,RetentionRuleTypes`. If you don't use the RetentionRuleTypes switch, the values RetentionRuleTypes appears blank and HasRules appears False.
@@ -189,6 +173,7 @@ To see the RetentionRuleTypes property, you need to pipe the command to a format
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -198,15 +183,13 @@ Accept wildcard characters: False
```
### -TeamsPolicyOnly
-
-> Applicable: Security & Compliance
-
The TeamsPolicyOnly switch specifies whether to show only Teams policies in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RetentionComplianceRule.md
rename to exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md
index 4340821384..9c1279ce96 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionComplianceRule.md
+++ b/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-retentioncompliancerule
applicable: Security & Compliance
+title: Get-RetentionComplianceRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-retentioncompliancerule
-schema: 2.0.0
-title: Get-RetentionComplianceRule
+ms.reviewer:
---
# Get-RetentionComplianceRule
@@ -57,9 +56,6 @@ This example displays detailed information for the retention rule named "30 Day
## PARAMETERS
### -Identity
-
-> Applicable: Security & Compliance
-
The Identity parameter specifies the retention rule you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -70,6 +66,7 @@ The Identity parameter specifies the retention rule you want to view. You can us
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter filters the retention rule results by the associated retention policy. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -94,6 +88,7 @@ You can use this parameter with the Identity parameter in the same command.
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -103,15 +98,13 @@ Accept wildcard characters: False
```
### -PriorityCleanup
-
-> Applicable: Security & Compliance
-
{{ Fill PriorityCleanup Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md b/exchange/exchange-ps/exchange/Get-RetentionEvent.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md
rename to exchange/exchange-ps/exchange/Get-RetentionEvent.md
index e8c112c3ed..c650acf830 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md
+++ b/exchange/exchange-ps/exchange/Get-RetentionEvent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-retentionevent
applicable: Exchange Online, Security & Compliance
+title: Get-RetentionEvent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-retentionevent
-schema: 2.0.0
-title: Get-RetentionEvent
+ms.reviewer:
---
# Get-RetentionEvent
@@ -50,15 +49,13 @@ This example returns detailed information about retention the specified retentio
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the retention event that you want to view.
```yaml
Type: EwsStoreObjectIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -68,15 +65,13 @@ Accept wildcard characters: False
```
### -AllStatus
-
-> Applicable: Exchange Online
-
The AllStatus switch specifies whether to include zero count events in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -86,15 +81,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md b/exchange/exchange-ps/exchange/Get-RetentionPolicy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md
rename to exchange/exchange-ps/exchange/Get-RetentionPolicy.md
index 4b13d321a9..231c381cff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-RetentionPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-retentionpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-RetentionPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-retentionpolicy
-schema: 2.0.0
-title: Get-RetentionPolicy
+ms.reviewer:
---
# Get-RetentionPolicy
@@ -44,15 +43,13 @@ This example returns all the properties of the retention policy RP Finance. The
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the policy name.
```yaml
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -62,9 +59,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -73,6 +67,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md b/exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md
rename to exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md
index 97f1c0a293..53ece7d08e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/exchange/Get-RetentionPolicyTag.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-retentionpolicytag
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-RetentionPolicyTag
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-retentionpolicytag
-schema: 2.0.0
-title: Get-RetentionPolicyTag
+ms.reviewer:
---
# Get-RetentionPolicyTag
@@ -84,15 +83,13 @@ This example returns all retention tags of Inbox and All types and pipes the res
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name of the tag.
```yaml
Type: RetentionPolicyTagIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -102,9 +99,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -113,6 +107,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -122,15 +117,13 @@ Accept wildcard characters: False
```
### -IncludeSystemTags
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludeSystemTags switch specifies whether to return any system tags. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -140,9 +133,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter returns the retention tags that are assigned to the retention policy that's applied to the specified mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -162,6 +152,7 @@ This parameter only returns default policy tags (DPTs) and personal tags; it doe
Type: MailboxIdParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -171,9 +162,6 @@ Accept wildcard characters: False
```
### -OptionalInMailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OptionalInMailbox parameter is used with the Mailbox parameter to return any opt-in retention tags that are assigned to the specified mailbox. You don't need to specify a value with this switch.
An opt-in retention tag is a personal tag that was explicitly assigned to the mailbox with the Set-RetentionPolicyTag -Mailbox -OptionalInMailbox command.
@@ -182,6 +170,7 @@ An opt-in retention tag is a personal tag that was explicitly assigned to the ma
Type: SwitchParameter
Parameter Sets: Mailbox
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -191,9 +180,6 @@ Accept wildcard characters: False
```
### -Types
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Types parameter specifies the type of retention tag to return. Valid values include:
- Calendar
@@ -218,6 +204,7 @@ The parameter accepts multiple values separated by a comma.
Type: ElcFolderType[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md b/exchange/exchange-ps/exchange/Get-ReviewItems.md
similarity index 97%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md
rename to exchange/exchange-ps/exchange/Get-ReviewItems.md
index 63618d7061..b9fa1c3b40 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md
+++ b/exchange/exchange-ps/exchange/Get-ReviewItems.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-reviewitems
applicable: Exchange Online
+title: Get-ReviewItems
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-reviewitems
-schema: 2.0.0
-title: Get-ReviewItems
+ms.reviewer:
---
# Get-ReviewItems
@@ -85,9 +84,6 @@ This example retrieves all items pending disposition for the label with the immu
## PARAMETERS
### -TargetLabelId
-
-> Applicable: Exchange Online
-
The TargetLabelId parameter specifies the label that you want to retrieve review items for. A valid value for this parameter is the immutable ID of the label.
To get the immutable ID value of a label, replace \ with the name of the label, and then run the following command in Exchange Online PowerShell: `Get-ComplianceTag -Identity "" | select ImmutableId`.
@@ -96,6 +92,7 @@ To get the immutable ID value of a label, replace \ with th
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -105,9 +102,6 @@ Accept wildcard characters: False
```
### -Disposed
-
-> Applicable: Exchange Online
-
The Disposed parameter specifies whether to return disposed items instead of items pending disposition. Valid values are:
- $true: Return disposed items.
@@ -117,6 +111,7 @@ The Disposed parameter specifies whether to return disposed items instead of ite
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -126,9 +121,6 @@ Accept wildcard characters: False
```
### -IncludeHeaders
-
-> Applicable: Exchange Online
-
The IncludeHeaders parameter specifies whether headers are returned as a property with the review items. Valid values are:
- $true: Headers are returned as a property with the review items. This option is useful when converting the output to a PSObject in PowerShell or when exporting to CSV.
@@ -138,6 +130,7 @@ The IncludeHeaders parameter specifies whether headers are returned as a propert
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -147,9 +140,6 @@ Accept wildcard characters: False
```
### -PagingCookie
-
-> Applicable: Exchange Online
-
The PagingCookie parameter identifies the page to retrieve. This parameter is useful in the following scenarios:
- To avoid throttling while retrieving a large number of items.
@@ -161,6 +151,7 @@ The PagingCookie value is returned in the PaginationCookie property each time th
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md b/exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md
rename to exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md
index 0265d8527c..20474cb2b2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-RoleAssignmentPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-roleassignmentpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-RoleAssignmentPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-roleassignmentpolicy
-schema: 2.0.0
-title: Get-RoleAssignmentPolicy
+ms.reviewer:
---
# Get-RoleAssignmentPolicy
@@ -64,15 +63,13 @@ For more information about pipelining and the Format-List cmdlet, see [About Pip
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the name of the assignment policy to view. If the name contains spaces, enclose the name in quotation marks (").
```yaml
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -95,6 +89,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md b/exchange/exchange-ps/exchange/Get-RoleGroup.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md
rename to exchange/exchange-ps/exchange/Get-RoleGroup.md
index 2a63f95861..7e6cfdc324 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md
+++ b/exchange/exchange-ps/exchange/Get-RoleGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-rolegroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-RoleGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-rolegroup
-schema: 2.0.0
-title: Get-RoleGroup
+ms.reviewer:
---
# Get-RoleGroup
@@ -70,9 +69,6 @@ This example retrieves a list of all linked role groups and the Active Directory
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the role group to retrieve. If the name of the role group contains spaces, enclose the name in quotation marks (").
If the Identity parameter isn't specified, all role groups are returned.
@@ -81,6 +77,7 @@ If the Identity parameter isn't specified, all role groups are returned.
Type: RoleGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: 1
@@ -90,9 +87,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -101,6 +95,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -137,6 +129,7 @@ You can filter on the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -146,9 +139,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -161,6 +151,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -170,15 +161,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -188,9 +177,6 @@ Accept wildcard characters: False
```
### -ShowPartnerLinked
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is functional only in the cloud-based service.
This ShowPartnerLinked switch specifies whether to return built-in role groups that are of type PartnerRoleGroup. You don't need to specify a value with this switch.
@@ -201,6 +187,7 @@ This type of role group is used in the cloud-based service to allow partner serv
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -210,9 +197,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -226,6 +210,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md b/exchange/exchange-ps/exchange/Get-RoleGroupMember.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md
rename to exchange/exchange-ps/exchange/Get-RoleGroupMember.md
index eb04094c83..8416becc8f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md
+++ b/exchange/exchange-ps/exchange/Get-RoleGroupMember.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-rolegroupmember
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-RoleGroupMember
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-rolegroupmember
-schema: 2.0.0
-title: Get-RoleGroupMember
+ms.reviewer:
---
# Get-RoleGroupMember
@@ -53,15 +52,13 @@ This example retrieves a list of all the members of the Organization Administrat
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the role group for which member information should be retrieved. If the role group name contains spaces, enclose the name in quotation marks (").
```yaml
Type: RoleGroupMemberIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -82,6 +76,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -91,9 +86,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -106,6 +98,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -115,15 +108,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md b/exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md
rename to exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md
index 02c53261b2..2f0f384197 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md
+++ b/exchange/exchange-ps/exchange/Get-RoutingGroupConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-routinggroupconnector
applicable: Exchange Server 2010
+title: Get-RoutingGroupConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-routinggroupconnector
-schema: 2.0.0
-title: Get-RoutingGroupConnector
+ms.reviewer:
---
# Get-RoutingGroupConnector
@@ -44,15 +43,13 @@ This example displays detailed configuration information for the routing group c
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the name or GUID of the routing group connector. The name is expressed as [[Administrative Group Name\\]Routing Group Name]\\Routing Group Connector Name. You can use the wildcard character (\*) as part of the administrative group or routing group name.
```yaml
Type: RoutingGroupConnectorIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: 1
@@ -62,15 +59,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md b/exchange/exchange-ps/exchange/Get-RpcClientAccess.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md
rename to exchange/exchange-ps/exchange/Get-RpcClientAccess.md
index 558b8e2687..adedda699a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md
+++ b/exchange/exchange-ps/exchange/Get-RpcClientAccess.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-rpcclientaccess
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-RpcClientAccess
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-rpcclientaccess
-schema: 2.0.0
-title: Get-RpcClientAccess
+ms.reviewer:
---
# Get-RpcClientAccess
@@ -49,15 +48,13 @@ This example returns detailed information for the RPC Client Access service on t
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that you want to view.
You can use any value that uniquely identifies the server. For example:
@@ -83,6 +77,7 @@ You can use any value that uniquely identifies the server. For example:
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md b/exchange/exchange-ps/exchange/Get-SCInsights.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md
rename to exchange/exchange-ps/exchange/Get-SCInsights.md
index 4ff893c003..7675f4455f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md
+++ b/exchange/exchange-ps/exchange/Get-SCInsights.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-scinsights
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-SCInsights
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-scinsights
-schema: 2.0.0
-title: Get-SCInsights
+ms.reviewer:
---
# Get-SCInsights
@@ -56,9 +55,6 @@ This example return insights data for March 15, 2018.
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
To specify a date/time value for this parameter, use either of the following options:
@@ -70,6 +66,7 @@ To specify a date/time value for this parameter, use either of the following opt
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md b/exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md
rename to exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md
index 126fcd4417..1330056090 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-SafeAttachmentPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-safeattachmentpolicy
applicable: Exchange Online
+title: Get-SafeAttachmentPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-safeattachmentpolicy
-schema: 2.0.0
-title: Get-SafeAttachmentPolicy
+ms.reviewer:
---
# Get-SafeAttachmentPolicy
@@ -50,9 +49,6 @@ This example shows detailed information about the safe attachment policy named D
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the safe attachment policy that you want to view.
You can use any value that uniquely identifies the policy. For example:
@@ -65,6 +61,7 @@ You can use any value that uniquely identifies the policy. For example:
Type: SafeAttachmentPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md b/exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md
rename to exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md
index d5b539c3be..0dded56904 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/exchange/Get-SafeAttachmentRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-safeattachmentrule
applicable: Exchange Online
+title: Get-SafeAttachmentRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-safeattachmentrule
-schema: 2.0.0
-title: Get-SafeAttachmentRule
+ms.reviewer:
---
# Get-SafeAttachmentRule
@@ -51,9 +50,6 @@ This example returns detailed information about the safe attachment rule named R
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the safe attachment rule that you want to view.
You can use any value that uniquely identifies the rule. For example:
@@ -66,6 +62,7 @@ You can use any value that uniquely identifies the rule. For example:
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online
-
The State parameter filters the results by the state of the rule. Valid values are Enabled and Disabled.
```yaml
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md b/exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md
rename to exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md
index 921116fc89..27c72f641a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md
+++ b/exchange/exchange-ps/exchange/Get-SafeLinksAggregateReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-safelinksaggregatereport
applicable: Exchange Online
+title: Get-SafeLinksAggregateReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-safelinksaggregatereport
-schema: 2.0.0
-title: Get-SafeLinksAggregateReport
+ms.reviewer:
---
# Get-SafeLinksAggregateReport
@@ -57,9 +56,6 @@ This example returns results summarized by Email Client and Teams results for th
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online
-
The Action parameter filters the results by action. Valid values are:
- Allowed
@@ -77,6 +73,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -86,9 +83,6 @@ Accept wildcard characters: False
```
### -AppNameList
-
-> Applicable: Exchange Online
-
The AppNameList parameter filters the results by the app where the link was found. Valid values are:
- Email Client
@@ -101,6 +95,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -123,6 +115,7 @@ Yesterday is the most recent date that you can specify. You can't specify a date
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -132,9 +125,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -145,6 +135,7 @@ Yesterday is the most recent date that you can specify. You can't specify a date
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -154,9 +145,6 @@ Accept wildcard characters: False
```
### -SummarizeBy
-
-> Applicable: Exchange Online
-
The SummarizeBy parameter returns totals based on the values you specify. If your report filters data using any of the values accepted by this parameter, you can use the SummarizeBy parameter to summarize the results based on those values. To decrease the number of rows returned in the report, consider using the SummarizeBy parameter. Summarizing reduces the amount of data that's retrieved for the report, and delivers the report faster. For example, instead of seeing each instance of a specific value of Action or AppNameList on an individual row in the report, you can use the SummarizeBy parameter to see the total number of instances of that specific Action or App on one row in the report.
For this cmdlet, valid values are:
@@ -168,6 +156,7 @@ For this cmdlet, valid values are:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md b/exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md
rename to exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md
index 7d26d0b6c1..ef6379a4e6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md
+++ b/exchange/exchange-ps/exchange/Get-SafeLinksDetailReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-safelinksdetailreport
applicable: Exchange Online
+title: Get-SafeLinksDetailReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-safelinksdetailreport
-schema: 2.0.0
-title: Get-SafeLinksDetailReport
+ms.reviewer:
---
# Get-SafeLinksDetailReport
@@ -76,9 +75,6 @@ This example returns filters the results by the following information:
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online
-
The Action parameter filters the results by action. Valid values are:
- Allowed: URL was allowed due to a "Good" verdict.
@@ -98,6 +94,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -107,9 +104,6 @@ Accept wildcard characters: False
```
### -AppNameList
-
-> Applicable: Exchange Online
-
The AppNameList parameter filters the results by the app where the link was found. Valid values are:
- Email Client
@@ -122,6 +116,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -131,9 +126,6 @@ Accept wildcard characters: False
```
### -Domain
-
-> Applicable: Exchange Online
-
The Domain parameter filters the results by the domain in the URL.
You can specify multiple values separated by commas.
@@ -142,6 +134,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -151,9 +144,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -164,6 +154,7 @@ Yesterday is the most recent date that you can specify. You can't specify a date
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -173,15 +164,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -191,15 +180,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -209,9 +196,6 @@ Accept wildcard characters: False
```
### -RecipientAddress
-
-> Applicable: Exchange Online
-
The RecipientAddress parameter filters the results by the recipient's email address.
You can specify multiple values separated by commas.
@@ -220,6 +204,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -229,9 +214,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018.
@@ -242,6 +224,7 @@ Yesterday is the most recent date that you can specify. You can't specify a date
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md b/exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md
rename to exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md
index a50d913ed8..63a24625de 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-SafeLinksPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-safelinkspolicy
applicable: Exchange Online
+title: Get-SafeLinksPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-safelinkspolicy
-schema: 2.0.0
-title: Get-SafeLinksPolicy
+ms.reviewer:
---
# Get-SafeLinksPolicy
@@ -50,9 +49,6 @@ This example shows detailed information about the Safe Links policy named Contos
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the Safe Links policy that you want to view.
You can use any value that uniquely identifies the policy. For example:
@@ -65,6 +61,7 @@ You can use any value that uniquely identifies the policy. For example:
Type: SafeLinksPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md b/exchange/exchange-ps/exchange/Get-SafeLinksRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md
rename to exchange/exchange-ps/exchange/Get-SafeLinksRule.md
index 73b94df76c..279ebc68cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md
+++ b/exchange/exchange-ps/exchange/Get-SafeLinksRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-safelinksrule
applicable: Exchange Online
+title: Get-SafeLinksRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-safelinksrule
-schema: 2.0.0
-title: Get-SafeLinksRule
+ms.reviewer:
---
# Get-SafeLinksRule
@@ -51,9 +50,6 @@ This example returns detailed information about the Safe Links rule named Resear
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the Safe Links rule that you want to view.
You can use any value that uniquely identifies the rule. For example:
@@ -66,6 +62,7 @@ You can use any value that uniquely identifies the rule. For example:
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online
-
The State parameter filters the results by the state of the rule. Valid values are Enabled and Disabled.
```yaml
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md b/exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md
rename to exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md
index ddcea38f6a..562980e971 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/exchange/Get-SearchDocumentFormat.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-searchdocumentformat
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-SearchDocumentFormat
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-searchdocumentformat
-schema: 2.0.0
-title: Get-SearchDocumentFormat
+ms.reviewer:
---
# Get-SearchDocumentFormat
@@ -51,15 +50,13 @@ This example retrieves all properties of the docx file format.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the identity of a file format.
```yaml
Type: SearchDocumentFormatId
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
@@ -87,6 +81,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md b/exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md
rename to exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md
index ecff279a3f..a986f97d43 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-SecOpsOverridePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-secopsoverridepolicy
applicable: Exchange Online
+title: Get-SecOpsOverridePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-secopsoverridepolicy
-schema: 2.0.0
-title: Get-SecOpsOverridePolicy
+ms.reviewer:
---
# Get-SecOpsOverridePolicy
@@ -42,9 +41,6 @@ This example returns detailed information about the one and only SecOps mailbox
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the SecOps override policy that you want to modify. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -56,6 +52,7 @@ The Identity parameter specifies the SecOps override policy that you want to mod
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 0
@@ -65,15 +62,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md b/exchange/exchange-ps/exchange/Get-SecurityPrincipal.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md
rename to exchange/exchange-ps/exchange/Get-SecurityPrincipal.md
index 28d3b1a44d..458dcbe1b3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md
+++ b/exchange/exchange-ps/exchange/Get-SecurityPrincipal.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-securityprincipal
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-SecurityPrincipal
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-securityprincipal
-schema: 2.0.0
-title: Get-SecurityPrincipal
+ms.reviewer:
---
# Get-SecurityPrincipal
@@ -71,15 +70,13 @@ This example retrieves well-known security principals and displays only the Name
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the security principal. When the security principal is explicitly specified by using this parameter, no additional security principals are returned.
```yaml
Type: ExtendedSecurityPrincipalIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: 1
@@ -89,9 +86,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -100,6 +94,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -109,9 +104,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -127,6 +119,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -136,9 +129,6 @@ Accept wildcard characters: False
```
### -IncludeDomainLocalFrom
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IncludeDomainLocalFrom parameter specifies whether to return domain local groups from the FQDN of the specified Active Directory domain (for example, contoso.com) in the results.
@@ -149,6 +139,7 @@ Don't use this parameter with the Filter or Identity parameters.
Type: SmtpDomain
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -158,9 +149,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -172,6 +160,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: ExtendedOrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -181,15 +170,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -199,15 +186,13 @@ Accept wildcard characters: False
```
### -RoleGroupAssignable
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The RoleGroupAssignable switch filters security principals by returning only objects that can be assigned to an RBAC role group. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -217,9 +202,6 @@ Accept wildcard characters: False
```
### -Types
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Types parameter filters the results by object type. Valid values are:
- Computer
@@ -235,6 +217,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md b/exchange/exchange-ps/exchange/Get-SendConnector.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md
rename to exchange/exchange-ps/exchange/Get-SendConnector.md
index 05f88698a8..b285afa86f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md
+++ b/exchange/exchange-ps/exchange/Get-SendConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-sendconnector
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SendConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-sendconnector
-schema: 2.0.0
-title: Get-SendConnector
+ms.reviewer:
---
# Get-SendConnector
@@ -42,15 +41,13 @@ This example displays detailed information about the Send connector named Contos
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name, or GUID of the Send connector. If the Identity name contains spaces, enclose the name in quotation marks ("). You can omit the Identity parameter label. You can also include the server name by using the format ServerName\\ConnectorName.
```yaml
Type: SendConnectorIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -60,9 +57,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -71,6 +65,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md b/exchange/exchange-ps/exchange/Get-SenderFilterConfig.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md
rename to exchange/exchange-ps/exchange/Get-SenderFilterConfig.md
index 4cf064d7b1..b89a8e9412 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md
+++ b/exchange/exchange-ps/exchange/Get-SenderFilterConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-senderfilterconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SenderFilterConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-senderfilterconfig
-schema: 2.0.0
-title: Get-SenderFilterConfig
+ms.reviewer:
---
# Get-SenderFilterConfig
@@ -42,15 +41,13 @@ This example returns detailed information about the Sender Filter configuration
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -60,9 +57,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -71,6 +65,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md b/exchange/exchange-ps/exchange/Get-SenderIdConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md
rename to exchange/exchange-ps/exchange/Get-SenderIdConfig.md
index ec6ce1c598..1e0dad4cd1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md
+++ b/exchange/exchange-ps/exchange/Get-SenderIdConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-senderidconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SenderIdConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-senderidconfig
-schema: 2.0.0
-title: Get-SenderIdConfig
+ms.reviewer:
---
# Get-SenderIdConfig
@@ -41,9 +40,6 @@ This example returns detailed information about the Sender ID configuration on t
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -52,6 +48,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md b/exchange/exchange-ps/exchange/Get-SenderReputationConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md
rename to exchange/exchange-ps/exchange/Get-SenderReputationConfig.md
index 871add3003..83288be5e1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md
+++ b/exchange/exchange-ps/exchange/Get-SenderReputationConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-senderreputationconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SenderReputationConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-senderreputationconfig
-schema: 2.0.0
-title: Get-SenderReputationConfig
+ms.reviewer:
---
# Get-SenderReputationConfig
@@ -41,9 +40,6 @@ This example returns detailed information about the sender reputation configurat
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -52,6 +48,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md b/exchange/exchange-ps/exchange/Get-ServerComponentState.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md
rename to exchange/exchange-ps/exchange/Get-ServerComponentState.md
index 5a82a37409..2008d37985 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md
+++ b/exchange/exchange-ps/exchange/Get-ServerComponentState.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-servercomponentstate
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ServerComponentState
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-servercomponentstate
-schema: 2.0.0
-title: Get-ServerComponentState
+ms.reviewer:
---
# Get-ServerComponentState
@@ -50,9 +49,6 @@ This example returns detailed information for the component state of the Unified
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Exchange server where you want to view the configuration settings. You can use the following values:
- Name
@@ -63,6 +59,7 @@ The Identity parameter specifies the Exchange server where you want to view the
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -72,15 +69,13 @@ Accept wildcard characters: False
```
### -Component
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Component parameter specifies the component or endpoint for which you want to retrieve the state. To see the available values, run the following command: `Get-ServerComponentState `.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -90,9 +85,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -101,6 +93,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md b/exchange/exchange-ps/exchange/Get-ServerHealth.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md
rename to exchange/exchange-ps/exchange/Get-ServerHealth.md
index 3dd602e8a9..329cfe409b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md
+++ b/exchange/exchange-ps/exchange/Get-ServerHealth.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-serverhealth
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ServerHealth
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-serverhealth
-schema: 2.0.0
-title: Get-ServerHealth
+ms.reviewer:
---
# Get-ServerHealth
@@ -54,9 +53,6 @@ This example returns the server health for server Server01.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -68,6 +64,7 @@ The Identity parameter specifies the Exchange server where you want to run this
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -77,15 +74,13 @@ Accept wildcard characters: False
```
### -HaImpactingOnly
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The HaImpactingOnly switch specifies whether the cmdlet must roll up only the monitors that have HaImpacting set to True. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -HealthSet
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The HealthSet parameter returns the health state of a group of monitors. Monitors that are similar or are tied to a component's architecture are grouped to form a health set. You can determine the collection of monitors (and associated probes and responders) in a given health set by using the Get-MonitoringItemIdentity cmdlet.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md b/exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md
rename to exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md
index 641724b1b8..2986dafdb9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/exchange/Get-ServerMonitoringOverride.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-servermonitoringoverride
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ServerMonitoringOverride
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-servermonitoringoverride
-schema: 2.0.0
-title: Get-ServerMonitoringOverride
+ms.reviewer:
---
# Get-ServerMonitoringOverride
@@ -41,9 +40,6 @@ This example retrieves all monitoring overrides for the Exch01 server.
## PARAMETERS
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -57,6 +53,7 @@ You can't use this parameter to configure other Edge Transport servers remotely.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md b/exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md
rename to exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md
index 8b0404f1c8..842dc2fa11 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md
+++ b/exchange/exchange-ps/exchange/Get-ServiceDeliveryReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-servicedeliveryreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-ServiceDeliveryReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-servicedeliveryreport
-schema: 2.0.0
-title: Get-ServiceDeliveryReport
+ms.reviewer:
---
# Get-ServiceDeliveryReport
@@ -42,15 +41,13 @@ This example shows the delivery path information for the recipient chris@contoso
## PARAMETERS
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -60,15 +57,13 @@ Accept wildcard characters: False
```
### -Recipient
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Recipient parameter specifies the email address of the recipient you want to test.
```yaml
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md b/exchange/exchange-ps/exchange/Get-ServicePrincipal.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md
rename to exchange/exchange-ps/exchange/Get-ServicePrincipal.md
index 19cfbc1188..ee06d9d363 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md
+++ b/exchange/exchange-ps/exchange/Get-ServicePrincipal.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-serviceprincipal
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-ServicePrincipal
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-serviceprincipal
-schema: 2.0.0
-title: Get-ServicePrincipal
+ms.reviewer:
---
# Get-ServicePrincipal
@@ -53,9 +52,6 @@ This example returns detailed information about the service principal with the O
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter specifies the service principal that you want to view. You can use any value that uniquely identifies the service principal. For example:
- Name
@@ -68,6 +64,7 @@ The Identity parameter specifies the service principal that you want to view. Yo
Type: ServicePrincipalIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: 0
@@ -77,15 +74,13 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md b/exchange/exchange-ps/exchange/Get-SettingOverride.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md
rename to exchange/exchange-ps/exchange/Get-SettingOverride.md
index 2fb293f518..dec2d72019 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md
+++ b/exchange/exchange-ps/exchange/Get-SettingOverride.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-settingoverride
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SettingOverride
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-settingoverride
-schema: 2.0.0
-title: Get-SettingOverride
+ms.reviewer:
---
# Get-SettingOverride
@@ -53,9 +52,6 @@ This example displays a detailed information for the setting override object nam
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the setting override that you want to view. You can use any value that uniquely identifies the override. For example:
- Name
@@ -66,6 +62,7 @@ The Identity parameter specifies the setting override that you want to view. You
Type: SettingOverrideIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md b/exchange/exchange-ps/exchange/Get-SharingPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md
rename to exchange/exchange-ps/exchange/Get-SharingPolicy.md
index 928a905807..a9e5d5b87f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-SharingPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-sharingpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-SharingPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-sharingpolicy
-schema: 2.0.0
-title: Get-SharingPolicy
+ms.reviewer:
---
# Get-SharingPolicy
@@ -51,9 +50,6 @@ This example retrieves the full information for the sharing policy Fabrikam.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the sharing policy that you want to view. You can use one of the following values:
- ADObjectID
@@ -65,6 +61,7 @@ The Identity parameter specifies the sharing policy that you want to view. You c
Type: SharingPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -85,6 +79,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md b/exchange/exchange-ps/exchange/Get-SiteMailbox.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md
rename to exchange/exchange-ps/exchange/Get-SiteMailbox.md
index 1953f1a4b1..a35a4f6e0c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md
+++ b/exchange/exchange-ps/exchange/Get-SiteMailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-sitemailbox
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SiteMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-sitemailbox
-schema: 2.0.0
-title: Get-SiteMailbox
+ms.reviewer:
---
# Get-SiteMailbox
@@ -65,9 +64,6 @@ This example queries for site mailboxes that are marked for deletion and removes
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the site mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -81,6 +77,7 @@ The Identity parameter specifies the identity of the site mailbox. You can use a
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -90,9 +87,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -105,6 +99,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -114,9 +109,6 @@ Accept wildcard characters: False
```
### -BypassOwnerCheck
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BypassOwnerCheck parameter is used when the account that's running the command isn't a member or owner of the site mailbox. You don't need to specify a value with this switch.
If you don't use this switch, and you aren't a member or owner of the site mailbox, the command will fail.
@@ -125,6 +117,7 @@ If you don't use this switch, and you aren't a member or owner of the site mailb
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -134,9 +127,6 @@ Accept wildcard characters: False
```
### -DeletedSiteMailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DeletedSiteMailbox switch returns site mailboxes that have been marked for pending deletion. You don't need to specify a value with this switch.
When the lifecycle application in SharePoint closes a site mailbox, the site mailbox is retained for the period specified in the lifecycle policy in the closed state. The mailbox can then be reactivated by an end user or by a SharePoint administrator. After the retention period, the Exchange site mailbox that's housed in the mailbox database will have its name prepended with MDEL: to indicate that it has been marked for deletion. To free storage space and the alias, use the Remove-Mailbox cmdlet to manually remove these site mailboxes from the mailbox database.
@@ -145,6 +135,7 @@ When the lifecycle application in SharePoint closes a site mailbox, the site mai
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -154,15 +145,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -172,9 +161,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -185,6 +171,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -194,15 +181,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md b/exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md
rename to exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md
index e868fb6ee1..a79fefc2f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md
+++ b/exchange/exchange-ps/exchange/Get-SiteMailboxDiagnostics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-sitemailboxdiagnostics
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SiteMailboxDiagnostics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-sitemailboxdiagnostics
-schema: 2.0.0
-title: Get-SiteMailboxDiagnostics
+ms.reviewer:
---
# Get-SiteMailboxDiagnostics
@@ -56,9 +55,6 @@ This example returns the event information for the Marketing Events 2015 site ma
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the site mailbox that you want to view. You can use any value that uniquely identifies the site mailbox. For example:
- Name
@@ -72,6 +68,7 @@ The Identity parameter specifies the site mailbox that you want to view. You can
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -81,9 +78,6 @@ Accept wildcard characters: False
```
### -BypassOwnerCheck
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BypassOwnerCheck parameter is used when the account that's running the command isn't a member or owner of the site mailbox. You don't need to specify a value with this switch.
If you don't use this switch and you aren't a member or owner of the site mailbox, the command will fail.
@@ -92,6 +86,7 @@ If you don't use this switch and you aren't a member or owner of the site mailbo
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -101,9 +96,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -113,6 +105,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -122,15 +115,13 @@ Accept wildcard characters: False
```
### -SendMeEmail
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SendMeEmail switch specifies that the diagnostic information is sent to the primary SMTP email address of the user account that's running the command. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -140,15 +131,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md
rename to exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md
index 91b294c205..1e107e4c93 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-SiteMailboxProvisioningPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-sitemailboxprovisioningpolicy
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SiteMailboxProvisioningPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-sitemailboxprovisioningpolicy
-schema: 2.0.0
-title: Get-SiteMailboxProvisioningPolicy
+ms.reviewer:
---
# Get-SiteMailboxProvisioningPolicy
@@ -53,9 +52,6 @@ This example returns detailed information about the site mailbox provisioning po
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the site mailbox provisioning policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -66,6 +62,7 @@ The Identity parameter specifies the site mailbox provisioning policy that you w
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md b/exchange/exchange-ps/exchange/Get-SmimeConfig.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md
rename to exchange/exchange-ps/exchange/Get-SmimeConfig.md
index cdd857bd7f..94acefe7bf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md
+++ b/exchange/exchange-ps/exchange/Get-SmimeConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-smimeconfig
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-SmimeConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-smimeconfig
-schema: 2.0.0
-title: Get-SmimeConfig
+ms.reviewer:
---
# Get-SmimeConfig
@@ -41,15 +40,13 @@ This example shows the S/MIME configuration that's used with Outlook on the web.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md b/exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md
rename to exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md
index 7c93c5cd2b..2bc72a8f55 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md
+++ b/exchange/exchange-ps/exchange/Get-SmtpDaneInboundStatus.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-smtpdaneinboundstatus
applicable: Exchange Online
+title: Get-SmtpDaneInboundStatus
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-smtpdaneinboundstatus
-schema: 2.0.0
-title: Get-SmtpDaneInboundStatus
+ms.reviewer:
---
# Get-SmtpDaneInboundStatus
@@ -42,15 +41,13 @@ This example checks the DANE status for the accepted domain contoso.com.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Online
-
The DomainName parameter specifies the accepted domain in the Exchange Online organization where you want to view information about DANE (for example, contoso.com).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md b/exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md
rename to exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md
index 351bcb4516..01335195b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md
+++ b/exchange/exchange-ps/exchange/Get-SpoofIntelligenceInsight.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-spoofintelligenceinsight
applicable: Exchange Online, Exchange Online Protection
+title: Get-SpoofIntelligenceInsight
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-spoofintelligenceinsight
-schema: 2.0.0
-title: Get-SpoofIntelligenceInsight
+ms.reviewer:
---
# Get-SpoofIntelligenceInsight
@@ -58,15 +57,13 @@ This example exports the same list of spoofed senders to a CSV file.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter is available but isn't used.
```yaml
Type: HostedConnectionFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 0
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md b/exchange/exchange-ps/exchange/Get-SpoofMailReport.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md
rename to exchange/exchange-ps/exchange/Get-SpoofMailReport.md
index 30898b8ba5..312ec706dc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md
+++ b/exchange/exchange-ps/exchange/Get-SpoofMailReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-spoofmailreport
applicable: Exchange Online, Exchange Online Protection
+title: Get-SpoofMailReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-spoofmailreport
-schema: 2.0.0
-title: Get-SpoofMailReport
+ms.reviewer:
---
# Get-SpoofMailReport
@@ -66,9 +65,6 @@ This example shows the insider spoofing detections in your organization during t
## PARAMETERS
### -Action
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Action parameter filters the report by the action taken on messages. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget Actions`. The action you specify must correspond to the report type. For example, you can only specify malware filter actions for malware reports.
You can specify multiple values separated by commas.
@@ -79,6 +75,7 @@ Common values for this report are GoodMail and CaughtAsSpam.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -88,15 +85,13 @@ Accept wildcard characters: False
```
### -Direction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Direction parameter filters the results by incoming messages. The valid value for this parameter is Inbound.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -106,9 +101,6 @@ Accept wildcard characters: False
```
### -EndDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -117,6 +109,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -126,15 +119,13 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EventType parameter filters the report by the event type. The only valid value for this parameter is SpoofMail.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -144,15 +135,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -162,15 +151,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -180,15 +167,13 @@ Accept wildcard characters: False
```
### -ProbeTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -198,9 +183,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -209,6 +191,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md b/exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md
rename to exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md
index ecf022b35a..4a09b7af84 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md
+++ b/exchange/exchange-ps/exchange/Get-StoreUsageStatistics.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-storeusagestatistics
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-StoreUsageStatistics
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-storeusagestatistics
-schema: 2.0.0
-title: Get-StoreUsageStatistics
+ms.reviewer:
---
# Get-StoreUsageStatistics
@@ -79,9 +78,6 @@ This example retrieves store usage statistics for database DB1 and sorts the out
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox to get usage statistics from. You can use one of the following values to identify the mailbox:
- GUID
@@ -100,6 +96,7 @@ You can't use this parameter with the Database or Server parameters.
Type: GeneralMailboxIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -109,9 +106,6 @@ Accept wildcard characters: False
```
### -Database
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Database parameter specifies the name of the mailbox database to get usage statistics from (the top 25 largest mailboxes on the specified mailbox database). You can use any value that uniquely identifies the mailbox database. For example:
- Name
@@ -124,6 +118,7 @@ You can't use this parameter with the Identity or Server parameters.
Type: DatabaseIdParameter
Parameter Sets: Database
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -133,9 +128,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Mailbox server to get usage statistics from (the top 25 mailboxes on all active databases on the specified server). You can use one of the following values to identify the server:
- Fully qualified domain name (FQDN)
@@ -147,6 +139,7 @@ You can't use this parameter with the Database or Identity parameters.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -156,9 +149,6 @@ Accept wildcard characters: False
```
### -CopyOnServer
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The CopyOnServer parameter specifies the mailbox database copy to get usage statistics from. You can use any value that uniquely identifies the mailbox database. For example:
- Name
@@ -171,6 +161,7 @@ You use this parameter with the Server or Identity parameters.
Type: ServerIdParameter
Parameter Sets: Database, Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -180,15 +171,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -198,9 +187,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -216,6 +202,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -225,9 +212,6 @@ Accept wildcard characters: False
```
### -IncludePassive
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludePassive switch specifies whether to include usage statistics from active and passive copies of mailbox databases on the Mailbox server you specified with the Server parameter. You don't need to specify a value with this switch.
If you don't use this switch, only statistics from active copies of mailbox databases are included in the results.
@@ -236,6 +220,7 @@ If you don't use this switch, only statistics from active copies of mailbox data
Type: SwitchParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md
rename to exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md
index 71f674f883..420045a251 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md
+++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewActivity.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewactivity
applicable: Exchange Online, Security & Compliance
+title: Get-SupervisoryReviewActivity
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-supervisoryreviewactivity
-schema: 2.0.0
-title: Get-SupervisoryReviewActivity
+ms.reviewer:
---
# Get-SupervisoryReviewActivity
@@ -48,9 +47,6 @@ This example exports all the supervisory review activities for a policy to a .cs
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -59,6 +55,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: True
Position: Named
@@ -68,15 +65,13 @@ Accept wildcard characters: False
```
### -PolicyId
-
-> Applicable: Exchange Online, Security & Compliance
-
{{ Fill PolicyId Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: True
Position: Named
@@ -86,9 +81,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -97,6 +89,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewOverallProgressReport.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewOverallProgressReport.md
rename to exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md
index dbc52974fd..3a432c1505 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewOverallProgressReport.md
+++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewOverallProgressReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewoverallprogressreport
applicable: Security & Compliance
+title: Get-SupervisoryReviewOverallProgressReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-supervisoryreviewoverallprogressreport
-schema: 2.0.0
-title: Get-SupervisoryReviewOverallProgressReport
+ms.reviewer:
---
# Get-SupervisoryReviewOverallProgressReport
@@ -44,9 +43,6 @@ This example returns a list of the total number of supervised communications cla
## PARAMETERS
### -EndDate
-
-> Applicable: Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -55,6 +51,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -64,15 +61,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Security & Compliance
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -82,15 +77,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -100,9 +93,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -111,6 +101,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyReport.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyReport.md
rename to exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md
index 34eb1e064a..d3982ce31b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyReport.md
+++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewpolicyreport
applicable: Exchange Online, Security & Compliance
+title: Get-SupervisoryReviewPolicyReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-supervisoryreviewpolicyreport
-schema: 2.0.0
-title: Get-SupervisoryReviewPolicyReport
+ms.reviewer:
---
# Get-SupervisoryReviewPolicyReport
@@ -61,9 +60,6 @@ This example returns the supervisory review policy events for the policy named E
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -72,6 +68,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -81,15 +78,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -99,15 +94,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -117,9 +110,6 @@ Accept wildcard characters: False
```
### -Policies
-
-> Applicable: Exchange Online, Security & Compliance
-
The Policies parameter filters the results by the supervisory review policy.
You can specify multiple values separated by commas.
@@ -128,6 +118,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -137,9 +128,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -148,6 +136,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyV2.md
rename to exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md
index a6b4994a08..cc356b57a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewPolicyV2.md
+++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewPolicyV2.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewpolicyv2
applicable: Exchange Online, Security & Compliance
+title: Get-SupervisoryReviewPolicyV2
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-supervisoryreviewpolicyv2
-schema: 2.0.0
-title: Get-SupervisoryReviewPolicyV2
+ms.reviewer:
---
# Get-SupervisoryReviewPolicyV2
@@ -48,9 +47,6 @@ This example returns detailed information for the supervisory review policy name
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the supervisory review policy that you want to view. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -61,6 +57,7 @@ The Identity parameter specifies the supervisory review policy that you want to
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewReport.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewReport.md
rename to exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md
index c5358a7103..5e1a033aa5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewReport.md
+++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewreport
applicable: Exchange Online, Security & Compliance
+title: Get-SupervisoryReviewReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-supervisoryreviewreport
-schema: 2.0.0
-title: Get-SupervisoryReviewReport
+ms.reviewer:
---
# Get-SupervisoryReviewReport
@@ -53,9 +52,6 @@ This example returns the supervisory review events for the policy named US Broke
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -64,6 +60,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Exchange Online, Security & Compliance
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -91,15 +86,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Exchange Online, Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -109,9 +102,6 @@ Accept wildcard characters: False
```
### -Policies
-
-> Applicable: Exchange Online, Security & Compliance
-
The Policies parameter filters the results by the supervisory review policy.
You can specify multiple values separated by commas.
@@ -120,6 +110,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -129,9 +120,6 @@ Accept wildcard characters: False
```
### -Reviewers
-
-> Applicable: Exchange Online, Security & Compliance
-
The Reviewers parameter filters the results by the reviewers of the supervisory review policy.
You can specify multiple values separated by commas.
@@ -140,6 +128,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -149,9 +138,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Online, Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -160,6 +146,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewRule.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewRule.md
rename to exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md
index 135c9a1e38..1a7f812f23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewRule.md
+++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewrule
applicable: Exchange Online, Security & Compliance
+title: Get-SupervisoryReviewRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-supervisoryreviewrule
-schema: 2.0.0
-title: Get-SupervisoryReviewRule
+ms.reviewer:
---
# Get-SupervisoryReviewRule
@@ -57,9 +56,6 @@ This example returns the rule that assigned to the supervisory review policy nam
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance
-
The Identity parameter specifies the supervisory review rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -70,6 +66,7 @@ The Identity parameter specifies the supervisory review rule that you want to vi
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -IncludeRuleXml
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeRuleXml Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -97,9 +92,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Exchange Online, Security & Compliance
-
The Policy parameter filters the results by supervisory review policy that's assigned to the rule. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -110,6 +102,7 @@ The Policy parameter filters the results by supervisory review policy that's ass
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewTopCasesReport.md b/exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewTopCasesReport.md
rename to exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md
index b6ff38b992..f630b5e84b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewTopCasesReport.md
+++ b/exchange/exchange-ps/exchange/Get-SupervisoryReviewTopCasesReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-supervisoryreviewtopcasesreport
applicable: Security & Compliance
+title: Get-SupervisoryReviewTopCasesReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-supervisoryreviewtopcasesreport
-schema: 2.0.0
-title: Get-SupervisoryReviewTopCasesReport
+ms.reviewer:
---
# Get-SupervisoryReviewTopCasesReport
@@ -43,9 +42,6 @@ This example returns detailed information on supervisory policies, including the
## PARAMETERS
### -EndDate
-
-> Applicable: Security & Compliance
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -54,6 +50,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -63,15 +60,13 @@ Accept wildcard characters: False
```
### -Page
-
-> Applicable: Security & Compliance
-
The Page parameter specifies the page number of the results you want to view. Valid input for this parameter is an integer between 1 and 1000. The default value is 1.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -81,15 +76,13 @@ Accept wildcard characters: False
```
### -PageSize
-
-> Applicable: Security & Compliance
-
The PageSize parameter specifies the maximum number of entries per page. Valid input for this parameter is an integer between 1 and 5000. The default value is 1000.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -99,9 +92,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Security & Compliance
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -110,6 +100,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md b/exchange/exchange-ps/exchange/Get-SweepRule.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md
rename to exchange/exchange-ps/exchange/Get-SweepRule.md
index 4a56442e92..ceab5bc86d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md
+++ b/exchange/exchange-ps/exchange/Get-SweepRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-sweeprule
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-SweepRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-sweeprule
-schema: 2.0.0
-title: Get-SweepRule
+ms.reviewer:
---
# Get-SweepRule
@@ -60,9 +59,6 @@ This example returns detailed information for the Sweep rule with the specified
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the Sweep rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- RuleId property (for example, x2hlsdpGmUifjFgxxGIOJw==).
@@ -73,6 +69,7 @@ The Identity parameter specifies the Sweep rule that you want to view. You can u
Type: SweepRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -82,15 +79,13 @@ Accept wildcard characters: False
```
### -BypassScopeCheck
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The BypassScopeCheck switch specifies whether to bypass the scope check for the user that's running the command. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -100,9 +95,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -111,6 +103,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -120,9 +113,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter filters the results by the specified mailbox. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -140,6 +130,7 @@ The Mailbox parameter filters the results by the specified mailbox. You can use
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -149,15 +140,13 @@ Accept wildcard characters: False
```
### -Provider
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Provider parameter filters the results by the specified provider.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -167,9 +156,6 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
@@ -178,6 +164,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -187,9 +174,6 @@ Accept wildcard characters: False
```
### -SkipCount
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill SkipCount Description }}
@@ -198,6 +182,7 @@ This parameter is available only in the cloud-based service.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md b/exchange/exchange-ps/exchange/Get-SystemMessage.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md
rename to exchange/exchange-ps/exchange/Get-SystemMessage.md
index 86e3e2f970..ba18ccc28c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md
+++ b/exchange/exchange-ps/exchange/Get-SystemMessage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-systemmessage
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-SystemMessage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-systemmessage
-schema: 2.0.0
-title: Get-SystemMessage
+ms.reviewer:
---
# Get-SystemMessage
@@ -75,9 +74,6 @@ You should output the list to a file, because the list is very long, and you'll
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the custom system message that you want to view. You can use any value that uniquely identifies the system message. For example:
- Identity
@@ -135,6 +131,7 @@ Maximum number of levels (depth) in a mailbox folder:
Type: SystemMessageIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -144,9 +141,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -155,6 +149,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -164,9 +159,6 @@ Accept wildcard characters: False
```
### -Original
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Original switch filters the results by the default system messages that are included with Exchange. You don't need to specify a value with this switch.
You can't use this switch with the Identity parameter.
@@ -175,6 +167,7 @@ You can't use this switch with the Identity parameter.
Type: SwitchParameter
Parameter Sets: Original
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md b/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md
rename to exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md
index b7738fa384..4f520c8a57 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-teamsprotectionpolicy
applicable: Exchange Online
+title: Get-TeamsProtectionPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-teamsprotectionpolicy
-schema: 2.0.0
-title: Get-TeamsProtectionPolicy
+ms.reviewer:
---
# Get-TeamsProtectionPolicy
@@ -41,15 +40,13 @@ This example shows detailed information about the Teams protection policy in the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the Teams protection policy that you want to view. There's only one Teams protection policy in an organization named Teams Protection Policy.
```yaml
Type: TeamsProtectionPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md
index ce99649cfb..5aba335ec7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/Get-TeamsProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-teamsprotectionpolicyrule
applicable: Exchange Online
+title: Get-TeamsProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-teamsprotectionpolicyrule
-schema: 2.0.0
-title: Get-TeamsProtectionPolicyRule
+ms.reviewer:
---
# Get-TeamsProtectionPolicyRule
@@ -42,15 +41,13 @@ This example shows detailed information about the Teams protection policy in the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the Teams protection policy rule that you want to view. There's only one Teams protection policy rule in an organization named Teams Protection Policy Rule.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: 1
@@ -60,9 +57,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Online
-
The State parameter filters the results by the State value of the rule. Valid values are:
- Enabled
@@ -72,6 +66,7 @@ The State parameter filters the results by the State value of the rule. Valid va
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md b/exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md
rename to exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md
index 2281e8eb73..e011044ffb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md
+++ b/exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-tenantallowblocklistitems
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-TenantAllowBlockListItems
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-tenantallowblocklistitems
-schema: 2.0.0
-title: Get-TenantAllowBlockListItems
+ms.reviewer:
---
# Get-TenantAllowBlockListItems
@@ -72,9 +71,6 @@ This example returns information for all allowed non-Microsoft phishing simulati
## PARAMETERS
### -ListType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The ListType parameter specifies the list to view. Valid values are:
- FileHash
@@ -86,6 +82,7 @@ The ListType parameter specifies the list to view. Valid values are:
Type: ListType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -95,9 +92,6 @@ Accept wildcard characters: False
```
### -Entry
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Entry parameter filters the results based on the ListType parameter value. Valid values are:
- FileHash: The exact SHA256 file hash value.
@@ -111,6 +105,7 @@ This value is shown in the Value property of the entry in the output of the Get-
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -120,15 +115,13 @@ Accept wildcard characters: False
```
### -NoExpiration
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The NoExpiration switch filters the results by entries that are set to never expire. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: NoExpiration
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
@@ -138,15 +131,13 @@ Accept wildcard characters: False
```
### -Allow
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Allow switch filters the results for allow entries. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -156,15 +147,13 @@ Accept wildcard characters: False
```
### -Block
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Block switch filters the results for block entries. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -174,9 +163,6 @@ Accept wildcard characters: False
```
### -ExpirationDate
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The ExpirationDate parameter filters the results by expiration date in Coordinated Universal Time (UTC).
To specify a date/time value for this parameter, use either of the following options:
@@ -188,6 +174,7 @@ To specify a date/time value for this parameter, use either of the following opt
Type: DateTime
Parameter Sets: Expiration
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -197,9 +184,6 @@ Accept wildcard characters: False
```
### -ListSubType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The ListSubType parameter filters the results by subtype. Valid values are:
- AdvancedDelivery
@@ -209,6 +193,7 @@ The ListSubType parameter filters the results by subtype. Valid values are:
Type: ListSubType[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -218,9 +203,6 @@ Accept wildcard characters: False
```
### -OutputJson
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The OutputJson switch specifies whether to return all entries in a single JSON value. You don't need to specify a value with this switch.
You use this switch to prevent the command from halting on the first entry that contains a syntax error.
@@ -229,6 +211,7 @@ You use this switch to prevent the command from halting on the first entry that
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md
rename to exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md
index 4a6937ad9f..a77fd3036a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md
+++ b/exchange/exchange-ps/exchange/Get-TenantAllowBlockListSpoofItems.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-tenantallowblocklistspoofitems
applicable: Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-TenantAllowBlockListSpoofItems
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-tenantallowblocklistspoofitems
-schema: 2.0.0
-title: Get-TenantAllowBlockListSpoofItems
+ms.reviewer:
---
# Get-TenantAllowBlockListSpoofItems
@@ -72,15 +71,13 @@ This example exports the same list of spoofed pairs to a CSV file.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter is available but isn't used.
```yaml
Type: HostedConnectionFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: 0
@@ -90,9 +87,6 @@ Accept wildcard characters: False
```
### -Action
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The Action parameter filters the results by action type. Valid values are:
- Allow
@@ -102,6 +96,7 @@ The Action parameter filters the results by action type. Valid values are:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -111,9 +106,6 @@ Accept wildcard characters: False
```
### -SpoofType
-
-> Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
-
The SpoofType parameter filters the results by spoof type. Valid values are:
- External
@@ -123,6 +115,7 @@ The SpoofType parameter filters the results by spoof type. Valid values are:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md b/exchange/exchange-ps/exchange/Get-TextMessagingAccount.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md
rename to exchange/exchange-ps/exchange/Get-TextMessagingAccount.md
index 6d7d0bf508..11e102c7e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md
+++ b/exchange/exchange-ps/exchange/Get-TextMessagingAccount.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-textmessagingaccount
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-TextMessagingAccount
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-textmessagingaccount
-schema: 2.0.0
-title: Get-TextMessagingAccount
+ms.reviewer:
---
# Get-TextMessagingAccount
@@ -56,9 +55,6 @@ This example finds all user mailboxes where text messaging notifications are ena
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -76,6 +72,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -85,9 +82,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -96,6 +90,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -105,9 +100,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -116,6 +108,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -125,9 +118,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -138,6 +128,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -147,15 +138,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md b/exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md
rename to exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md
index f3cb66dd00..5299f4079b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-ThrottlingPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-throttlingpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ThrottlingPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-throttlingpolicy
-schema: 2.0.0
-title: Get-ThrottlingPolicy
+ms.reviewer:
---
# Get-ThrottlingPolicy
@@ -56,15 +55,13 @@ This example displays the parameters and values for throttling policy Throttling
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter identifies the name of the throttling policy that you want to return settings for.
```yaml
Type: ThrottlingPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -85,6 +79,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -94,15 +89,13 @@ Accept wildcard characters: False
```
### -Diagnostics
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Diagnostics switch specifies whether you want the output to include the diagnostics string. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -112,15 +105,13 @@ Accept wildcard characters: False
```
### -Explicit
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Explicit switch specifies whether to return only the policy settings that have been directly assigned using this policy. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,9 +121,6 @@ Accept wildcard characters: False
```
### -ThrottlingPolicyScope
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ThrottlingPolicyScope parameter specifies the scope of the throttling policy. You can use the following values:
- Global
@@ -145,6 +133,7 @@ For information about each of these policy scopes, see [User workload management
Type: ThrottlingPolicyScopeType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md
rename to exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md
index 77d4935205..6850db5cc9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md
+++ b/exchange/exchange-ps/exchange/Get-ThrottlingPolicyAssociation.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-throttlingpolicyassociation
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-ThrottlingPolicyAssociation
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-throttlingpolicyassociation
-schema: 2.0.0
-title: Get-ThrottlingPolicyAssociation
+ms.reviewer:
---
# Get-ThrottlingPolicyAssociation
@@ -72,9 +71,6 @@ This example returns detailed information for the throttling policy association
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the throttling policy association that you want to view. You can use any value that uniquely identifies the throttling policy association. For example:
- Name
@@ -95,6 +91,7 @@ The Identity parameter specifies the throttling policy association that you want
Type: ThrottlingPolicyAssociationIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -104,9 +101,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -119,6 +113,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -128,9 +123,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -139,6 +131,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -148,15 +141,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -166,15 +157,13 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -184,9 +173,6 @@ Accept wildcard characters: False
```
### -ThrottlingPolicy
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ThrottlingPolicy parameter filters the results by throttling policy. You can use any value that uniquely identifies the throttling policy. For example:
- Name
@@ -197,6 +183,7 @@ The ThrottlingPolicy parameter filters the results by throttling policy. You can
Type: ThrottlingPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md b/exchange/exchange-ps/exchange/Get-TransportAgent.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md
rename to exchange/exchange-ps/exchange/Get-TransportAgent.md
index 82e2fe42d4..8efaaf32bc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md
+++ b/exchange/exchange-ps/exchange/Get-TransportAgent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-transportagent
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-TransportAgent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-transportagent
-schema: 2.0.0
-title: Get-TransportAgent
+ms.reviewer:
---
# Get-TransportAgent
@@ -50,15 +49,13 @@ This example displays detailed information about the Transport Rule agent that's
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the display name of the transport agent to be displayed. The length of the name can't exceed 64 characters.
```yaml
Type: TransportAgentObjectId
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -79,6 +73,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -88,9 +83,6 @@ Accept wildcard characters: False
```
### -TransportService
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
- Hub for the Transport service on Mailbox servers.
@@ -103,6 +95,7 @@ The TransportService parameter specifies the transport service that you want to
Type: TransportService
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md b/exchange/exchange-ps/exchange/Get-TransportConfig.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md
rename to exchange/exchange-ps/exchange/Get-TransportConfig.md
index 02598b341e..3357a4be56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md
+++ b/exchange/exchange-ps/exchange/Get-TransportConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-transportconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Get-TransportConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-transportconfig
-schema: 2.0.0
-title: Get-TransportConfig
+ms.reviewer:
---
# Get-TransportConfig
@@ -51,9 +50,6 @@ This example lists all delivery status notification-related (DSN) configuration
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -62,6 +58,7 @@ This parameter is reserved for internal Microsoft use.
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -84,6 +78,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md b/exchange/exchange-ps/exchange/Get-TransportPipeline.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md
rename to exchange/exchange-ps/exchange/Get-TransportPipeline.md
index f475a86fd2..8366b7fc1a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md
+++ b/exchange/exchange-ps/exchange/Get-TransportPipeline.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-transportpipeline
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-TransportPipeline
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-transportpipeline
-schema: 2.0.0
-title: Get-TransportPipeline
+ms.reviewer:
---
# Get-TransportPipeline
@@ -56,9 +55,6 @@ This example returns a list of agents registered in the transport pipeline, with
## PARAMETERS
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -67,6 +63,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md b/exchange/exchange-ps/exchange/Get-TransportRule.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md
rename to exchange/exchange-ps/exchange/Get-TransportRule.md
index f0b41ab022..d55f8756f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md
+++ b/exchange/exchange-ps/exchange/Get-TransportRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-transportrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-TransportRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-transportrule
-schema: 2.0.0
-title: Get-TransportRule
+ms.reviewer:
---
# Get-TransportRule
@@ -72,9 +71,6 @@ In on-premises Exchange, this example returns a summary list of all rules that e
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -85,6 +81,7 @@ The Identity parameter specifies the rule that you want to view. You can use any
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -94,9 +91,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -107,6 +101,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -116,9 +111,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The State parameter specifies filters the results by enabled or disabled rules. Valid values are:
- Enabled: Only enabled rules are returned in the results.
@@ -130,6 +122,7 @@ If you don't use this parameter, the command returns all rules, both enabled and
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -139,9 +132,6 @@ Accept wildcard characters: False
```
### -DlpPolicy
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
**Note**: This parameter is functional only in on-premises Exchange.
The DlpPolicy parameter filters the results by the name of the specified data loss prevention (DLP) policy. If the value contains spaces, enclose the value in quotation marks (").
@@ -152,6 +142,7 @@ DLP policies in your organization allow you to prevent unintentional disclosure
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -161,9 +152,6 @@ Accept wildcard characters: False
```
### -ExcludeConditionActionDetails
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The ExcludeConditionActionDetails parameter specifies whether to hide specific details from the results. Valid values are:
@@ -175,6 +163,7 @@ The ExcludeConditionActionDetails parameter specifies whether to hide specific d
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -184,9 +173,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Filter parameter filters the results by using an OPATH. This parameter searches the Description property, which includes the conditions, exceptions, actions and the associated values of a transport rule.
This parameter uses the syntax `"Description -like 'Text*'"`. For example, `"Description -like '192.168.1.1*'"`.
@@ -197,6 +183,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -206,15 +193,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md b/exchange/exchange-ps/exchange/Get-TransportRuleAction.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md
rename to exchange/exchange-ps/exchange/Get-TransportRuleAction.md
index 356cfd7f34..a7052dc127 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md
+++ b/exchange/exchange-ps/exchange/Get-TransportRuleAction.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-transportruleaction
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-TransportRuleAction
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-transportruleaction
-schema: 2.0.0
-title: Get-TransportRuleAction
+ms.reviewer:
---
# Get-TransportRuleAction
@@ -52,15 +51,13 @@ For more information about pipelining, see [About Pipelines](https://learn.micro
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Name parameter specifies the name of the action that you want to view. To see the list of available names, run the command Get-TransportRuleAction.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md b/exchange/exchange-ps/exchange/Get-TransportRulePredicate.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md
rename to exchange/exchange-ps/exchange/Get-TransportRulePredicate.md
index 002d434fe7..1781b502e3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md
+++ b/exchange/exchange-ps/exchange/Get-TransportRulePredicate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-transportrulepredicate
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Get-TransportRulePredicate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-transportrulepredicate
-schema: 2.0.0
-title: Get-TransportRulePredicate
+ms.reviewer:
---
# Get-TransportRulePredicate
@@ -63,15 +62,13 @@ For more information about how to work with the output of a command, see [Workin
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Name parameter specifies the name of the predicate that you want to view. To see the list of available names, run the command Get-TransportRulePredicate.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md b/exchange/exchange-ps/exchange/Get-TransportServer.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md
rename to exchange/exchange-ps/exchange/Get-TransportServer.md
index be4676662a..9e6bfd34f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md
+++ b/exchange/exchange-ps/exchange/Get-TransportServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-transportserver
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-TransportServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-transportserver
-schema: 2.0.0
-title: Get-TransportServer
+ms.reviewer:
---
# Get-TransportServer
@@ -51,9 +50,6 @@ This example retrieves the detailed transport configuration information for the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Transport server that you want to view. You can use any value that uniquely identifies the server. For example:
- Name
@@ -65,6 +61,7 @@ The Identity parameter specifies the Transport server that you want to view. You
Type: TransportServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -85,6 +79,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md b/exchange/exchange-ps/exchange/Get-TransportService.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md
rename to exchange/exchange-ps/exchange/Get-TransportService.md
index a7da169a33..de2c585879 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md
+++ b/exchange/exchange-ps/exchange/Get-TransportService.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-transportservice
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-TransportService
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-transportservice
-schema: 2.0.0
-title: Get-TransportService
+ms.reviewer:
---
# Get-TransportService
@@ -49,9 +48,6 @@ This example retrieves the detailed transport configuration information for the
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the Mailbox server that hosts the Transport service configuration you want to view. You can use any value that uniquely identifies the server. For example:
- Name
@@ -65,6 +61,7 @@ You can't use this parameter on an Edge Transport server.
Type: TransportServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -85,6 +79,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md b/exchange/exchange-ps/exchange/Get-Trust.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-Trust.md
rename to exchange/exchange-ps/exchange/Get-Trust.md
index 035a77f9d4..06c4e8a053 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md
+++ b/exchange/exchange-ps/exchange/Get-Trust.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-trust
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-Trust
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-trust
-schema: 2.0.0
-title: Get-Trust
+ms.reviewer:
---
# Get-Trust
@@ -43,15 +42,13 @@ This example enumerates all trusts for the domain Contoso.com.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainName parameter specifies that trusts returned are restricted to the domain name specified.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md b/exchange/exchange-ps/exchange/Get-UMActiveCalls.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md
rename to exchange/exchange-ps/exchange/Get-UMActiveCalls.md
index 291c7a984f..ad6d739107 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md
+++ b/exchange/exchange-ps/exchange/Get-UMActiveCalls.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umactivecalls
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMActiveCalls
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umactivecalls
-schema: 2.0.0
-title: Get-UMActiveCalls
+ms.reviewer:
---
# Get-UMActiveCalls
@@ -91,9 +90,6 @@ This example displays a list of active calls associated with the UM dial plan My
## PARAMETERS
### -DialPlan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DialPlan parameter specifies the UM dial plan for which you want to retrieve active calls.
You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in the same command.
@@ -102,6 +98,7 @@ You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in t
Type: UMDialPlanIdParameter
Parameter Sets: DialPlan
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -111,9 +108,6 @@ Accept wildcard characters: False
```
### -InstanceServer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The InstanceServer parameter specifies the Mailbox server running the Microsoft Exchange Unified Messaging service for which you want to retrieve active calls.
You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in the same command.
@@ -122,6 +116,7 @@ You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in t
Type: UMServer
Parameter Sets: ServerInstance
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -131,9 +126,6 @@ Accept wildcard characters: False
```
### -IPGateway
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The IPGateway parameter specifies the UM IP gateway for which you want to retrieve active calls.
You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in the same command.
@@ -142,6 +134,7 @@ You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in t
Type: UMIPGatewayIdParameter
Parameter Sets: UMIPGateway
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -151,15 +144,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -169,9 +160,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Server parameter filters the results by the specified Unified Messaging server. You can use any value that uniquely identifies the server. For example:
- Name
@@ -185,6 +173,7 @@ You can't use the DialPlan, InstanceServer, IPGateway, or Server parameters in t
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md b/exchange/exchange-ps/exchange/Get-UMAutoAttendant.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md
rename to exchange/exchange-ps/exchange/Get-UMAutoAttendant.md
index f8dd5e3588..4ae3dced8b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md
+++ b/exchange/exchange-ps/exchange/Get-UMAutoAttendant.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umautoattendant
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMAutoAttendant
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umautoattendant
-schema: 2.0.0
-title: Get-UMAutoAttendant
+ms.reviewer:
---
# Get-UMAutoAttendant
@@ -61,15 +60,13 @@ This examples displays all the UM auto attendants associated with the UM dial pl
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for the UM auto attendant that's being viewed. This is the directory object ID for the UM auto attendant.
```yaml
Type: UMAutoAttendantIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -UMDialPlan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMDialPlan parameter specifies whether to display all the UM auto attendants that are associated with the UM dial plan that's specified.
```yaml
Type: UMDialPlanIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md b/exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md
rename to exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md
index 0c79f7fbfd..e469e77136 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/exchange/Get-UMCallAnsweringRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umcallansweringrule
applicable: Exchange Server 2013, Exchange Server 2016
+title: Get-UMCallAnsweringRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umcallansweringrule
-schema: 2.0.0
-title: Get-UMCallAnsweringRule
+ms.reviewer:
---
# Get-UMCallAnsweringRule
@@ -54,15 +53,13 @@ This example displays the properties of the call answering rule MyUMCallAnswerin
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for a call answering rule being viewed.
```yaml
Type: UMCallAnsweringRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -72,15 +69,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -90,9 +85,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Mailbox parameter specifies the UM-enabled mailbox that contains the UM call answering rule. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -112,6 +104,7 @@ If you don't use this parameter, the mailbox of the user who is running the comm
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md b/exchange/exchange-ps/exchange/Get-UMCallDataRecord.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md
rename to exchange/exchange-ps/exchange/Get-UMCallDataRecord.md
index ff1aaeaeeb..868677c8f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md
+++ b/exchange/exchange-ps/exchange/Get-UMCallDataRecord.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umcalldatarecord
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMCallDataRecord
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umcalldatarecord
-schema: 2.0.0
-title: Get-UMCallDataRecord
+ms.reviewer:
---
# Get-UMCallDataRecord
@@ -59,9 +58,6 @@ This example displays the UM call data records for the UM-enabled user Tony.
## PARAMETERS
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Mailbox parameter specifies the UM-enabled mailbox that UM call data records are displayed for. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -79,6 +75,7 @@ The Mailbox parameter specifies the UM-enabled mailbox that UM call data records
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -88,15 +85,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md b/exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md
rename to exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md
index 45deb8cca3..44123198a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md
+++ b/exchange/exchange-ps/exchange/Get-UMCallRouterSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umcallroutersettings
applicable: Exchange Server 2013, Exchange Server 2016
+title: Get-UMCallRouterSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umcallroutersettings
-schema: 2.0.0
-title: Get-UMCallRouterSettings
+ms.reviewer:
---
# Get-UMCallRouterSettings
@@ -51,9 +50,6 @@ This example displays detailed information for the Microsoft Exchange Unified Me
## PARAMETERS
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -67,6 +63,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -76,15 +73,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md b/exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md
rename to exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md
index c37b790bbe..87b5ea88f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md
+++ b/exchange/exchange-ps/exchange/Get-UMCallSummaryReport.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umcallsummaryreport
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMCallSummaryReport
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umcallsummaryreport
-schema: 2.0.0
-title: Get-UMCallSummaryReport
+ms.reviewer:
---
# Get-UMCallSummaryReport
@@ -87,9 +86,6 @@ This example displays the statistics for calls received or placed by Mailbox ser
## PARAMETERS
### -GroupBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The GroupBy parameter specifies how to return the results. Valid values are:
- Day: Daily statistics for the last 90 days.
@@ -100,6 +96,7 @@ The GroupBy parameter specifies how to return the results. Valid values are:
Type: GroupBy
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -109,15 +106,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -127,15 +122,13 @@ Accept wildcard characters: False
```
### -UMDialPlan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMDialPlan parameter specifies the Unified Messaging (UM) dial plan to show statistics for. If you don't specify a dial plan, statistics are included for all dial plans in the organization.
```yaml
Type: UMDialPlanIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -145,15 +138,13 @@ Accept wildcard characters: False
```
### -UMIPGateway
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMIPGateway parameter specifies the UM IP gateway to show statistics for. If you don't specify a UM IP gateway, statistics are included for all UM IP gateways for a selected dial plan, or, if no dial plan is selected, results will be returned for all UM IP gateways in the organization.
```yaml
Type: UMIPGatewayIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md b/exchange/exchange-ps/exchange/Get-UMDialPlan.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md
rename to exchange/exchange-ps/exchange/Get-UMDialPlan.md
index dbac8b385c..fe86e9ee42 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md
+++ b/exchange/exchange-ps/exchange/Get-UMDialPlan.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umdialplan
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMDialPlan
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umdialplan
-schema: 2.0.0
-title: Get-UMDialPlan
+ms.reviewer:
---
# Get-UMDialPlan
@@ -53,15 +52,13 @@ This example displays a formatted list of properties for the UM dial plan MyUMDi
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the UM dial plan ID.
```yaml
Type: UMDialPlanIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md b/exchange/exchange-ps/exchange/Get-UMHuntGroup.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md
rename to exchange/exchange-ps/exchange/Get-UMHuntGroup.md
index 2c4eae3937..d1a7328d41 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md
+++ b/exchange/exchange-ps/exchange/Get-UMHuntGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umhuntgroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMHuntGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umhuntgroup
-schema: 2.0.0
-title: Get-UMHuntGroup
+ms.reviewer:
---
# Get-UMHuntGroup
@@ -61,15 +60,13 @@ This example displays all of the UM hunt groups associated with the UM dial plan
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for the UM hunt group being viewed. This is the directory object ID for the UM hunt group.
```yaml
Type: UMHuntGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -UMDialPlan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMDialPlan parameter specifies the UM dial plan associated with a UM hunt group.
```yaml
Type: UMDialPlanIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md b/exchange/exchange-ps/exchange/Get-UMIPGateway.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md
rename to exchange/exchange-ps/exchange/Get-UMIPGateway.md
index a34b158d04..f027b0d0a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md
+++ b/exchange/exchange-ps/exchange/Get-UMIPGateway.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umipgateway
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMIPGateway
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umipgateway
-schema: 2.0.0
-title: Get-UMIPGateway
+ms.reviewer:
---
# Get-UMIPGateway
@@ -63,15 +62,13 @@ This example displays all the UM IP gateways including IP gateway simulators in
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for the UM IP gateway being viewed. This parameter is the directory object ID for the UM IP gateway.
```yaml
Type: UMIPGatewayIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -81,15 +78,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -99,9 +94,6 @@ Accept wildcard characters: False
```
### -IncludeSimulator
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The IncludeSimulator switch retrieves the simulator of the UM IP gateway being viewed. You don't need to specify a value with this switch.
A simulator allows a client to connect to the Mailbox server.
@@ -110,6 +102,7 @@ A simulator allows a client to connect to the Mailbox server.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md b/exchange/exchange-ps/exchange/Get-UMMailbox.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md
rename to exchange/exchange-ps/exchange/Get-UMMailbox.md
index b2de66ff19..215a6b501d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md
+++ b/exchange/exchange-ps/exchange/Get-UMMailbox.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ummailbox
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMMailbox
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ummailbox
-schema: 2.0.0
-title: Get-UMMailbox
+ms.reviewer:
---
# Get-UMMailbox
@@ -71,9 +70,6 @@ This example displays detailed information for the UM-enabled mailbox for tonysm
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the UM-enabled mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -91,6 +87,7 @@ The Identity parameter specifies the UM-enabled mailbox that you want to view. Y
Type: MailboxIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -100,9 +97,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -115,6 +109,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -124,9 +119,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -135,6 +127,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -144,15 +137,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -162,9 +153,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -180,6 +168,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -189,9 +178,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -203,6 +189,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -212,9 +199,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -226,6 +210,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -235,9 +220,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -248,6 +230,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -257,15 +240,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -275,9 +256,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -292,6 +270,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md b/exchange/exchange-ps/exchange/Get-UMMailboxPIN.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md
rename to exchange/exchange-ps/exchange/Get-UMMailboxPIN.md
index 04ded39c11..c3eb5e4cc0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md
+++ b/exchange/exchange-ps/exchange/Get-UMMailboxPIN.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ummailboxpin
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMMailboxPIN
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ummailboxpin
-schema: 2.0.0
-title: Get-UMMailboxPin
+ms.reviewer:
---
# Get-UMMailboxPin
@@ -15,7 +14,7 @@ title: Get-UMMailboxPin
## SYNOPSIS
This cmdlet is available only in on-premises Exchange.
-Use the Get-UMMailboxPin cmdlet to return information from a Unified Messaging (UM)-enabled user's mailbox.
+Use the Get-UMMailboxPIN cmdlet to return information from a Unified Messaging (UM)-enabled user's mailbox.
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
@@ -33,7 +32,7 @@ Get-UMMailboxPin [[-Identity] ]
```
## DESCRIPTION
-The Get-UMMailboxPin cmdlet returns information calculated from the PIN data stored in encrypted form in the user's mailbox. This cmdlet also shows whether the mailbox or user access has been locked out.
+The Get-UMMailboxPIN cmdlet returns information calculated from the PIN data stored in encrypted form in the user's mailbox. This cmdlet also shows whether the mailbox or user access has been locked out.
After this task is completed, you can view information on a user's mailbox.
@@ -43,14 +42,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
### Example 1
```powershell
-Get-UMMailboxPin
+Get-UMMailboxPIN
```
This example displays the UM mailbox PIN-related properties for all UM-enabled users.
### Example 2
```powershell
-Get-UMMailboxPin -Identity tonysmith@contoso.com
+Get-UMMailboxPIN -Identity tonysmith@contoso.com
```
This example displays the UM mailbox PIN-related properties for tonysmith@contoso.com.
@@ -58,9 +57,6 @@ This example displays the UM mailbox PIN-related properties for tonysmith@contos
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -78,6 +74,7 @@ The Identity parameter specifies the mailbox that you want to view. You can use
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -87,9 +84,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -98,6 +92,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -107,15 +102,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -125,9 +118,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -139,6 +129,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -148,9 +139,6 @@ Accept wildcard characters: False
```
### -IgnoreErrors
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The IgnoreErrors switch specifies whether to ignore errors. You don't need to specify a value with this switch.
When you use this switch, errors that occur are written as warnings.
@@ -159,6 +147,7 @@ When you use this switch, errors that occur are written as warnings.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -168,9 +157,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -181,6 +167,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -190,15 +177,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md b/exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md
rename to exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md
index 6bb94bc162..d3e95a0446 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-UMMailboxPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ummailboxpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Get-UMMailboxPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ummailboxpolicy
-schema: 2.0.0
-title: Get-UMMailboxPolicy
+ms.reviewer:
---
# Get-UMMailboxPolicy
@@ -61,15 +60,13 @@ This examples displays all the UM mailbox policies associated with the UM dial p
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the identifier for the UM mailbox policy being viewed. This is the directory object ID for the UM mailbox policy.
```yaml
Type: MailboxPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -UMDialPlan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMDialPlan parameter specifies that all UM mailbox policies associated with the UM dial plan are displayed.
```yaml
Type: UMDialPlanIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md b/exchange/exchange-ps/exchange/Get-UMService.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMService.md
rename to exchange/exchange-ps/exchange/Get-UMService.md
index 1baf293205..6551e952a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md
+++ b/exchange/exchange-ps/exchange/Get-UMService.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umservice
applicable: Exchange Server 2013, Exchange Server 2016
+title: Get-UMService
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umservice
-schema: 2.0.0
-title: Get-UMService
+ms.reviewer:
---
# Get-UMService
@@ -53,9 +52,6 @@ This example displays detailed information for the Microsoft Exchange Unified Me
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The Identity parameter specifies the Mailbox server that hosts the Unified Messaging service configuration you want to view. You can use any value that uniquely identifies the server. For example:
- Name
@@ -67,6 +63,7 @@ The Identity parameter specifies the Mailbox server that hosts the Unified Messa
Type: UMServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: 1
@@ -76,15 +73,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md b/exchange/exchange-ps/exchange/Get-UmServer.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md
rename to exchange/exchange-ps/exchange/Get-UmServer.md
index eeb14f3928..0ba48166ad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md
+++ b/exchange/exchange-ps/exchange/Get-UmServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-umserver
applicable: Exchange Server 2010
+title: Get-UmServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-umserver
-schema: 2.0.0
-title: Get-UMServer
+ms.reviewer:
---
# Get-UMServer
@@ -55,9 +54,6 @@ This example returns detailed information for the Unified Messaging server named
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010
-
The Identity parameter specifies the Unified Messaging server that you want to view. You can use any value that uniquely identifies the server. For example:
- Name
@@ -69,6 +65,7 @@ The Identity parameter specifies the Unified Messaging server that you want to v
Type: UMServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: 1
@@ -78,15 +75,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UnifiedAuditLogRetentionPolicy.md
rename to exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md
index 9156191778..07a961fcf8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedAuditLogRetentionPolicy.md
+++ b/exchange/exchange-ps/exchange/Get-UnifiedAuditLogRetentionPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-unifiedauditlogretentionpolicy
applicable: Security & Compliance
+title: Get-UnifiedAuditLogRetentionPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-unifiedauditlogretentionpolicy
-schema: 2.0.0
-title: Get-UnifiedAuditLogRetentionPolicy
+ms.reviewer:
---
# Get-UnifiedAuditLogRetentionPolicy
@@ -54,9 +53,6 @@ This example lists the configurable properties for all audit log retention polic
## PARAMETERS
### -Operation
-
-> Applicable: Security & Compliance
-
The Operations parameter filters the results by the operations that are specified in the policy. For a list of the available values for this parameter, see [Audited activities](https://learn.microsoft.com/purview/audit-log-activities).
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -65,6 +61,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -74,15 +71,13 @@ Accept wildcard characters: False
```
### -RecordType
-
-> Applicable: Security & Compliance
-
The RecordType parameter filters the results by the record types that are defined in the policy. For details about the available values, see [AuditLogRecordType](https://learn.microsoft.com/office/office-365-management-api/office-365-management-activity-api-schema#auditlogrecordtype).
```yaml
Type: AuditRecordType
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -92,9 +87,6 @@ Accept wildcard characters: False
```
### -RetentionDuration
-
-> Applicable: Security & Compliance
-
The RetentionDuration parameter filters the policy results by the retention duration specified in the policy. Valid values are:
- ThreeMonths
@@ -108,6 +100,7 @@ Type: UnifiedAuditLogRetentionDuration
Parameter Sets: (All)
Aliases:
Accepted values: ThreeMonths, SixMonths, NineMonths, TwelveMonths, TenYears
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -117,9 +110,6 @@ Accept wildcard characters: False
```
### -UserId
-
-> Applicable: Security & Compliance
-
The UserIds parameter filters the policy results by the ID of the users who are specified in the policy.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -128,6 +118,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md b/exchange/exchange-ps/exchange/Get-UnifiedGroup.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md
rename to exchange/exchange-ps/exchange/Get-UnifiedGroup.md
index 0673369181..0d661079bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md
+++ b/exchange/exchange-ps/exchange/Get-UnifiedGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-unifiedgroup
applicable: Exchange Online, Exchange Online Protection
+title: Get-UnifiedGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-unifiedgroup
-schema: 2.0.0
-title: Get-UnifiedGroup
+ms.reviewer:
---
# Get-UnifiedGroup
@@ -104,9 +103,6 @@ This example returns Microsoft 365 Groups that are created when a Microsoft Team
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the Microsoft 365 Group that you want to view. You can use any value that uniquely identifies the Microsoft 365 Group. For example:
- Name
@@ -122,6 +118,7 @@ The Identity parameter specifies the Microsoft 365 Group that you want to view.
Type: UnifiedGroupIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -131,15 +128,13 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -149,9 +144,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -167,6 +159,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -176,9 +169,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of AcceptMessagesOnlyFromSendersOrMembers recipients in the AcceptMessagesOnlyFromSendersOrMembersWithDisplayNames property. You don't need to specify a value with this switch.
This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, AcceptMessagesOnlyFromSendersOrMembers recipients are shown as GUIDs and the AcceptMessagesOnlyFromSendersOrMembersWithDisplayNames property is empty.
@@ -187,6 +177,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -196,9 +187,6 @@ Accept wildcard characters: False
```
### -IncludeAllProperties
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeAllProperties switch specifies whether to include the values of all properties in the results. You don't need to specify a value with this switch.
If you don't use this switch, the values of some properties (for example, CalendarMemberReadOnly, CalendarUrl, InboxUrl, PeopleUrl, and PhotoUrl) might appear blank.
@@ -207,6 +195,7 @@ If you don't use this switch, the values of some properties (for example, Calend
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -216,9 +205,6 @@ Accept wildcard characters: False
```
### -IncludeBypassModerationFromSendersOrMembersWithDisplayNames
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeBypassModerationFromSendersOrMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of BypassModerationFromSendersOrMembers recipients in the BypassModerationFromSendersOrMembersWithDisplayNames property. You don't need to specify a value with this switch.
This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, BypassModerationFromSendersOrMembers recipients are shown as GUIDs and the BypassModerationFromSendersOrMembersWithDisplayNames property is empty.
@@ -227,6 +213,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -236,9 +223,6 @@ Accept wildcard characters: False
```
### -IncludeGrantSendOnBehalfToWithDisplayNames
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeGrantSendOnBehalfToWithDisplayNames switch specifies whether to return the SMTP addresses and display names of GrantSendOnBehalfTo recipients in the GrantSendOnBehalfToWithDisplayNames property. You don't need to specify a value with this switch.
This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, GrantSendOnBehalfTo recipients are shown as GUIDs and the GrantSendOnBehalfToWithDisplayNames property is empty.
@@ -247,6 +231,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -256,9 +241,6 @@ Accept wildcard characters: False
```
### -IncludeModeratedByWithDisplayNames
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeModeratedByWithDisplayNames switch specifies whether to return the SMTP addresses and display names of ModeratedBy recipients in the ModeratedByWithDisplayNames property. You don't need to specify a value with this switch.
This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, ModeratedBy recipients are shown as GUIDs and the ModeratedByWithDisplayNames property is empty.
@@ -267,6 +249,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -276,9 +259,6 @@ Accept wildcard characters: False
```
### -IncludeRejectMessagesFromSendersOrMembersWithDisplayNames
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeRejectMessagesFromSendersOrMembersWithDisplayNames switch specifies whether to return the SMTP addresses and display names of RejectMessagesFromSendersOrMembers recipients in the RejectMessagesFromSendersOrMembersWithDisplayNames property. You don't need to specify a value with this switch.
This switch was introduced to restore human-readable identifiers in the results of the cmdlet. If you don't use this switch, ModeratedBy recipients are shown as GUIDs and the RejectMessagesFromSendersOrMembersWithDisplayNames property is empty.
@@ -287,6 +267,7 @@ This switch was introduced to restore human-readable identifiers in the results
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -296,9 +277,6 @@ Accept wildcard characters: False
```
### -IncludeSoftDeletedGroups
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncludeSoftDeletedGroups switch specifies whether to include soft-deleted Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
Soft-deleted Microsoft 365 Groups are deleted groups that are still recoverable.
@@ -307,6 +285,7 @@ Soft-deleted Microsoft 365 Groups are deleted groups that are still recoverable.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -316,15 +295,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -334,9 +311,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -351,6 +325,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md b/exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md
rename to exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md
index daf58d4d2b..e47851e9e1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md
+++ b/exchange/exchange-ps/exchange/Get-UnifiedGroupLinks.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-unifiedgrouplinks
applicable: Exchange Online, Exchange Online Protection
+title: Get-UnifiedGroupLinks
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-unifiedgrouplinks
-schema: 2.0.0
-title: Get-UnifiedGroupLinks
+ms.reviewer:
---
# Get-UnifiedGroupLinks
@@ -44,9 +43,6 @@ This example show the members of the Microsoft 365 Group named Human Resources D
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the Microsoft 365 Group that you want to view. You can use any value that uniquely identifies the Microsoft 365 Group. For example:
- Name
@@ -60,6 +56,7 @@ The Identity parameter specifies the Microsoft 365 Group that you want to view.
Type: UnifiedGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -LinkType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The LinkType parameter filters the results by recipient roles in the Microsoft 365 Group. Valid values are:
- Members: Participate in conversations, create Teams channels, collaborate on files, and edit the connected SharePoint site.
@@ -82,6 +76,7 @@ The LinkType parameter filters the results by recipient roles in the Microsoft 3
Type: LinkType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -91,15 +86,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-User.md b/exchange/exchange-ps/exchange/Get-User.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Get-User.md
rename to exchange/exchange-ps/exchange/Get-User.md
index e2d12cf058..3cafe8aba0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-User.md
+++ b/exchange/exchange-ps/exchange/Get-User.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-user
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: Get-User
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-user
-schema: 2.0.0
-title: Get-User
+ms.reviewer:
---
# Get-User
@@ -103,9 +102,6 @@ This example uses the Filter parameter to retrieve information about all users t
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Identity parameter the user that you want to view. You can use any value that uniquely identifies the user. For example:
- Name
@@ -118,6 +114,7 @@ The Identity parameter the user that you want to view. You can use any value tha
Type: UserIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: 1
@@ -127,9 +124,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -142,6 +136,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -151,9 +146,6 @@ Accept wildcard characters: False
```
### -Arbitration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Arbitration switch is required to return arbitration mailboxes in the results. You don't need to specify a value with this switch.
@@ -166,6 +158,7 @@ To return arbitration mailboxes that are used to store audit log settings or dat
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -175,9 +168,6 @@ Accept wildcard characters: False
```
### -AuditLog
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The AuditLog switch is required to return audit log mailboxes in the results. You don't need to specify a value with this switch.
@@ -190,6 +180,7 @@ To return other types of arbitration mailboxes, don't use this switch. Instead,
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -199,9 +190,6 @@ Accept wildcard characters: False
```
### -AuxAuditLog
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The AuxAuditLog switch is required to return auxiliary audit log mailboxes in the results. You don't need to specify a value with this switch.
@@ -214,6 +202,7 @@ To return other types of arbitration mailboxes, don't use this switch. Instead,
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -223,9 +212,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
@@ -236,6 +222,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -245,9 +232,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -256,6 +240,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -265,9 +250,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -283,6 +265,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -292,9 +275,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
@@ -308,6 +288,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -317,9 +298,6 @@ Accept wildcard characters: False
```
### -IncludeDirectReportsWithDisplayNames
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
{{ Fill IncludeDirectReportsWithDisplayNames Description }}
@@ -328,6 +306,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: Identity, AnrSet
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -337,9 +316,6 @@ Accept wildcard characters: False
```
### -IsVIP
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The IsVIP switch filters the results by priority accounts. You don't need to specify a value with this switch.
@@ -350,6 +326,7 @@ For more information about priority accounts, see [Manage and monitor priority a
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -359,9 +336,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -373,6 +347,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -382,9 +357,6 @@ Accept wildcard characters: False
```
### -PublicFolder
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
-
The PublicFolder switch is required to return public folder mailboxes in the results. You don't need to specify a value with this switch.
Public folder mailboxes are specially designed mailboxes that store the hierarchy and content of public folders.
@@ -393,6 +365,7 @@ Public folder mailboxes are specially designed mailboxes that store the hierarch
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
Required: False
Position: Named
@@ -402,9 +375,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
@@ -417,6 +387,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -426,9 +397,6 @@ Accept wildcard characters: False
```
### -RecipientTypeDetails
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The RecipientTypeDetails parameter filters the results by the specified user subtype. Valid values are:
- DisabledUser
@@ -461,6 +429,7 @@ You can specify multiple values separated by commas.
Type: RecipientTypeDetails[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -470,15 +439,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -488,9 +455,6 @@ Accept wildcard characters: False
```
### -Sortby
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -508,6 +472,7 @@ You can sort by the following properties:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
@@ -517,9 +482,6 @@ Accept wildcard characters: False
```
### -SupervisoryReviewPolicy
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -528,6 +490,7 @@ This parameter is reserved for internal Microsoft use.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UserBriefingConfig.md b/exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UserBriefingConfig.md
rename to exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
index 4053998bbe..6c04f88148 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UserBriefingConfig.md
+++ b/exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-userbriefingconfig
applicable: Exchange Online
+title: Get-UserBriefingConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-userbriefingconfig
-schema: 2.0.0
-title: Get-UserBriefingConfig
---
# Get-UserBriefingConfig
@@ -52,15 +51,13 @@ This example returns the Briefing configuration for the user lila@contoso.com.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the user that you want to view (for example, lila@contoso.com).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -70,15 +67,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md b/exchange/exchange-ps/exchange/Get-UserPhoto.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md
rename to exchange/exchange-ps/exchange/Get-UserPhoto.md
index 5112382af9..5314df112d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md
+++ b/exchange/exchange-ps/exchange/Get-UserPhoto.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-userphoto
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-UserPhoto
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-userphoto
-schema: 2.0.0
-title: Get-UserPhoto
+ms.reviewer:
---
# Get-UserPhoto
@@ -81,9 +80,6 @@ This example displays information about the user photo that was uploaded to Pila
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the user account. You can use any value that uniquely identifies the user account. For example:
- Name
@@ -101,6 +97,7 @@ The Identity parameter specifies the user account. You can use any value that un
Type: MailboxIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -110,9 +107,6 @@ Accept wildcard characters: False
```
### -Anr
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
- CommonName (CN)
@@ -125,6 +119,7 @@ The Anr parameter specifies a string on which to perform an ambiguous name resol
Type: String
Parameter Sets: AnrSet
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -134,9 +129,6 @@ Accept wildcard characters: False
```
### -Credential
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
A value for this parameter requires the Get-Credential cmdlet. To pause this command and receive a prompt for credentials, use the value `(Get-Credential)`. Or, before you run this command, store the credentials in a variable (for example, `$cred = Get-Credential`) and then use the variable name (`$cred`) for this parameter. For more information, see [Get-Credential](https://learn.microsoft.com/powershell/module/microsoft.powershell.security/get-credential).
@@ -145,6 +137,7 @@ A value for this parameter requires the Get-Credential cmdlet. To pause this com
Type: PSCredential
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -154,15 +147,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -172,9 +163,6 @@ Accept wildcard characters: False
```
### -Filter
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -190,6 +178,7 @@ For detailed information about OPATH filters in Exchange, see [Additional OPATH
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -199,15 +188,13 @@ Accept wildcard characters: False
```
### -GroupMailbox
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The GroupMailbox switch is required to return Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -217,9 +204,6 @@ Accept wildcard characters: False
```
### -IgnoreDefaultScope
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:
@@ -231,6 +215,7 @@ This switch enables the command to access Active Directory objects that aren't c
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -240,9 +225,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -254,6 +236,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -263,15 +246,13 @@ Accept wildcard characters: False
```
### -PhotoType
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -281,9 +262,6 @@ Accept wildcard characters: False
```
### -Preview
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Preview switch filters the results by preview photos. You don't need to specify a value with this switch.
A preview photo is a photo that was uploaded to the user's account, but wasn't saved, for example, if a user uploads a photo in Outlook on the web Options, but doesn't save it. If you use the Preview switch after a user photo is saved, this cmdlet returns an error saying the preview photo doesn't exist.
@@ -292,6 +270,7 @@ A preview photo is a photo that was uploaded to the user's account, but wasn't s
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -301,9 +280,6 @@ Accept wildcard characters: False
```
### -ReadFromDomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
The command: `Set-AdServerSettings -ViewEntireForest $true` to include all objects in the forest requires the ReadFromDomainController switch. Otherwise, the command might use a global catalog that contains outdated information. Also, you might need to run multiple iterations of the command with the ReadFromDomainController switch to get the information.
@@ -314,6 +290,7 @@ By default, the recipient scope is set to the domain that hosts your Exchange se
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -323,15 +300,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -341,9 +316,6 @@ Accept wildcard characters: False
```
### -SortBy
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
If the default view doesn't include the property you're sorting by, you can append the command with ` | Format-Table -Auto Property1,Property2,...PropertyX`. to create a new view that contains all of the properties that you want to see. Wildcards (\*) in the property names are supported.
@@ -354,6 +326,7 @@ You can sort by the Id property.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md b/exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md
rename to exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md
index 47c8e975ea..b9afdf3095 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md
+++ b/exchange/exchange-ps/exchange/Get-UserPrincipalNamesSuffix.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-userprincipalnamessuffix
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-UserPrincipalNamesSuffix
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-userprincipalnamessuffix
-schema: 2.0.0
-title: Get-UserPrincipalNamesSuffix
+ms.reviewer:
---
# Get-UserPrincipalNamesSuffix
@@ -47,9 +46,6 @@ This example returns all UPN suffixes for the Active Directory forest.
## PARAMETERS
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -61,6 +57,7 @@ The OrganizationalUnit parameter filters the results based on the object's locat
Type: ExtendedOrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-VivaInsightsSettings.md b/exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-VivaInsightsSettings.md
rename to exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md
index 3e9042e558..bbfd395ab1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-VivaInsightsSettings.md
+++ b/exchange/exchange-ps/exchange/Get-VivaInsightsSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-vivainsightssettings
applicable: Exchange Online
+title: Get-VivaInsightsSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-vivainsightssettings
-schema: 2.0.0
-title: Get-VivaInsightsSettings
---
# Get-VivaInsightsSettings
@@ -59,15 +58,13 @@ This example shows the configuration of Microsoft Viva Insights in Microsoft Tea
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Online
-
The Identity parameter specifies the user that you want to view. You identify the user by their User Principal Name (UPN) (for example, roy@contoso.onmicrosoft.com).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -77,9 +74,6 @@ Accept wildcard characters: False
```
### -Feature
-
-> Applicable: Exchange Online
-
The Feature parameter filters the results by the specified Microsoft Viva Insights feature. Valid values are:
- Headspace: Represents all features of Headspace.
@@ -89,6 +83,7 @@ The Feature parameter filters the results by the specified Microsoft Viva Insigh
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeature.md b/exchange/exchange-ps/exchange/Get-VivaModuleFeature.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeature.md
rename to exchange/exchange-ps/exchange/Get-VivaModuleFeature.md
index 3cff28b979..b2787501f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeature.md
+++ b/exchange/exchange-ps/exchange/Get-VivaModuleFeature.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeature
applicable: Exchange Online
+title: Get-VivaModuleFeature
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-vivamodulefeature
-schema: 2.0.0
-title: Get-VivaModuleFeature
+ms.reviewer:
---
# Get-VivaModuleFeature
@@ -56,15 +56,13 @@ This example returns the details of the Reflection feature in Viva Insights.
## PARAMETERS
### -ModuleId
-
-> Applicable: Exchange Online
-
The ModuleId parameter specifies the Viva module of the features that you want to view.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -74,9 +72,6 @@ Accept wildcard characters: False
```
### -FeatureId
-
-> Applicable: Exchange Online
-
The FeatureId parameter specifies the specific feature in the Viva module that you want to view.
You can view details about all the features in a Viva module that support feature access controls by running the cmdlet without the FeatureId parameter. These details include the identifiers of all features in a Viva module that support feature access controls.
@@ -85,6 +80,7 @@ You can view details about all the features in a Viva module that support featur
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Positional
@@ -94,15 +90,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeatureEnablement.md b/exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md
similarity index 98%
rename from exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeatureEnablement.md
rename to exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md
index 47a20bcf39..8fed8e655e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeatureEnablement.md
+++ b/exchange/exchange-ps/exchange/Get-VivaModuleFeatureEnablement.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeatureenablement
applicable: Exchange Online
+title: Get-VivaModuleFeatureEnablement
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-vivamodulefeatureenablement
-schema: 2.0.0
-title: Get-VivaModuleFeatureEnablement
+ms.reviewer:
---
# Get-VivaModuleFeatureEnablement
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeaturePolicy.md
rename to exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md
index bebd8abdc5..1e4a57e8a1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-VivaModuleFeaturePolicy.md
+++ b/exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md
@@ -1,13 +1,13 @@
---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-vivamodulefeaturepolicy
applicable: Exchange Online
+title: Get-VivaModuleFeaturePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-vivamodulefeaturepolicy
-schema: 2.0.0
-title: Get-VivaModuleFeaturePolicy
+ms.reviewer:
---
# Get-VivaModuleFeaturePolicy
@@ -88,17 +88,15 @@ This example returns details about the policies for all features across all Viva
## PARAMETERS
### -FeatureId
-
-> Applicable: Exchange Online
-
The FeatureId parameter specifies the feature in the Viva module that you want to view the policies for.
To view details about the features in a Viva module that support feature access controls, refer to the Get-VivaModuleFeature cmdlet. The details provided by the Get-VivaModuleFeature cmdlet include the feature identifier.
```yaml
Type: String
-Parameter Sets: FeaturePolicy, FeaturePolicyWithMembers
+Parameter Sets: FeaturePolicy
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -107,16 +105,27 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -ModuleId
+```yaml
+Type: String
+Parameter Sets: FeaturePolicyWithMembers
+Aliases:
+Applicable: Exchange Online
-> Applicable: Exchange Online
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: True
+```
+### -ModuleId
The ModuleId parameter specifies the Viva module of the feature policies that you want to view.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -126,9 +135,6 @@ Accept wildcard characters: False
```
### -PolicyId
-
-> Applicable: Exchange Online
-
The PolicyId parameter specifies the specific policy for the feature in the Viva module that you want to view.
To view details about all policies for a feature in a Viva module, run this cmdlet without the PolicyId parameter. These details include the identifiers of all the policies for a feature in a Viva module.
@@ -137,6 +143,7 @@ To view details about all policies for a feature in a Viva module, run this cmdl
Type: String
Parameter Sets: FeaturePolicy
Aliases:
+Applicable: Exchange Online
Required: False
Position: Positional
@@ -146,10 +153,7 @@ Accept wildcard characters: False
```
### -MemberIds
-
-> Applicable: Exchange Online
-
-The MemberIds parameter specifies the specific users or groups for which you want to view the policies for the feature in the Viva module.
+The MemberIds parameter specifies the specific users or groups for which you want to view the policies for the feature in the Viva module.
You can provide up to three member IDs. Use the \* character to specify all modules or features.
@@ -157,6 +161,7 @@ You can provide up to three member IDs. Use the \* character to specify all modu
Type: String[]
Parameter Sets: FeaturePolicyWithMembers
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -166,15 +171,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Microsoft.Exchange.Management.RestApiClient.Unlimited`1[System.UInt32]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-VivaOrgInsightsDelegatedRole.md b/exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Get-VivaOrgInsightsDelegatedRole.md
rename to exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md
index b4d9ec3c12..22defddf64 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-VivaOrgInsightsDelegatedRole.md
+++ b/exchange/exchange-ps/exchange/Get-VivaOrgInsightsDelegatedRole.md
@@ -1,12 +1,12 @@
---
-author: chrisda
external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-vivaorginsightsdelegatedrole
-schema: 2.0.0
+Module Name: ExchangeOnlineManagement
+online version: https://learn.microsoft.com/powershell/module/exchange/get-vivaorginsightsdelegatedrole
title: Get-VivaOrgInsightsDelegatedRole
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
---
# Get-VivaOrgInsightsDelegatedRole
@@ -49,9 +49,6 @@ This example filters the results by the specified delegator.
## PARAMETERS
### -Delegator
-
-> Applicable: Exchange Online
-
The Delegator parameter specifies the account of the leader that can view organizational insights. This capability is given to delegates.
A valid value for this parameter is the ObjectID value of the delegator account. Use the [Get-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/get-mguser) cmdlet in Microsoft Graph PowerShell to find this value.
@@ -60,6 +57,7 @@ A valid value for this parameter is the ObjectID value of the delegator account.
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -69,15 +67,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Exchange Online
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md b/exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md
rename to exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md
index bfc03e42ee..1345ae232f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/Get-WebServicesVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-webservicesvirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-WebServicesVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-webservicesvirtualdirectory
-schema: 2.0.0
-title: Get-WebServicesVirtualDirectory
+ms.reviewer:
---
# Get-WebServicesVirtualDirectory
@@ -72,9 +71,6 @@ This example returns a summary list of all virtual directories in the client acc
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the EWS virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
- Name or Server\\Name
@@ -89,6 +85,7 @@ You can't use the Identity and Server parameters in the same command.
Type: VirtualDirectoryIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -98,9 +95,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -114,6 +108,7 @@ You can't use the Server and Identity parameters in the same command.
Type: ServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -123,9 +118,6 @@ Accept wildcard characters: False
```
### -ADPropertiesOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
If you don't use this switch, the properties in Active Directory and in the Internet Information Services (IIS) metabase are returned.
@@ -134,6 +126,7 @@ If you don't use this switch, the properties in Active Directory and in the Inte
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -143,15 +136,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -161,9 +152,6 @@ Accept wildcard characters: False
```
### -ShowMailboxVirtualDirectories
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
By default, this cmdlet shows information about virtual directories in the Client Access services on Mailbox servers. Client connections are proxied from the Client Access services on Mailbox servers to the backend services on Mailbox servers. Clients don't connect directly to the backend services.
@@ -174,6 +162,7 @@ We recommend that you use this parameter only under the direction of Microsoft C
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md b/exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md
rename to exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md
index 0779c91d83..3be7ea0728 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/exchange/Get-X400AuthoritativeDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-x400authoritativedomain
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Get-X400AuthoritativeDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-x400authoritativedomain
-schema: 2.0.0
-title: Get-X400AuthoritativeDomain
+ms.reviewer:
---
# Get-X400AuthoritativeDomain
@@ -15,7 +14,7 @@ title: Get-X400AuthoritativeDomain
## SYNOPSIS
This cmdlet is available only in on-premises Exchange.
-Use the Get-X400AuthoritativeDomain cmdlet to view the configuration information for the X.400 authoritative domains configured in your organization. For more information about how to configure an X.400 authoritative domain, see [Set-X400AuthoritativeDomain](https://learn.microsoft.com/powershell/module/exchangepowershell/set-x400authoritativedomain).
+Use the Get-X400AuthoritativeDomain cmdlet to view the configuration information for the X.400 authoritative domains configured in your organization. For more information about how to configure an X.400 authoritative domain, see [Set-X400AuthoritativeDomain](https://learn.microsoft.com/powershell/module/exchange/set-x400authoritativedomain).
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
@@ -42,15 +41,13 @@ This example displays detailed information about the X.400 authoritative domain
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies a string value for the X.400 authoritative domain. Enter either the GUID or the name of the remote domain.
```yaml
Type: X400AuthoritativeDomainIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -60,9 +57,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -71,6 +65,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Get-eDiscoveryCaseAdmin.md
rename to exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md
index b5742b5617..2af5f1721a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-eDiscoveryCaseAdmin.md
+++ b/exchange/exchange-ps/exchange/Get-eDiscoveryCaseAdmin.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-ediscoverycaseadmin
applicable: Security & Compliance
+title: Get-eDiscoveryCaseAdmin
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/get-ediscoverycaseadmin
-schema: 2.0.0
-title: Get-eDiscoveryCaseAdmin
+ms.reviewer:
---
# Get-eDiscoveryCaseAdmin
@@ -44,15 +43,13 @@ This example returns a summary list of all eDiscovery Administrators.
## PARAMETERS
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -62,15 +59,13 @@ Accept wildcard characters: False
```
### -ResultSize
-
-> Applicable: Security & Compliance
-
The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md b/exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md
rename to exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md
index 0785727433..bdec677fd8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md
+++ b/exchange/exchange-ps/exchange/Import-DlpPolicyCollection.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/import-dlppolicycollection
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Import-DlpPolicyCollection
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/import-dlppolicycollection
-schema: 2.0.0
-title: Import-DlpPolicyCollection
+ms.reviewer:
---
# Import-DlpPolicyCollection
@@ -51,15 +50,13 @@ This example imports the DLP policy collection in the file C:\\My Documents\\DLP
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the name of the DLP policy you want to import. The DLP policy must exist in the XML file you specify with the FileData parameter.
```yaml
Type: DlpPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -69,9 +66,6 @@ Accept wildcard characters: False
```
### -FileData
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FileData parameter specifies the DLP policy collection file you want to import.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -80,6 +74,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -89,9 +84,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -101,6 +93,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -110,15 +103,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -128,9 +119,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -139,6 +127,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -148,15 +137,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md b/exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md
rename to exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md
index 7cd67448e0..41752441f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/exchange/Import-DlpPolicyTemplate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/import-dlppolicytemplate
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Import-DlpPolicyTemplate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/import-dlppolicytemplate
-schema: 2.0.0
-title: Import-DlpPolicyTemplate
+ms.reviewer:
---
# Import-DlpPolicyTemplate
@@ -43,9 +42,6 @@ This example imports the DLP policy template file C:\\My Documents\\External DLP
## PARAMETERS
### -FileData
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The FileData parameter specifies the DLP policy template file you want to import.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -54,6 +50,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -63,9 +60,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -75,6 +69,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -84,15 +79,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md b/exchange/exchange-ps/exchange/Import-ExchangeCertificate.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md
rename to exchange/exchange-ps/exchange/Import-ExchangeCertificate.md
index 16a6171171..f9175f98ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md
+++ b/exchange/exchange-ps/exchange/Import-ExchangeCertificate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/import-exchangecertificate
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Import-ExchangeCertificate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/import-exchangecertificate
-schema: 2.0.0
-title: Import-ExchangeCertificate
+ms.reviewer:
---
# Import-ExchangeCertificate
@@ -102,9 +101,6 @@ This example imports a chain of certificates from the PKCS #7 file C:\\Certifica
## PARAMETERS
### -FileData
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The FileData parameter specifies the contents of the certificate file that you want to import.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -119,6 +115,7 @@ If the value contains spaces, enclose the value in quotation marks (").
Type: Byte[]
Parameter Sets: FileData
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -128,9 +125,6 @@ Accept wildcard characters: False
```
### -FileName
-
-> Applicable: Exchange Server 2013
-
**Note**: This parameter was removed from Exchange 2016 and Exchange 2019 by the [2022 H1 Cumulative Updates](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-2022-h1-cumulative-updates-for-exchange-server/ba-p/3285026) because it accepts UNC path values. To import a certificate file without using the FileName parameter, use the FileData parameter.
This parameter is available only in Exchange 2013.
@@ -145,6 +139,7 @@ If the value contains spaces, enclose the value in quotation marks (").
Type: String
Parameter Sets: Instance
Aliases:
+Applicable: Exchange Server 2013
Required: True
Position: Named
@@ -154,15 +149,13 @@ Accept wildcard characters: False
```
### -Instance
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter has been deprecated and is no longer used.
```yaml
Type: String[]
Parameter Sets: FileName
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -172,9 +165,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -184,6 +174,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -193,9 +184,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -204,6 +192,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -213,9 +202,6 @@ Accept wildcard characters: False
```
### -FriendlyName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The FriendlyName parameter specifies a friendly name for the certificate. The value must be less than 64 characters.
The friendly name value is descriptive text and doesn't affect the functionality of the certificate.
@@ -224,6 +210,7 @@ The friendly name value is descriptive text and doesn't affect the functionality
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -233,9 +220,6 @@ Accept wildcard characters: False
```
### -Password
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Password parameter specifies the password that's required to import the certificate.
You can use the following methods as a value for this parameter:
@@ -248,6 +232,7 @@ You can use the following methods as a value for this parameter:
Type: SecureString
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -257,9 +242,6 @@ Accept wildcard characters: False
```
### -PrivateKeyExportable
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key and controls whether you can export the certificate from this server. Valid values are:
- $true: The private key is exportable, so you can export the certificate from this server.
@@ -269,6 +251,7 @@ The PrivateKeyExportable parameter specifies whether the certificate has an expo
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -278,9 +261,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -294,6 +274,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -303,15 +284,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-FilePlanProperty.md b/exchange/exchange-ps/exchange/Import-FilePlanProperty.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Import-FilePlanProperty.md
rename to exchange/exchange-ps/exchange/Import-FilePlanProperty.md
index 9065fc4a6c..0a64f7f630 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-FilePlanProperty.md
+++ b/exchange/exchange-ps/exchange/Import-FilePlanProperty.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/import-fileplanproperty
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/import-fileplanproperty
+applicable: Security & Compliance
title: Import-FilePlanProperty
+schema: 2.0.0
---
# Import-FilePlanProperty
@@ -44,15 +42,13 @@ This example imports the specified CSV file.
## PARAMETERS
### -RawCsv
-
-> Applicable: Security & Compliance
-
The RawCsv parameter specifies the CSV file to import.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -62,9 +58,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -74,6 +67,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -83,15 +77,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -101,9 +93,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -112,6 +101,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -121,15 +111,13 @@ Accept wildcard characters: False
```
### -ValidateOnly
-
-> Applicable: Security & Compliance
-
The ValidateOnly switch validates the CSV file without importing. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -139,15 +127,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md b/exchange/exchange-ps/exchange/Import-JournalRuleCollection.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md
rename to exchange/exchange-ps/exchange/Import-JournalRuleCollection.md
index 20711926b1..535e6e67f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md
+++ b/exchange/exchange-ps/exchange/Import-JournalRuleCollection.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/import-journalrulecollection
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Import-JournalRuleCollection
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/import-journalrulecollection
-schema: 2.0.0
-title: Import-JournalRuleCollection
+ms.reviewer:
---
# Import-JournalRuleCollection
@@ -34,7 +33,7 @@ The Import-JournalRuleCollection cmdlet imports a journal rule collection you pr
Importing a journal rule collection from an XML file removes or overwrites all pre-existing journal rules in your organization. Make sure that you have a backup of your current journal rule collection before you import and overwrite your current journal rules.
-For more information about how to export a journal rule collection to an XML file, see [Export-JournalRuleCollection](https://learn.microsoft.com/powershell/module/exchangepowershell/export-journalrulecollection).
+For more information about how to export a journal rule collection to an XML file, see [Export-JournalRuleCollection](https://learn.microsoft.com/powershell/module/exchange/export-journalrulecollection).
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
@@ -50,15 +49,13 @@ This example imports journal rules from the XML file named ExportedJournalRules.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the name of a journal rule to be imported.
```yaml
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -FileData
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The FileData parameter specifies the XML file that contains the exported journal rule collection from the Export-JournalRuleCollection cmdlet.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -79,6 +73,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -88,9 +83,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -100,6 +92,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -109,15 +102,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -127,15 +118,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md b/exchange/exchange-ps/exchange/Import-RecipientDataProperty.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md
rename to exchange/exchange-ps/exchange/Import-RecipientDataProperty.md
index 4aa0575df7..3c8ed062fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md
+++ b/exchange/exchange-ps/exchange/Import-RecipientDataProperty.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/import-recipientdataproperty
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: Import-RecipientDataProperty
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/import-recipientdataproperty
-schema: 2.0.0
-title: Import-RecipientDataProperty
+ms.reviewer:
---
# Import-RecipientDataProperty
@@ -63,9 +62,6 @@ This example imports the picture file for Ayla Kol.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Identity parameter specifies the mailbox or contact that you're adding the picture or spoken name file to. You can use any value that uniquely identifies the user. For example:
- Name
@@ -77,6 +73,7 @@ The Identity parameter specifies the mailbox or contact that you're adding the p
Type: MailboxUserContactIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -86,9 +83,6 @@ Accept wildcard characters: False
```
### -FileData
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FileData parameter specifies the picture or spoken name file that you want to import.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -101,6 +95,7 @@ To import a spoken name, use the SpokenName switch. A valid spoken name file is
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -122,6 +114,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -131,9 +124,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -142,6 +132,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -151,9 +142,6 @@ Accept wildcard characters: False
```
### -Picture
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Picture switch specifies that you're importing the user's picture file. You don't need to specify a value with this switch.
You can't use this switch with the SpokenName switch.
@@ -162,6 +150,7 @@ You can't use this switch with the SpokenName switch.
Type: SwitchParameter
Parameter Sets: ImportPicture
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -171,9 +160,6 @@ Accept wildcard characters: False
```
### -SpokenName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SpokenName switch specifies that you're importing the user's spoken name file. You don't need to specify a value with this switch.
You can't use this switch with the Picture switch.
@@ -182,6 +168,7 @@ You can't use this switch with the Picture switch.
Type: SwitchParameter
Parameter Sets: ImportSpokenName
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -191,15 +178,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md b/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md
rename to exchange/exchange-ps/exchange/Import-TransportRuleCollection.md
index ac58f3c39e..30fae12016 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md
+++ b/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/import-transportrulecollection
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: Import-TransportRuleCollection
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/import-transportrulecollection
-schema: 2.0.0
-title: Import-TransportRuleCollection
+ms.reviewer:
---
# Import-TransportRuleCollection
@@ -35,7 +34,7 @@ Import-TransportRuleCollection [[-Identity] ] [-FileData] Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is functional only in Exchange Server 2010.
The Identity parameter specifies the transport rule that you want to import. You can use any value that uniquely identifies the rule. For example:
@@ -66,6 +62,7 @@ The Identity parameter specifies the transport rule that you want to import. You
Type: RuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: 1
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -FileData
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The FileData parameter specifies the XML file that contains the exported transport rule collection from the Export-TransportRuleCollection cmdlet.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -86,6 +80,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -107,6 +99,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -129,6 +119,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -138,9 +129,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -149,6 +137,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -158,15 +147,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md b/exchange/exchange-ps/exchange/Import-UMPrompt.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md
rename to exchange/exchange-ps/exchange/Import-UMPrompt.md
index 84ada54feb..5f34ab73ab 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md
+++ b/exchange/exchange-ps/exchange/Import-UMPrompt.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/import-umprompt
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
+title: Import-UMPrompt
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/import-umprompt
-schema: 2.0.0
-title: Import-UMPrompt
+ms.reviewer:
---
# Import-UMPrompt
@@ -90,9 +89,6 @@ This example imports the welcome greeting file AfterHoursWelcomeGreeting.wav fro
## PARAMETERS
### -PromptFileData
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The PromptFileData parameter specifies the byte array of the custom prompt.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -101,6 +97,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: UploadDialPlanPrompts, UploadAutoAttendantPrompts
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -110,15 +107,13 @@ Accept wildcard characters: False
```
### -PromptFileName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The PromptFileName parameter specifies the name of the custom prompt.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -128,15 +123,13 @@ Accept wildcard characters: False
```
### -PromptFileStream
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The PromptFileStream parameter specifies whether the audio file will be uploaded or imported as an audio stream and not a byte array. The default setting is for the audio file to imported as a byte array.
```yaml
Type: Stream
Parameter Sets: UploadAutoAttendantPromptsStream, UploadDialPlanPromptsStream
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -146,15 +139,13 @@ Accept wildcard characters: False
```
### -UMAutoAttendant
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMAutoAttendant parameter specifies the UM auto attendant ID. This parameter specifies the directory object identifier for the UM auto attendant.
```yaml
Type: UMAutoAttendantIdParameter
Parameter Sets: UploadAutoAttendantPrompts, UploadAutoAttendantPromptsStream
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -164,15 +155,13 @@ Accept wildcard characters: False
```
### -UMDialPlan
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The UMDialPlan parameter specifies the UM dial plan ID. This parameter specifies the directory object identifier for the UM dial plan.
```yaml
Type: UMDialPlanIdParameter
Parameter Sets: UploadDialPlanPrompts, UploadDialPlanPromptsStream
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: True
Position: Named
@@ -182,9 +171,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -194,6 +180,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -203,15 +190,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
@@ -221,15 +206,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md b/exchange/exchange-ps/exchange/Install-TransportAgent.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md
rename to exchange/exchange-ps/exchange/Install-TransportAgent.md
index 92cf1ae653..9e51b2aaa8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md
+++ b/exchange/exchange-ps/exchange/Install-TransportAgent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/install-transportagent
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Install-TransportAgent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/install-transportagent
-schema: 2.0.0
-title: Install-TransportAgent
+ms.reviewer:
---
# Install-TransportAgent
@@ -47,15 +46,13 @@ This example shows how a fictitious application named Test App is installed in t
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies the display name of the transport agent to be installed. The length of the name can't exceed 64 characters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -65,15 +62,13 @@ Accept wildcard characters: False
```
### -AssemblyPath
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AssemblyPath parameter specifies the location of the transport agent Microsoft.NET assembly. Universal Naming Convention (UNC) file paths can't be used.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -83,15 +78,13 @@ Accept wildcard characters: False
```
### -TransportAgentFactory
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TransportAgentFactory parameter specifies the Microsoft.NET class type of the transport agent factory. The developer of the transport agent being installed provides the transport agent factory and related information. For more information, see the documentation provided by the developer of the transport agent.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -101,9 +94,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -113,6 +103,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -122,9 +113,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -133,6 +121,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -142,9 +131,6 @@ Accept wildcard characters: False
```
### -TransportService
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
- Hub for the Transport service on Mailbox servers.
@@ -157,6 +143,7 @@ The TransportService parameter specifies the transport service that you want to
Type: TransportService
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -166,15 +153,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Install-UnifiedCompliancePrerequisite.md b/exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Install-UnifiedCompliancePrerequisite.md
rename to exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md
index 81065e9097..dfc3b902a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Install-UnifiedCompliancePrerequisite.md
+++ b/exchange/exchange-ps/exchange/Install-UnifiedCompliancePrerequisite.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/install-unifiedcomplianceprerequisite
applicable: Security & Compliance
+title: Install-UnifiedCompliancePrerequisite
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/install-unifiedcomplianceprerequisite
-schema: 2.0.0
-title: Install-UnifiedCompliancePrerequisite
+ms.reviewer:
---
# Install-UnifiedCompliancePrerequisite
@@ -72,9 +71,6 @@ This example recreates the Compliance Policy Center, even if the site has alread
## PARAMETERS
### -ForceInitialize
-
-> Applicable: Security & Compliance
-
The ForceInitialize switch recreates the Compliance Policy Center, even if it has already been created. You don't specify a value with this switch.
You can't use this switch with the LoadOnly switch.
@@ -83,6 +79,7 @@ You can't use this switch with the LoadOnly switch.
Type: SwitchParameter
Parameter Sets: Initialize
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -92,9 +89,6 @@ Accept wildcard characters: False
```
### -LoadOnly
-
-> Applicable: Security & Compliance
-
The LoadOnly switch loads the current settings of the Compliance Policy Center. You don't specify a value with this switch.
You can't use this switch with the ForceInitialize switch.
@@ -103,6 +97,7 @@ You can't use this switch with the ForceInitialize switch.
Type: SwitchParameter
Parameter Sets: LoadOnly
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -112,15 +107,13 @@ Accept wildcard characters: False
```
### -PolicyCenterSiteOwner
-
-> Applicable: Security & Compliance
-
The PolicyCenterSiteOwner parameter specifies the email address of the owner of the Compliance Policy Center. You can use this parameter by itself or with the ForceInitialize switch.
```yaml
Type: SmtpAddress
Parameter Sets: Initialize
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md b/exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md
similarity index 85%
rename from exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md
rename to exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md
index 2faa34ef03..d208ed10b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md
+++ b/exchange/exchange-ps/exchange/Invoke-ComplianceSearchActionStep.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/invoke-compliancesearchactionstep
applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+title: Invoke-ComplianceSearchActionStep
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/invoke-compliancesearchactionstep
-schema: 2.0.0
-title: Invoke-ComplianceSearchActionStep
+ms.reviewer:
---
# Invoke-ComplianceSearchActionStep
@@ -41,15 +40,13 @@ This cmdlet is reserved for internal Microsoft use.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
-
This cmdlet is reserved for internal Microsoft use.
```yaml
Type: ComplianceSearchActionIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
Required: False
Position: 1
@@ -59,15 +56,13 @@ Accept wildcard characters: False
```
### -Parameters
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
-
This cmdlet is reserved for internal Microsoft use.
```yaml
Type: PSObject
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
Required: True
Position: Named
@@ -77,15 +72,13 @@ Accept wildcard characters: False
```
### -Step
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
-
This cmdlet is reserved for internal Microsoft use.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
Required: True
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSecurityFilterAction.md b/exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSecurityFilterAction.md
rename to exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md
index 43023c90bc..af2ca95201 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSecurityFilterAction.md
+++ b/exchange/exchange-ps/exchange/Invoke-ComplianceSecurityFilterAction.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/invoke-compliancesecurityfilteraction
applicable: Security & Compliance
+title: Invoke-ComplianceSecurityFilterAction
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/invoke-compliancesecurityfilteraction
-schema: 2.0.0
-title: Invoke-ComplianceSecurityFilterAction
+ms.reviewer:
---
# Invoke-ComplianceSecurityFilterAction
@@ -109,9 +108,6 @@ This example sets the boundary of the specified OneDrive site to the specified C
## PARAMETERS
### -Action
-
-> Applicable: Security & Compliance
-
The Action parameter specifies the action for the command. Valid values are:
- GetStatus
@@ -121,6 +117,7 @@ The Action parameter specifies the action for the command. Valid values are:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -130,9 +127,6 @@ Accept wildcard characters: False
```
### -EmailAddress
-
-> Applicable: Security & Compliance
-
The EmailAddress parameter specifies the the affected user mailbox. You can use the following values to uniquely identify the mailbox:
- Name
@@ -146,6 +140,7 @@ If the value contains spaces, enclose the value in quotation marks.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 2
@@ -155,9 +150,6 @@ Accept wildcard characters: False
```
### -PropertyName
-
-> Applicable: Security & Compliance
-
The PropertyName parameter specifies the name of the property of the compliance boundary for the OneDrive site that you want to view or modify. Valid values are:
- CustomAttribute1 to CustomAttribute15
@@ -168,6 +160,7 @@ Use the PropertyValue parameter to set the compliance boundary.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 3
@@ -177,15 +170,13 @@ Accept wildcard characters: False
```
### -PropertyValue
-
-> Applicable: Security & Compliance
-
The PropertyValue parameter specifies the value of the PropertyName value when you use the Action parameter value Set to set the compliance boundary of a OneDrive site. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 4
@@ -195,15 +186,13 @@ Accept wildcard characters: False
```
### -SiteUrl
-
-> Applicable: Security & Compliance
-
The SiteUrl parameter specifies the OneDrive site that you want to view or modify. This parameter uses the syntax `https://-my.sharepoint.com/personal/__onmicrosoft_com/_layouts/15/onedrive.aspx`. For example: `https://contoso-my.sharepoint.com/personal/lila_contoso_onmicrosoft_com/_layouts/15/onedrive.aspx`.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 5
@@ -213,9 +202,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -225,6 +211,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -234,15 +221,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-HoldRemovalAction.md b/exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/Invoke-HoldRemovalAction.md
rename to exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md
index ebf40db69c..3579f174b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Invoke-HoldRemovalAction.md
+++ b/exchange/exchange-ps/exchange/Invoke-HoldRemovalAction.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/invoke-holdremovalaction
applicable: Security & Compliance
+title: Invoke-HoldRemovalAction
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/invoke-holdremovalaction
-schema: 2.0.0
-title: Invoke-HoldRemovalAction
+ms.reviewer:
---
# Invoke-HoldRemovalAction
@@ -61,9 +60,6 @@ This example displays all hold removals that have been done using this cmdlet.
## PARAMETERS
### -Action
-
-> Applicable: Security & Compliance
-
The Action parameter specifies the mode that the cmdlet operates in. Valid values are:
- GetHoldRemovals: Shows all hold removals that were done using this cmdlet.
@@ -74,6 +70,7 @@ The Action parameter specifies the mode that the cmdlet operates in. Valid value
Type: HoldRemovalActionType
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -83,9 +80,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -95,6 +89,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -104,9 +99,6 @@ Accept wildcard characters: False
```
### -ExchangeLocation
-
-> Applicable: Security & Compliance
-
The ExchangeLocation parameter specifies the email address of the mailbox that contains the holds to view or remove.
This parameter is required when you use the value GetHolds or RemoveHold for the Action parameter.
@@ -115,6 +107,7 @@ This parameter is required when you use the value GetHolds or RemoveHold for the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -124,9 +117,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to force remove the hold even when the policy is active. Instead, you should remove the hold from the case hold policy.
@@ -135,6 +125,7 @@ You can use this switch to force remove the hold even when the policy is active.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -144,9 +135,6 @@ Accept wildcard characters: False
```
### -HoldId
-
-> Applicable: Security & Compliance
-
The HoldId parameter specifies the hold that you want to view or remove.
To find valid values for this parameter, use this cmdlet with the Action parameter value GetHolds and look for the HoldId property in the output.
@@ -155,6 +143,7 @@ To find valid values for this parameter, use this cmdlet with the Action paramet
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -164,9 +153,6 @@ Accept wildcard characters: False
```
### -SharePointLocation
-
-> Applicable: Security & Compliance
-
The SharePointLocation parameter specifies the URL of the SharePoint site that contains the holds to view or remove.
This parameter is required when you use the value GetHolds or RemoveHold for the Action parameter.
@@ -175,6 +161,7 @@ This parameter is required when you use the value GetHolds or RemoveHold for the
Type: String
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -184,15 +171,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md b/exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md
rename to exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md
index 7292433a9c..858171d8c8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md
+++ b/exchange/exchange-ps/exchange/Invoke-MonitoringProbe.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/invoke-monitoringprobe
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Invoke-MonitoringProbe
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/invoke-monitoringprobe
-schema: 2.0.0
-title: Invoke-MonitoringProbe
+ms.reviewer:
---
# Invoke-MonitoringProbe
@@ -52,15 +51,13 @@ This example creates an Exchange ActiveSync monitoring probe on the EX1 server.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the identity of the monitoring probe to run.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -70,9 +67,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -86,6 +80,7 @@ You can't use this parameter to configure other Edge Transport servers remotely.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -Account
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Account parameter specifies the identity of the mailbox or user account that will run the monitoring probe.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,15 +106,13 @@ Accept wildcard characters: False
```
### -Endpoint
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Endpoint parameter specifies the name of the monitoring probe endpoint to connect to, for example, contoso.mail.com.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,15 +122,13 @@ Accept wildcard characters: False
```
### -ItemTargetExtension
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ItemTargetExtension parameter specifies cmdlet extension data that you can pass to the monitoring probe. The probe that runs on the server may require specific data for its execution. This data is presented to the probe on execution in an XML format.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -149,15 +138,13 @@ Accept wildcard characters: False
```
### -Password
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Password parameter specifies the password of the mailbox or user account that will run the monitoring probe.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -167,15 +154,13 @@ Accept wildcard characters: False
```
### -PropertyOverride
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PropertyOverride parameter specifies a property that you want to override, for example, to set the time-out value to be extended beyond the default value.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -185,15 +170,13 @@ Accept wildcard characters: False
```
### -SecondaryAccount
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SecondaryAccount parameter specifies the identity of the delegate mailbox or user account that will run the monitoring probe.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -203,15 +186,13 @@ Accept wildcard characters: False
```
### -SecondaryEndpoint
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SecondaryEndpoint parameter specifies the name of the secondary monitoring probe endpoint to connect to, for example, contoso.mail.fabrikam.com.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -221,15 +202,13 @@ Accept wildcard characters: False
```
### -SecondaryPassword
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SecondaryPassword parameter specifies the password of the delegate mailbox or user account that will run the monitoring probe.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -239,15 +218,13 @@ Accept wildcard characters: False
```
### -TimeOutSeconds
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TimeOutSeconds parameter specifies the monitoring operation time-out period.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md b/exchange/exchange-ps/exchange/Mount-Database.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Mount-Database.md
rename to exchange/exchange-ps/exchange/Mount-Database.md
index b9d8d46279..8d6dc5909a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md
+++ b/exchange/exchange-ps/exchange/Mount-Database.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/mount-database
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Mount-Database
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/mount-database
-schema: 2.0.0
-title: Mount-Database
+ms.reviewer:
---
# Mount-Database
@@ -47,9 +46,6 @@ This example mounts the database MyDatabase.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies mailbox database that you want to mount. You can use any value that uniquely identifies the database. For example:
- Name
@@ -60,6 +56,7 @@ The Identity parameter specifies mailbox database that you want to mount. You ca
Type: DatabaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -AcceptDataLoss
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AcceptDataLoss switch specifies that you accept the data loss caused by missing committed transaction log files without asking for confirmation. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -87,9 +82,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -99,6 +91,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -108,15 +101,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -126,9 +117,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
Use this switch to mount an empty database, or to override any errors or warnings that are encountered during the database mount.
@@ -137,6 +125,7 @@ Use this switch to mount an empty database, or to override any errors or warning
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -146,15 +135,13 @@ Accept wildcard characters: False
```
### -NewCapacity
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The NewCapacity switch specifies that you want to trigger the forced creation of a database only if all copies of the database don't have an .edb file. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -164,15 +151,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md b/exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md
rename to exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md
index 20923aba50..c59b2bf565 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md
+++ b/exchange/exchange-ps/exchange/Move-ActiveMailboxDatabase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/move-activemailboxdatabase
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Move-ActiveMailboxDatabase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/move-activemailboxdatabase
-schema: 2.0.0
-title: Move-ActiveMailboxDatabase
+ms.reviewer:
---
# Move-ActiveMailboxDatabase
@@ -135,9 +134,6 @@ This example performs a server switchover for the Mailbox server MBX1. All activ
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the mailbox database that you want to activate. You can use any value that uniquely identifies the database. For example:
- Name
@@ -150,6 +146,7 @@ You can't use this parameter with the Server parameter
Type: DatabaseIdParameter
Parameter Sets: Identity, SkipAllChecks
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -159,9 +156,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the server that you want to move all active mailbox databases from. You can use any value that uniquely identifies the server. For example:
- Name
@@ -175,6 +169,7 @@ You can't use this parameter with the Identity parameter
Type: MailboxServerIdParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -184,9 +179,6 @@ Accept wildcard characters: False
```
### -ActivatePreferredOnServer
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ActivatePreferredOnServer parameter specifies the Mailbox server where you want to activate all mailbox databases that have copies with an ActivationPreference value of 1. You can use any value that uniquely identifies the server. For example:
- Name
@@ -200,6 +192,7 @@ You can use this parameter as part of ending maintenance mode on a Mailbox serve
Type: MailboxServerIdParameter
Parameter Sets: ActivatePreferred
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -209,15 +202,13 @@ Accept wildcard characters: False
```
### -ActivateOnServer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ActivateOnServer parameter specifies the name of the Mailbox server on which the mailbox database copy should be activated.
```yaml
Type: MailboxServerIdParameter
Parameter Sets: Identity, Server
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: 2
@@ -227,9 +218,6 @@ Accept wildcard characters: False
```
### -SkipAllChecks
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The SkipAllChecks switch specifies whether to skip all checks. You don't need to specify a value with this switch.
This switch is equivalent to specifying all of the individual skip parameters that are available on this cmdlet.
@@ -240,6 +228,7 @@ You can only use this switch with the ActivateOnServer parameter.
Type: SwitchParameter
Parameter Sets: SkipAllChecks
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -249,9 +238,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -261,6 +247,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -270,15 +257,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -288,9 +273,6 @@ Accept wildcard characters: False
```
### -MountDialOverride
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. The following are possible values:
- None: When using this value, the currently configured auto database mount dial setting on the target server will be used.
@@ -303,6 +285,7 @@ The MountDialOverride parameter is used to override the auto database mount dial
Type: DatabaseMountDialOverride
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -312,15 +295,13 @@ Accept wildcard characters: False
```
### -MoveAllDatabasesOrNone
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The MoveAllDatabasesOrNone switch specifies whether to prevent any databases from moving if a single active database on the server can't be moved. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: Server
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -330,15 +311,13 @@ Accept wildcard characters: False
```
### -MoveComment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MoveComment parameter specifies an optional administrative reason for the move operation. The comment is recorded in the Event log.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -348,9 +327,6 @@ Accept wildcard characters: False
```
### -SkipActiveCopyChecks
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SkipActiveCopyChecks switch specifies whether to skip checking the current active copy to see if it's currently a seeding source for any passive databases. You don't need to specify a value with this switch.
**Note**: When you use this switch, you can move a database that's currently a seeding source, which cancels the seed operation.
@@ -359,6 +335,7 @@ The SkipActiveCopyChecks switch specifies whether to skip checking the current a
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -368,9 +345,6 @@ Accept wildcard characters: False
```
### -SkipClientExperienceChecks
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SkipClientExperienceChecks switch specifies whether to skip the search catalog (content index) state check to see if the search catalog is healthy and up to date. You don't need to specify a value with this switch.
If the search catalog for the database copy you're activating is in an unhealthy or unusable state and you use this parameter to skip the search catalog health check and activate the database copy, you will need to either re-crawl or reseed the search catalog.
@@ -379,6 +353,7 @@ If the search catalog for the database copy you're activating is in an unhealthy
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -388,15 +363,13 @@ Accept wildcard characters: False
```
### -SkipCpuChecks
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The SkipCpuChecks switch specifies whether to skip the high CPU utilization checks. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -406,9 +379,6 @@ Accept wildcard characters: False
```
### -SkipHealthChecks
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SkipHealthChecks switch specifies whether to bypass passive copy health checks. You don't need to specify a value with this switch.
When you use this switch, you can move the active copy to a database copy that's in the Failed state. You should only use this switch if the initial attempt to move the active database has failed. This is because the SkipHealthChecks switch performs additional validation to ensure that the log files are consistent, which can take a considerable amount of time.
@@ -417,6 +387,7 @@ When you use this switch, you can move the active copy to a database copy that's
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -426,15 +397,13 @@ Accept wildcard characters: False
```
### -SkipLagChecks
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SkipLagChecks switch specifies whether to allow a copy to be activated that has replay and copy queues outside of the configured criteria. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -444,9 +413,6 @@ Accept wildcard characters: False
```
### -SkipMaximumActiveDatabasesChecks
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SkipMaximumActiveDatabasesChecks switch specifies whether to skip checking the value of MaximumPreferredActiveDatabases during the best copy and server selection (BCSS) process. You don't need to specify a value with this switch.
Any configured value for MaximumActiveDatabases will still be honored during the BCSS process and by the Information Store.
@@ -455,6 +421,7 @@ Any configured value for MaximumActiveDatabases will still be honored during the
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -464,15 +431,13 @@ Accept wildcard characters: False
```
### -SkipMoveSuppressionChecks
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The SkipMoveSuppressionChecks switch specifies whether to skip the move suppression checks. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -482,15 +447,13 @@ Accept wildcard characters: False
```
### -TerminateOnWarning
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TerminateOnWarning switch specifies whether to terminate the task and output an error message if a warning is encountered during the switchover operation. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -500,15 +463,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md b/exchange/exchange-ps/exchange/Move-AddressList.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md
rename to exchange/exchange-ps/exchange/Move-AddressList.md
index 8a33bcacdd..d2c70381c6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md
+++ b/exchange/exchange-ps/exchange/Move-AddressList.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/move-addresslist
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Move-AddressList
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/move-addresslist
-schema: 2.0.0
-title: Move-AddressList
+ms.reviewer:
---
# Move-AddressList
@@ -44,9 +43,6 @@ This example moves the address list with GUID c3fffd8e-026b-41b9-88c4-8c21697ac8
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the address list that you want to move. You can use any value that uniquely identifies the address list. For example:
- Name
@@ -58,6 +54,7 @@ The Identity parameter specifies the address list that you want to move. You can
Type: AddressListIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -67,9 +64,6 @@ Accept wildcard characters: False
```
### -Target
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Container parameter specifies where to move the address list. Valid input for this parameter is under the root "\\" (also known as All Address Lists) or under an existing address list. You can use any value that uniquely identifies the address list. For example:
- Name
@@ -81,6 +75,7 @@ The Container parameter specifies where to move the address list. Valid input fo
Type: AddressListIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -90,9 +85,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -104,6 +96,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,15 +106,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,15 +122,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md b/exchange/exchange-ps/exchange/Move-DatabasePath.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md
rename to exchange/exchange-ps/exchange/Move-DatabasePath.md
index 3a1b166654..88ab1bea84 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md
+++ b/exchange/exchange-ps/exchange/Move-DatabasePath.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/move-databasepath
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Move-DatabasePath
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/move-databasepath
-schema: 2.0.0
-title: Move-DatabasePath
+ms.reviewer:
---
# Move-DatabasePath
@@ -55,9 +54,6 @@ This example sets a new path for the mailbox database specified by the mailbox d
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the database that you want to move. You can use any value that uniquely identifies the database. For example:
- Name
@@ -68,6 +64,7 @@ The Identity parameter specifies the database that you want to move. You can use
Type: DatabaseIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -77,9 +74,6 @@ Accept wildcard characters: False
```
### -ConfigurationOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ConfigurationOnly switch specifies whether to change the configuration of the database without moving any files. You don't need to specify a value with this switch.
If you don't use this switch, the configuration of the database changes and the files are moved.
@@ -88,6 +82,7 @@ If you don't use this switch, the configuration of the database changes and the
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -97,9 +92,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -111,6 +103,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -120,15 +113,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -138,15 +129,13 @@ Accept wildcard characters: False
```
### -EDBFilePath
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The EdbFilePath parameter specifies a new file path for the database. All current database files are moved to this location. The default location is `%ExchangeInstallPath%Mailbox\LocalCopies\MBDatabase.edb`. This file path can't be the same as the path for the backup copy of the database.
```yaml
Type: EdbFilePath
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -156,9 +145,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -167,6 +153,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -176,15 +163,13 @@ Accept wildcard characters: False
```
### -LogFolderPath
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LogFolderPath parameter specifies the folder where log files are stored.
```yaml
Type: NonRootLocalLongFullPath
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -194,15 +179,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -212,15 +195,13 @@ Accept wildcard characters: False
```
### -EDBFilePath
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The EdbFilePath parameter specifies a new file path for the database. All current database files are moved to this location. The default location is ``%ExchangeInstallPath%Mailbox\LocalCopies\MBDatabase.edb`. This file path can't be the same as the path for the backup copy of the database.
```yaml
Type: EdbFilePath
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md b/exchange/exchange-ps/exchange/Move-OfflineAddressBook.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md
rename to exchange/exchange-ps/exchange/Move-OfflineAddressBook.md
index c66383eeb8..52e6b27ad3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md
+++ b/exchange/exchange-ps/exchange/Move-OfflineAddressBook.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/move-offlineaddressbook
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: Move-OfflineAddressBook
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/move-offlineaddressbook
-schema: 2.0.0
-title: Move-OfflineAddressBook
+ms.reviewer:
---
# Move-OfflineAddressBook
@@ -45,9 +44,6 @@ This example moves OAB generation in Exchange 2010 to the server named Server1.
## PARAMETERS
### -Identity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Identity parameter specifies the GUID, distinguished name (DN), or OAB name that represents a specific OAB. You can also include the path by using the format Server\\OfflineAddressBookName.
You can omit the parameter label so that only the OAB name or GUID is supplied.
@@ -56,6 +52,7 @@ You can omit the parameter label so that only the OAB name or GUID is supplied.
Type: OfflineAddressBookIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -79,6 +73,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -88,15 +83,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -106,9 +99,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -122,6 +112,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,15 +122,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md
rename to exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md
index 05e0967f85..85953675d6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md
+++ b/exchange/exchange-ps/exchange/New-ATPBuiltInProtectionRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-atpbuiltinprotectionrule
applicable: Exchange Online
+title: New-ATPBuiltInProtectionRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-atpbuiltinprotectionrule
-schema: 2.0.0
-title: New-ATPBuiltInProtectionRule
+ms.reviewer:
---
# New-ATPBuiltInProtectionRule
@@ -55,9 +54,6 @@ This cmdlet creates the rule for the Built-in protection preset security policy.
## PARAMETERS
### -SafeAttachmentPolicy
-
-> Applicable: Exchange Online
-
The SafeAttachmentPolicy parameter specifies the Safe Attachments policy that's associated with the Built-in preset security policy. Use the following command to identify the policy: `Get-SafeAttachmentPolicy | Where-Object -Property IsBuiltInProtection -eq -Value "True"`.
The name of the default Safe Attachments policy that's used for the Built-in protection preset security policy is Built-In Protection Policy.
@@ -66,6 +62,7 @@ The name of the default Safe Attachments policy that's used for the Built-in pro
Type: SafeAttachmentPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -SafeLinksPolicy
-
-> Applicable: Exchange Online
-
The SafeLinksPolicy parameter specifies the Safe Links policy that's associated with the Built-in preset security policy. Use the following command to identify the policy: `Get-SafeLinksPolicy | Where-Object -Property IsBuiltInProtection -eq -Value "True"`.
The name of the default Safe Links policy that's used for the Built-in protection preset security policy is Built-In Protection Policy.
@@ -86,6 +80,7 @@ The name of the default Safe Links policy that's used for the Built-in protectio
Type: SafeLinksPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -Comments
-
-> Applicable: Exchange Online
-
The Comments parameter specifies informative comments for the rule, such as what the rule is used for or how it has changed over time. The length of the comment can't exceed 1024 characters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -113,9 +106,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -125,6 +115,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -134,15 +125,13 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientDomainIs
-
-> Applicable: Exchange Online
-
The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -152,9 +141,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentTo
-
-> Applicable: Exchange Online
-
The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -170,6 +156,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -179,9 +166,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentToMemberOf
-
-> Applicable: Exchange Online
-
The ExceptIfSentToMemberOf parameter specifies an exception that looks for messages sent to members of groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -199,6 +183,7 @@ If you remove the group after you create the rule, no exception is made for mess
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -208,9 +193,6 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Online
-
The Name parameter specifies a unique name for the rule. The maximum length is 64 characters.
The name of the only rule is ATP Built-In Protection Rule.
@@ -219,6 +201,7 @@ The name of the only rule is ATP Built-In Protection Rule.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -228,15 +211,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md
similarity index 96%
rename from exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md
index 5d3eb131cf..9397716f14 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/New-ATPProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-atpprotectionpolicyrule
applicable: Exchange Online
+title: New-ATPProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-atpprotectionpolicyrule
-schema: 2.0.0
-title: New-ATPProtectionPolicyRule
+ms.reviewer:
---
# New-ATPProtectionPolicyRule
@@ -59,9 +58,6 @@ This example creates the rule for the Standard preset security policy. No restri
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online
-
The Name parameter specifies a unique name for the rule. The maximum length is 64 characters.
By default, the rules are named Standard Preset Security Policy or Strict Preset Security Policy. Since you don't need to create rules other than those used by the Standard preset security policy or the Strict preset security policy, we highly recommend that you use the default rule names for clarity and consistency.
@@ -70,6 +66,7 @@ By default, the rules are named Standard Preset Security Policy or Strict Preset
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 0
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -SafeAttachmentPolicy
-
-> Applicable: Exchange Online
-
The SafeAttachmentPolicy parameter specifies the existing Safe Attachments policy that's associated with the preset security policy.
If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy will be one of the following values:
@@ -95,6 +89,7 @@ You can find the Safe Attachments policy that's used by the Standard or Strict p
Type: SafeAttachmentPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -104,9 +99,6 @@ Accept wildcard characters: False
```
### -SafeLinksPolicy
-
-> Applicable: Exchange Online
-
The SafeLinksPolicy parameter specifies the existing Safe Links policy that's associated with the preset security policy.
If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy will be one of the following values:
@@ -120,6 +112,7 @@ You can find the Safe Links policy that's used by the Standard or Strict preset
Type: SafeLinksPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -129,15 +122,13 @@ Accept wildcard characters: False
```
### -Comments
-
-> Applicable: Exchange Online
-
The Comments parameter specifies informative comments for the rule, such as what the rule is used for or how it has changed over time. The length of the comment can't exceed 1024 characters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -147,9 +138,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -159,6 +147,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -168,9 +157,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online
-
The Enabled parameter specifies whether the rule is enabled. Valid values are:
- $true: The rule is enabled. The State value of the rule is Enabled. This is the default value.
@@ -185,6 +171,7 @@ After you create the rule, you turn on or turn off the preset security policy us
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -194,15 +181,13 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientDomainIs
-
-> Applicable: Exchange Online
-
The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -212,9 +197,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentTo
-
-> Applicable: Exchange Online
-
The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -230,6 +212,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -239,9 +222,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentToMemberOf
-
-> Applicable: Exchange Online,
-
The ExceptIfSentToMemberOf parameter specifies an exception that looks for messages sent to members of groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -259,6 +239,7 @@ If you remove the group after you create the rule, no exception is made for mess
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online,
Required: False
Position: Named
@@ -268,9 +249,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Online
-
The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
The default value for the rule that's associated with the Strict preset security policy is 0, and the default value for the rule that's associated with the Standard preset security policy is 1.
@@ -281,6 +259,7 @@ When you create the policy, you must use the default value.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -290,15 +269,13 @@ Accept wildcard characters: False
```
### -RecipientDomainIs
-
-> Applicable: Exchange Online
-
The RecipientDomainIs parameter specifies a condition that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -308,9 +285,6 @@ Accept wildcard characters: False
```
### -SentTo
-
-> Applicable: Exchange Online
-
The SentTo parameter specifies a condition that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -326,6 +300,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -335,9 +310,6 @@ Accept wildcard characters: False
```
### -SentToMemberOf
-
-> Applicable: Exchange Online
-
The SentToMemberOf parameter specifies a condition that looks for messages sent to members of distribution groups, dynamic distribution groups, or mail-enabled security groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -355,6 +327,7 @@ If you remove the group after you create the rule, no action is taken on message
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -364,15 +337,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md b/exchange/exchange-ps/exchange/New-AcceptedDomain.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md
rename to exchange/exchange-ps/exchange/New-AcceptedDomain.md
index 7b60a5bca3..157ffaec81 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md
+++ b/exchange/exchange-ps/exchange/New-AcceptedDomain.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-accepteddomain
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-AcceptedDomain
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-accepteddomain
-schema: 2.0.0
-title: New-AcceptedDomain
+ms.reviewer:
---
# New-AcceptedDomain
@@ -45,15 +44,13 @@ This example creates the new authoritative accepted domain Contoso.
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies a unique name for the accepted domain object.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -63,9 +60,6 @@ Accept wildcard characters: False
```
### -DomainName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainName parameter specifies the SMTP domain that you want to establish as an accepted domain. Valid input for the DomainName parameter is an SMTP domain. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: \*.contoso.com.
However, you can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. The domain name string may not contain more than 256 characters.
@@ -74,6 +68,7 @@ However, you can't embed a wildcard character, as shown in the following example
Type: SmtpDomainWithSubdomains
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -83,9 +78,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -95,6 +87,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -104,9 +97,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -115,6 +105,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -124,9 +115,6 @@ Accept wildcard characters: False
```
### -DomainType
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainType parameter specifies the type of accepted domain that you want to configure. Valid values are Authoritative, InternalRelay or ExternalRelay. You must set at least one value.
In an authoritative domain, messages are delivered to a recipient that has a domain account in your Exchange organization. In an internal relay domain, messages are relayed to a server outside your Exchange organization, but still under the authority of your company or IT department. Use the internal relay domain if you want to treat the messages to this domain as internal messages. In an external relay domain, messages are relayed to an email server, outside your organization, which you don't control.
@@ -137,6 +125,7 @@ The default value is Authoritative.
Type: AcceptedDomainType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -146,15 +135,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md
rename to exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md
index 81e0237759..136f962987 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/exchange/New-ActiveSyncDeviceAccessRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-activesyncdeviceaccessrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-ActiveSyncDeviceAccessRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-activesyncdeviceaccessrule
-schema: 2.0.0
-title: New-ActiveSyncDeviceAccessRule
+ms.reviewer:
---
# New-ActiveSyncDeviceAccessRule
@@ -53,15 +52,13 @@ This example creates a device access rule that uses the UserAgent characteristic
## PARAMETERS
### -AccessLevel
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AccessLevel parameter specifies the access level of devices that are defined by the rule. Valid values for this parameter are Allow, Block and Quarantine.
```yaml
Type: DeviceAccessLevel
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -Characteristic
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Characteristic parameter specifies the device characteristic or category that's used by the rule. Valid values for this parameter are:
- DeviceModel
@@ -86,6 +80,7 @@ The Characteristic parameter specifies the device characteristic or category tha
Type: DeviceAccessCharacteristic
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -95,9 +90,6 @@ Accept wildcard characters: False
```
### -QueryString
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The QueryString parameter specifies the device identifier that's used by the rule. This parameter uses a text value that's used with Characteristic parameter value to define the device. Wildcards or partial matches aren't allowed.
You can use the Get-MobileDevice cmdlet to find the text values that you can use with the QueryString parameter. For example: Get-MobileDevice | Format-List DeviceOS,DeviceModel,DeviceType.
@@ -106,6 +98,7 @@ You can use the Get-MobileDevice cmdlet to find the text values that you can use
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -127,6 +117,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -136,9 +127,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -147,6 +135,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -156,15 +145,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md
similarity index 80%
rename from exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md
rename to exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md
index 9d14e34c18..2480ceb160 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/exchange/New-ActiveSyncMailboxPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-activesyncmailboxpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-ActiveSyncMailboxPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-activesyncmailboxpolicy
-schema: 2.0.0
-title: New-ActiveSyncMailboxPolicy
+ms.reviewer:
---
# New-ActiveSyncMailboxPolicy
@@ -117,15 +116,13 @@ This example creates the Mobile Device mailbox policy Contoso that has several p
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies the name of the policy.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -135,9 +132,6 @@ Accept wildcard characters: False
```
### -AllowApplePushNotifications
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The AllowApplePushNotifications parameter specifies whether push notifications are allowed for Apple mobile devices. The default value is $true.
@@ -146,6 +140,7 @@ The AllowApplePushNotifications parameter specifies whether push notifications a
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -155,15 +150,13 @@ Accept wildcard characters: False
```
### -AllowBluetooth
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowBluetooth parameter specifies whether the Bluetooth capabilities of the mobile phone are allowed. The available options are Disable, HandsfreeOnly, and Allow. The default value is Allow.
```yaml
Type: BluetoothType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -173,15 +166,13 @@ Accept wildcard characters: False
```
### -AllowBrowser
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowBrowser parameter specifies whether Microsoft Pocket Internet Explorer is allowed on the mobile phone. The default value is $true. This parameter doesn't affect non-Microsoft browsers.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -191,15 +182,13 @@ Accept wildcard characters: False
```
### -AllowCamera
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowCamera parameter specifies whether the mobile phone's camera is allowed. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -209,15 +198,13 @@ Accept wildcard characters: False
```
### -AllowConsumerEmail
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowConsumerEmail parameter specifies whether the mobile phone user can configure a personal email account on the device. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -227,15 +214,13 @@ Accept wildcard characters: False
```
### -AllowDesktopSync
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowDesktopSync parameter specifies whether the mobile phone can synchronize with a desktop computer through a cable. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -245,15 +230,13 @@ Accept wildcard characters: False
```
### -AllowExternalDeviceManagement
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowExternalDeviceManagement parameter specifies whether an external device management program is allowed to manage the device.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -263,15 +246,13 @@ Accept wildcard characters: False
```
### -AllowHTMLEmail
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowHTMLEmail parameter specifies whether HTML email is enabled on the device. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -281,15 +262,13 @@ Accept wildcard characters: False
```
### -AllowInternetSharing
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowInternetSharing parameter specifies whether the mobile phone can be used as a modem to connect a computer to the Internet. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -299,15 +278,13 @@ Accept wildcard characters: False
```
### -AllowIrDA
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowIrDA parameter specifies whether infrared connections are allowed to the mobile phone. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -317,15 +294,13 @@ Accept wildcard characters: False
```
### -AllowMobileOTAUpdate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowMobileOTAUpdate parameter specifies whether certain updates are seen by devices that implemented support for this restricting functionality. Further control can be specified via the MobileOTAUpdateMode parameter.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -335,15 +310,13 @@ Accept wildcard characters: False
```
### -AllowNonProvisionableDevices
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
When set to $true, the AllowNonProvisionableDevices parameter enables all devices to synchronize with the computer running Exchange, regardless of whether the device can enforce all the specific settings established in the Mobile Device mailbox policy. This also includes devices managed by a separate device management system. When set to $false, this parameter blocks these devices that aren't provisioned from synchronizing with the server running Exchange. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -353,15 +326,13 @@ Accept wildcard characters: False
```
### -AllowPOPIMAPEmail
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowPOPIMAPEmail parameter specifies whether the user can configure a POP3 or IMAP4 email account on the device. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -371,15 +342,13 @@ Accept wildcard characters: False
```
### -AllowRemoteDesktop
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowRemoteDesktop parameter specifies whether the mobile phone can initiate a remote desktop connection. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -389,15 +358,13 @@ Accept wildcard characters: False
```
### -AllowSimpleDevicePassword
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowSimpleDevicePassword parameter specifies whether a simple device password is allowed. A simple device password is a password that has a specific pattern, such as 1111 or 1234. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -407,15 +374,13 @@ Accept wildcard characters: False
```
### -AllowSMIMEEncryptionAlgorithmNegotiation
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowSMIMEEncryptionAlgorithmNegotiation parameter specifies whether the messaging application on the device can negotiate the encryption algorithm in case a recipient's certificate doesn't support the specified encryption algorithm.
```yaml
Type: SMIMEEncryptionAlgorithmNegotiationType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -425,15 +390,13 @@ Accept wildcard characters: False
```
### -AllowSMIMESoftCerts
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowSMIMESoftCerts parameter specifies whether S/MIME software certificates are allowed. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -443,15 +406,13 @@ Accept wildcard characters: False
```
### -AllowStorageCard
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowStorageCard parameter specifies whether the device can access information stored on a storage card. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -461,15 +422,13 @@ Accept wildcard characters: False
```
### -AllowTextMessaging
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowTextMessaging parameter specifies whether text messaging is allowed from the device. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -479,15 +438,13 @@ Accept wildcard characters: False
```
### -AllowUnsignedApplications
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowUnsignedApplications parameter specifies whether unsigned applications can be installed on the device. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -497,15 +454,13 @@ Accept wildcard characters: False
```
### -AllowUnsignedInstallationPackages
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowUnsignedInstallationPackages parameter specifies whether unsigned installation packages can be run on the device. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -515,15 +470,13 @@ Accept wildcard characters: False
```
### -AllowWiFi
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowWiFi parameter specifies whether wireless Internet access is allowed on the device. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -533,15 +486,13 @@ Accept wildcard characters: False
```
### -AlphanumericDevicePasswordRequired
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AlphanumericDevicePasswordRequired parameter specifies whether the device password must be alphanumeric. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -551,15 +502,13 @@ Accept wildcard characters: False
```
### -ApprovedApplicationList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ApprovedApplicationList parameter specifies a list of approved applications for the device.
```yaml
Type: ApprovedApplicationCollection
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -569,15 +518,13 @@ Accept wildcard characters: False
```
### -AttachmentsEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AttachmentsEnabled parameter specifies whether the user can download attachments. When set to $false, the user is blocked from downloading attachments. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -587,9 +534,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -599,6 +543,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -608,15 +553,13 @@ Accept wildcard characters: False
```
### -DeviceEncryptionEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DeviceEncryptionEnabled parameter, when set to $true, enables device encryption on the mobile phone. The default value is $false. Currently, only the storage card can be encrypted on devices running Windows Mobile 6.0 or later. We recommend that you don't use this setting and use the RequireStorageCardEncryption parameter instead.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -626,15 +569,13 @@ Accept wildcard characters: False
```
### -DevicePasswordEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
When set to $true, the DevicePasswordEnabled parameter specifies that the user set a password for the device. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -644,15 +585,13 @@ Accept wildcard characters: False
```
### -DevicePasswordExpiration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DevicePasswordExpiration parameter specifies the length of time, in days, that a password can be used. After this length of time, a new password must be created. The format of the parameter is dd.hh.mm:ss, for example, 24.00:00 = 24 hours.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -662,15 +601,13 @@ Accept wildcard characters: False
```
### -DevicePasswordHistory
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DevicePasswordHistory parameter specifies the number of previously used passwords to store. When a user creates a password, the user can't reuse a stored password that was previously used.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -680,15 +617,13 @@ Accept wildcard characters: False
```
### -DevicePolicyRefreshInterval
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DevicePolicyRefreshInterval parameter specifies how often the policy is sent from the server to the mobile phone
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -698,9 +633,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -709,6 +641,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -718,15 +651,13 @@ Accept wildcard characters: False
```
### -IrmEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IrmEnabled parameter specifies whether Information Rights Management (IRM) is enabled for the mailbox policy.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -736,15 +667,13 @@ Accept wildcard characters: False
```
### -IsDefault
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IsDefault parameter specifies whether this policy is the default Mobile Device mailbox policy. The default value is $false. If another policy is currently set as the default, setting this parameter replaces the old default policy with this policy.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -754,15 +683,13 @@ Accept wildcard characters: False
```
### -IsDefaultPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IsDefault parameter specifies whether this policy is the default Mobile Device mailbox policy. The default value is $false. If another policy is currently set as the default, setting this parameter replaces the old default policy with this policy.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -772,15 +699,13 @@ Accept wildcard characters: False
```
### -MaxAttachmentSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MaxAttachmentSize parameter specifies the maximum size of attachments that can be downloaded to the mobile phone. The default value is Unlimited.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -790,9 +715,6 @@ Accept wildcard characters: False
```
### -MaxCalendarAgeFilter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MaxCalendarAgeFilter parameter specifies the maximum range of calendar days that can be synchronized to the device. Valid values are:
- All
@@ -805,6 +727,7 @@ The MaxCalendarAgeFilter parameter specifies the maximum range of calendar days
Type: CalendarAgeFilterType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -814,15 +737,13 @@ Accept wildcard characters: False
```
### -MaxDevicePasswordFailedAttempts
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MaxDevicePasswordFailedAttempts parameter specifies the number of attempts a user can make to enter the correct password for the device. You can enter any number from 4 through 16. The default value is 8.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -832,9 +753,6 @@ Accept wildcard characters: False
```
### -MaxEmailAgeFilter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MaxEmailAgeFilter parameter specifies the maximum number of days of email items to synchronize to the device.
Possible values are:
@@ -852,6 +770,7 @@ Possible values are:
Type: EmailAgeFilterType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -861,15 +780,13 @@ Accept wildcard characters: False
```
### -MaxEmailBodyTruncationSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MaxEmailBodyTruncationSize parameter specifies the maximum size at which email messages are truncated when synchronized to the device. The value is specified in kilobytes (KB).
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -879,15 +796,13 @@ Accept wildcard characters: False
```
### -MaxEmailHTMLBodyTruncationSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MaxEmailHTMLBodyTruncationSize parameter specifies the maximum size at which HTML-formatted email messages are synchronized to the device. The value is specified in KB.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -897,15 +812,13 @@ Accept wildcard characters: False
```
### -MaxInactivityTimeDeviceLock
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MaxInactivityTimeDeviceLock parameter specifies the length of time that the device can be inactive before the password is required to reactivate the device. You can enter any interval between 30 seconds and 1 hour. The default value is 15 minutes. The format of the parameter is hh.mm:ss, for example, 15:00 = 15 minutes.
```yaml
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -915,15 +828,13 @@ Accept wildcard characters: False
```
### -MinDevicePasswordComplexCharacters
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MinDevicePasswordComplexCharacters parameter specifies the minimum number of complex characters required in a device password. A complex character isn't a letter.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -933,15 +844,13 @@ Accept wildcard characters: False
```
### -MinDevicePasswordLength
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MinDevicePasswordLength parameter specifies the minimum number of characters in the device password. You can enter any number from 1 through 16. The maximum length a password can be is 16 characters. The default value is 4.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -951,15 +860,13 @@ Accept wildcard characters: False
```
### -PasswordRecoveryEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The PasswordRecoveryEnabled parameter specifies whether you can store the recovery password for the device on an Exchange server. When set to $true, you can store the recovery password for the device on an Exchange server. The default value is $false. The recovery password can be viewed from either Outlook on the web or the Exchange admin center.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -969,15 +876,13 @@ Accept wildcard characters: False
```
### -RequireDeviceEncryption
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequireDeviceEncryption parameter specifies whether encryption is required on the device. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -987,15 +892,13 @@ Accept wildcard characters: False
```
### -RequireEncryptedSMIMEMessages
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequireEncryptedSMIMEMessages parameter specifies whether you must encrypt S/MIME messages. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1005,15 +908,13 @@ Accept wildcard characters: False
```
### -RequireEncryptionSMIMEAlgorithm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequireEncryptionSMIMEAlgorithm parameter specifies what required algorithm must be used when encrypting a message.
```yaml
Type: EncryptionSMIMEAlgorithmType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1023,15 +924,13 @@ Accept wildcard characters: False
```
### -RequireManualSyncWhenRoaming
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequireManualSyncWhenRoaming parameter specifies whether the device must synchronize manually while roaming. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1041,15 +940,13 @@ Accept wildcard characters: False
```
### -RequireSignedSMIMEAlgorithm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequireSignedSMIMEAlgorithm parameter specifies what required algorithm must be used when signing a message.
```yaml
Type: SignedSMIMEAlgorithmType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1059,15 +956,13 @@ Accept wildcard characters: False
```
### -RequireSignedSMIMEMessages
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequireSignedSMIMEMessages parameter specifies whether the device must send signed S/MIME messages.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1077,15 +972,13 @@ Accept wildcard characters: False
```
### -RequireStorageCardEncryption
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RequireStorageCardEncryption parameter specifies whether encryption of a storage card is required. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1095,15 +988,13 @@ Accept wildcard characters: False
```
### -UnapprovedInROMApplicationList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The UnapprovedInROMApplicationList parameter specifies a list of applications that can't be run in ROM.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1113,15 +1004,13 @@ Accept wildcard characters: False
```
### -UNCAccessEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The UNCAccessEnabled parameter specifies whether access to Microsoft Windows file shares is enabled. Access to specific shares is configured on the Microsoft Exchange ActiveSync virtual directory.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1131,15 +1020,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1149,15 +1036,13 @@ Accept wildcard characters: False
```
### -WSSAccessEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WSSAccessEnabled parameter specifies whether access to Microsoft Windows SharePoint Services is enabled. Access to specific shares is configured on the Exchange ActiveSync virtual directory.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md
rename to exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md
index 7580c9fdba..03c846da01 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/New-ActiveSyncVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-activesyncvirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-ActiveSyncVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-activesyncvirtualdirectory
-schema: 2.0.0
-title: New-ActiveSyncVirtualDirectory
+ms.reviewer:
---
# New-ActiveSyncVirtualDirectory
@@ -73,15 +72,13 @@ This example creates an Exchange ActiveSync virtual directory for the company Fo
## PARAMETERS
### -ApplicationRoot
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ApplicationRoot parameter specifies the metabase path of the virtual directory. By default, this path is the same as the website in which the virtual directory is created.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -91,15 +88,13 @@ Accept wildcard characters: False
```
### -AppPoolId
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AppPoolId parameter specifies the IIS application pool in which the virtual directory runs. We recommend that you leave this parameter at its default setting.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -109,9 +104,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -121,6 +113,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,15 +123,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -148,9 +139,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionFlags
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
- None: This is the default setting.
@@ -163,6 +151,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -172,9 +161,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionSPNList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
- $null: This is the default value.
@@ -184,6 +170,7 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -193,9 +180,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionTokenChecking
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
@@ -208,6 +192,7 @@ The ExtendedProtectionTokenChecking parameter defines how you want to use Extend
Type: ExtendedProtectionTokenCheckingMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -217,9 +202,6 @@ Accept wildcard characters: False
```
### -ExternalAuthenticationMethods
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExternalAuthenticationMethods parameter restricts the authentication methods that can be used to connect to the virtual directory from outside the firewall. Valid values are:
- Adfs
@@ -251,6 +233,7 @@ The default value is blank ($null), which means all available authentication met
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -260,15 +243,13 @@ Accept wildcard characters: False
```
### -ExternalUrl
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
```yaml
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -278,15 +259,13 @@ Accept wildcard characters: False
```
### -InstallProxySubDirectory
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The InstallProxySubDirectory parameter was used to create an subdirectory that was required for proxying ActiveSync connections with Exchange 2007.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -296,9 +275,6 @@ Accept wildcard characters: False
```
### -InternalAuthenticationMethods
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The InternalAuthenticationMethods parameter restricts the authentication methods that can be used to connect to the virtual directory from inside the firewall. Valid values are:
- Adfs
@@ -330,6 +306,7 @@ The default value is blank ($null), which means all available authentication met
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -339,15 +316,13 @@ Accept wildcard characters: False
```
### -InternalUrl
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
```yaml
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -357,15 +332,13 @@ Accept wildcard characters: False
```
### -Path
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Path parameter specifies the file system path of the virtual directory. We recommend using this parameter only when you need to use a custom location for the virtual directory files. The default value is blank ($null), which indicates the default location is used.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -375,9 +348,6 @@ Accept wildcard characters: False
```
### -Role
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Role parameter species the configuration for the virtual directory. Valid values are:
- ClientAccess: Configure the virtual directory for the Client Access (frontend) services on the Mailbox server.
@@ -389,6 +359,7 @@ Client connections are proxied from the Client Access services to the backend se
Type: VirtualDirectoryRole
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -398,9 +369,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -412,6 +380,7 @@ The Server parameter specifies the Exchange server that hosts the virtual direct
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -421,15 +390,13 @@ Accept wildcard characters: False
```
### -WebSiteName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WebSiteName parameter specifies the name of the IIS website under which the virtual directory is created. You don't need to use this parameter to create the virtual directory under the default website.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -439,15 +406,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AdaptiveScope.md b/exchange/exchange-ps/exchange/New-AdaptiveScope.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-AdaptiveScope.md
rename to exchange/exchange-ps/exchange/New-AdaptiveScope.md
index 793c5eec68..88433a9deb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AdaptiveScope.md
+++ b/exchange/exchange-ps/exchange/New-AdaptiveScope.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-adaptivescope
applicable: Security & Compliance
+title: New-AdaptiveScope
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-adaptivescope
-schema: 2.0.0
-title: New-AdaptiveScope
+ms.reviewer:
---
# New-AdaptiveScope
@@ -57,15 +56,13 @@ This example create an adaptive query scope named Project X with the following d
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the adaptive scope. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -FilterConditions
-
-> Applicable: Security & Compliance
-
The FilterConditions parameter specifies the conditions that are included in the dynamic boundary. Valid syntax and values depend of the value of the LocationType parameter:
- User or Group: Active Directory attributes. For example, for the condition "('Country or region' equals 'US' or 'Canada') and 'Department' equals 'Finance'", use the following syntax: `@{"Conditions" = @(@{"Conditions" = @(@{"Value" = "US"; "Operator" = "Equals"; "Name" = "CountryOrRegion"}, @{"Value" = "Canada"; "Operator" = "Equals"; "Name" = "CountryOrRegion"}); "Conjunction" = "Or"}, @{"Value" = "Finance"; "Operator" = "Equals"; "Name" = "Department"}); "Conjunction" = "And"}`
@@ -89,6 +83,7 @@ You can't use this parameter with the RawQuery parameter.
Type: PswsHashtable
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -98,9 +93,6 @@ Accept wildcard characters: False
```
### -LocationType
-
-> Applicable: Security & Compliance
-
The LocationType parameter specifies the location where the adaptive scope filter is defined. Valid values are:
- User
@@ -112,6 +104,7 @@ Type: DynamicBoundaryLocationType
Parameter Sets: (All)
Aliases:
Accepted values: Unknown, User, Group, Site
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -121,9 +114,6 @@ Accept wildcard characters: False
```
### -RawQuery
-
-> Applicable: Security & Compliance
-
The RawQuery parameter switches the scope to advanced query mode. You use OPATH filter syntax for advanced query mode.
You can't use this parameter with the FilterConditions parameter.
@@ -132,6 +122,7 @@ You can't use this parameter with the FilterConditions parameter.
Type: String
Parameter Sets: AdaptiveScopeRawQuery
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -141,15 +132,13 @@ Accept wildcard characters: False
```
### -AdministrativeUnit
-
-> Applicable: Security & Compliance
-
{{ Fill AdministrativeUnit Description }}
```yaml
Type: Guid
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -159,15 +148,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md b/exchange/exchange-ps/exchange/New-AddressBookPolicy.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md
rename to exchange/exchange-ps/exchange/New-AddressBookPolicy.md
index 0549ac3edd..4bade089b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md
+++ b/exchange/exchange-ps/exchange/New-AddressBookPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-addressbookpolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-AddressBookPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-addressbookpolicy
-schema: 2.0.0
-title: New-AddressBookPolicy
+ms.reviewer:
---
# New-AddressBookPolicy
@@ -52,15 +51,13 @@ This example creates an address book policy with the following settings:
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies the name of the address book policy.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -70,15 +67,13 @@ Accept wildcard characters: False
```
### -AddressLists
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AddressLists parameter specifies the address lists that will be used by mailbox users who are assigned this address book policy. This parameter accepts multiple values, which should be separated by a comma. For example, "\\Mr. Munson's Class","Mrs. McKay's Class","Mrs. Count's Class".
```yaml
Type: AddressListIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -88,15 +83,13 @@ Accept wildcard characters: False
```
### -GlobalAddressList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The GlobalAddressList parameter specifies the identity of the GAL that will be used by mailbox users who are assigned this address book policy. You can specify only one GAL for each address book policy.
```yaml
Type: GlobalAddressListIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -106,15 +99,13 @@ Accept wildcard characters: False
```
### -OfflineAddressBook
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OfflineAddressBook parameter specifies the identity of the OAB that will be used by mailbox users who are assigned this address book policy. You can specify only one OAB for each address book policy.
```yaml
Type: OfflineAddressBookIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -124,12 +115,9 @@ Accept wildcard characters: False
```
### -RoomList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RoomList parameter specifies an address list that used for location experiences for mailbox users who have this address book policy assigned to them.
-- When using location experiences (for example, Room Finder or selecting a conference room when scheduling a meeting), users see only resources that match the [RecipientFilter](https://learn.microsoft.com/powershell/module/exchangepowershell/new-addresslist#-recipientfilter) results from the address list that's specified by this parameter.
+- When using location experiences (for example, Room Finder or selecting a conference room when scheduling a meeting), users see only resources that match the [RecipientFilter](https://learn.microsoft.com/powershell/module/exchange/new-addresslist#-recipientfilter) results from the address list that's specified by this parameter.
- When using experiences that aren't location specific (for example, the To or Cc fields of a calendar event), the address lists specified by the AddressLists parameter in this address book policy are applied. The address list specified by this parameter isn't used.
A valid value for this parameter is one address list. You can use any value that uniquely identifies the address list. For example:
@@ -145,6 +133,7 @@ A valid value for this parameter is one address list. You can use any value that
Type: AddressListIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -154,9 +143,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -166,6 +152,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -175,9 +162,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -186,6 +170,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -195,15 +180,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md b/exchange/exchange-ps/exchange/New-AddressList.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/New-AddressList.md
rename to exchange/exchange-ps/exchange/New-AddressList.md
index b0e5d2457b..540855b553 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md
+++ b/exchange/exchange-ps/exchange/New-AddressList.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-addresslist
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-AddressList
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-addresslist
-schema: 2.0.0
-title: New-AddressList
+ms.reviewer:
---
# New-AddressList
@@ -102,15 +101,13 @@ This example creates the address list AL\_AgencyB that includes mailboxes that h
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies the unique name for the new address list. The maximum length is 64 characters, and it can't include a carriage return or a backslash (\\). If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -120,9 +117,6 @@ Accept wildcard characters: False
```
### -IncludedRecipients
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
- AllRecipients: This value can be used only by itself.
@@ -140,6 +134,7 @@ You need to use this parameter when you use any Conditional parameters as part o
Type: WellKnownRecipientType
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -149,9 +144,6 @@ Accept wildcard characters: False
```
### -RecipientFilter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -169,6 +161,7 @@ You can't use this parameter in combination with the IncludedRecipients paramete
Type: String
Parameter Sets: CustomFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -178,9 +171,6 @@ Accept wildcard characters: False
```
### -ConditionalCompany
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -191,6 +181,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -200,9 +191,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute1
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -213,6 +201,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -222,9 +211,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute10
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -235,6 +221,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -244,9 +231,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute11
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -257,6 +241,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -266,9 +251,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute12
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -279,6 +261,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -288,9 +271,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute13
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -301,6 +281,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -310,9 +291,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute14
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -323,6 +301,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -332,9 +311,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute15
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -345,6 +321,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -354,9 +331,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute2
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -367,6 +341,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -376,9 +351,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute3
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -389,6 +361,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -398,9 +371,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute4
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -411,6 +381,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -420,9 +391,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute5
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -433,6 +401,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -442,9 +411,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute6
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -455,6 +421,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -464,9 +431,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute7
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -477,6 +441,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -486,9 +451,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute8
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -499,6 +461,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -508,9 +471,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute9
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -521,6 +481,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -530,9 +491,6 @@ Accept wildcard characters: False
```
### -ConditionalDepartment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -543,6 +501,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -552,9 +511,6 @@ Accept wildcard characters: False
```
### -ConditionalStateOrProvince
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -565,6 +521,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -574,9 +531,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -586,6 +540,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -595,9 +550,6 @@ Accept wildcard characters: False
```
### -Container
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Container parameter specifies where to create the address list. Valid input for this parameter is under the root "\\" (also known as All Address Lists) or under an existing address list. You can use any value that uniquely identifies the address list. For example:
- Name
@@ -611,6 +563,7 @@ If you don't use this parameter,the address list is created under the root (\\).
Type: AddressListIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -620,9 +573,6 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DisplayName parameter specifies the display name of the address list. The display name is visible in the Exchange admin center and Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
If you don't use the DisplayName parameter, the value of the Name parameter is used for the display name.
@@ -631,6 +581,7 @@ If you don't use the DisplayName parameter, the value of the Name parameter is u
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -640,9 +591,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -651,6 +599,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -660,9 +609,6 @@ Accept wildcard characters: False
```
### -RecipientContainer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RecipientContainer parameter specifies a filter that's based on the recipient's location in Active Directory. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
@@ -678,6 +624,7 @@ If you don't use this parameter, the default value is the OU where the object wa
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -687,15 +634,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md b/exchange/exchange-ps/exchange/New-AddressRewriteEntry.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md
rename to exchange/exchange-ps/exchange/New-AddressRewriteEntry.md
index 0d8d06f58d..1c5c9541bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md
+++ b/exchange/exchange-ps/exchange/New-AddressRewriteEntry.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-addressrewriteentry
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-AddressRewriteEntry
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-addressrewriteentry
-schema: 2.0.0
-title: New-AddressRewriteEntry
+ms.reviewer:
---
# New-AddressRewriteEntry
@@ -60,15 +59,13 @@ This example creates an address rewrite entry that rewrites all email addresses
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies a unique name for this address rewrite entry.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -ExternalAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExternalAddress parameter specifies the final email addresses that you want. If the InternalAddress parameter specifies a single email address (chris@contoso.com), the ExternalAddress parameter must also specify a single email address (support@contoso.com). If the InternalAddress parameter specifies a single domain (contoso.com) or a domain and all subdomains (\*.contoso.com), the ExternalAddress parameter must specify a single domain (fabrikam.com).
You can't use the wildcard character (\*) with the ExternalAddress parameter.
@@ -89,6 +83,7 @@ You can't use the wildcard character (\*) with the ExternalAddress parameter.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -98,9 +93,6 @@ Accept wildcard characters: False
```
### -InternalAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The InternalAddress parameter specifies the original email addresses that you want to change. You can use the following values:
- Single email address: david@contoso.com
@@ -111,6 +103,7 @@ The InternalAddress parameter specifies the original email addresses that you wa
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -120,9 +113,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -132,6 +122,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,9 +132,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -152,6 +140,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -161,15 +150,13 @@ Accept wildcard characters: False
```
### -ExceptionList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExceptionList parameter specifies the email address domains that shouldn't be rewritten when the InternalAddress parameter contains the wildcard character to rewrite addresses in a domain and all subdomains (\*.contoso.com). You can enter multiple domain values in the ExceptionList parameter separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -179,9 +166,6 @@ Accept wildcard characters: False
```
### -OutboundOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OutboundOnly parameter enables or disables outbound-only address rewriting. Valid input for this parameter is $true or $false. The value $true means address rewriting occurs in outbound mail only. The value $false means address rewriting occurs on outbound mail and also on inbound mail (rewritten email addresses are changed back to the original email addresses in inbound mail). The default value is $false.
You must set this parameter to $true if the InternalAddress parameter contains the wildcard character to rewrite addresses in a domain and all subdomains (\*.contoso.com).
@@ -192,6 +176,7 @@ Also, when you configure outbound-only address rewriting, you need to configure
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -201,15 +186,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md b/exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md
similarity index 84%
rename from exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md
rename to exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md
index 6f6e1a5d91..1059619e55 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md
+++ b/exchange/exchange-ps/exchange/New-AdminAuditLogSearch.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-adminauditlogsearch
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+title: New-AdminAuditLogSearch
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-adminauditlogsearch
-schema: 2.0.0
-title: New-AdminAuditLogSearch
+ms.reviewer:
---
# New-AdminAuditLogSearch
@@ -67,9 +66,6 @@ This example returns entries in the administrator audit log of an Exchange Onlin
## PARAMETERS
### -EndDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The EndDate parameter specifies the end date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -78,6 +74,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
Default value: None
@@ -86,9 +83,6 @@ Accept wildcard characters: False
```
### -StartDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The StartDate parameter specifies the start date of the date range.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -97,6 +91,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
Default value: None
@@ -105,9 +100,6 @@ Accept wildcard characters: False
```
### -StatusMailRecipients
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The StatusMailRecipients parameter specifies the recipients that should receive the administrator audit log report. The recipient must be a valid SMTP address.
If you want to specify more than one recipient, separate each SMTP address with a comma.
@@ -116,6 +108,7 @@ If you want to specify more than one recipient, separate each SMTP address with
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: True
Position: Named
Default value: None
@@ -124,9 +117,6 @@ Accept wildcard characters: False
```
### -Cmdlets
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Cmdlets parameter specifies the cmdlets you want to search for in the administrator audit log. Only the log entries that contain the cmdlets you specify are returned.
If you want to specify more than one cmdlet, separate each cmdlet with a comma.
@@ -135,6 +125,7 @@ If you want to specify more than one cmdlet, separate each cmdlet with a comma.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
Default value: None
@@ -143,9 +134,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -155,6 +143,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
Default value: None
@@ -163,9 +152,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -174,6 +160,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -183,15 +170,13 @@ Accept wildcard characters: False
```
### -ExternalAccess
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ExternalAccess parameter returns only audit log entries for cmdlets that were run by a user outside of your organization. In Exchange Online, use this parameter to return audit log entries for cmdlets run by Microsoft datacenter administrators.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
Default value: None
@@ -200,9 +185,6 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Name parameter specifies the name of the administrator audit log search. The name is shown in the subject line of the audit log report email message.
If the name of the report contains spaces, enclose the name in quotation marks (").
@@ -211,6 +193,7 @@ If the name of the report contains spaces, enclose the name in quotation marks (
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
Default value: None
@@ -219,9 +202,6 @@ Accept wildcard characters: False
```
### -ObjectIds
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The ObjectIds parameter specifies that only administrator audit log entries that contain the specified changed objects should be returned. This parameter accepts a variety of objects, such as mailboxes, aliases, Send connector names and so on.
If you want to specify more than one object ID, separate each ID with a comma.
@@ -230,6 +210,7 @@ If you want to specify more than one object ID, separate each ID with a comma.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
Default value: None
@@ -238,9 +219,6 @@ Accept wildcard characters: False
```
### -Parameters
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The Parameters parameter specifies the parameters you want to search for in the administrator audit log. Only the log entries that contain the parameters you specify are returned. You can only use this parameter if you use the Cmdlets parameter.
If you want to specify more than one parameter, separate each parameter with a comma.
@@ -249,6 +227,7 @@ If you want to specify more than one parameter, separate each parameter with a c
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
Default value: None
@@ -257,9 +236,6 @@ Accept wildcard characters: False
```
### -UserIds
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The UserIds parameter specifies that only the administrator audit log entries that contain the specified ID of the user who ran the cmdlet should be returned.
If you want to specify more than one user ID, separate each ID with a comma.
@@ -268,6 +244,7 @@ If you want to specify more than one user ID, separate each ID with a comma.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
Default value: None
@@ -276,9 +253,6 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
@@ -287,6 +261,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
Required: False
Position: Named
Default value: None
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md b/exchange/exchange-ps/exchange/New-AntiPhishPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md
rename to exchange/exchange-ps/exchange/New-AntiPhishPolicy.md
index 3275adc777..412a2a5340 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md
+++ b/exchange/exchange-ps/exchange/New-AntiPhishPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-antiphishpolicy
applicable: Exchange Online, Exchange Online Protection
+title: New-AntiPhishPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-antiphishpolicy
-schema: 2.0.0
-title: New-AntiPhishPolicy
+ms.reviewer:
---
# New-AntiPhishPolicy
@@ -92,15 +91,13 @@ In Microsoft Defender for Office 365, this example creates and enables an antiph
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Name parameter specifies a unique name for the antiphish policy. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -110,15 +107,13 @@ Accept wildcard characters: False
```
### -AdminDisplayName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AdminDisplayName parameter specifies a description for the policy. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -128,9 +123,6 @@ Accept wildcard characters: False
```
### -AuthenticationFailAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This setting is part of spoof protection.
The AuthenticationFailAction parameter specifies the action to take when the message fails composite authentication (a mixture of traditional SPF, DKIM, and DMARC email authentication checks and proprietary backend intelligence). Valid values are:
@@ -142,6 +134,7 @@ The AuthenticationFailAction parameter specifies the action to take when the mes
Type: SpoofAuthenticationFailAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -151,9 +144,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -163,6 +153,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -172,9 +163,6 @@ Accept wildcard characters: False
```
### -DmarcQuarantineAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This setting is part of spoof protection.
The DmarcQuarantineAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=quarantine`. Valid values are:
@@ -188,6 +176,7 @@ This parameter is meaningful only when the HonorDmarcPolicy parameter is set to
Type: SpoofDmarcQuarantineAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -197,9 +186,6 @@ Accept wildcard characters: False
```
### -DmarcRejectAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This setting is part of spoof protection.
The DmarcRejectAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=reject`. Valid values are:
@@ -213,6 +199,7 @@ This parameter is meaningful only when the HonorDmarcPolicy parameter is set to
Type: SpoofDmarcRejectAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -222,9 +209,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
To create a disabled anti-phishing policy (the combination of the antiphish rule and the associated antiphish policy), use `-Enabled $false` on the **New-AntiPhishRule** cmdlet.
@@ -237,6 +221,7 @@ In the output of the **Get-AntiPhishRule** cmdlet, whether the anti-phishing pol
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -246,9 +231,6 @@ Accept wildcard characters: False
```
### -EnableFirstContactSafetyTips
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EnableFirstContactSafetyTips parameter specifies whether to enable or disable the safety tip that's shown when recipients first receive an email from a sender or do not often receive email from a sender. Valid values are:
- $true: First contact safety tips are enabled.
@@ -258,6 +240,7 @@ The EnableFirstContactSafetyTips parameter specifies whether to enable or disabl
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -267,9 +250,6 @@ Accept wildcard characters: False
```
### -EnableMailboxIntelligence
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The EnableMailboxIntelligence parameter specifies whether to enable or disable mailbox intelligence, which is artificial intelligence (AI) that determines user email patterns with their frequent contacts. Mailbox intelligence helps distinguish between messages from legitimate and impersonated senders based on a recipient's previous communication history. Valid values are:
@@ -281,6 +261,7 @@ The EnableMailboxIntelligence parameter specifies whether to enable or disable m
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -290,9 +271,6 @@ Accept wildcard characters: False
```
### -EnableMailboxIntelligenceProtection
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The EnableMailboxIntelligenceProtection specifies whether to enable or disable taking action for impersonation detections from mailbox intelligence results. Valid values are:
@@ -308,6 +286,7 @@ If you set this parameter to the value $false when the value of the EnableMailbo
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -317,9 +296,6 @@ Accept wildcard characters: False
```
### -EnableOrganizationDomainsProtection
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The EnableOrganizationDomainsProtection parameter specifies whether to enable domain impersonation protection for all registered domains in the Microsoft 365 organization. Valid values are:
@@ -331,6 +307,7 @@ The EnableOrganizationDomainsProtection parameter specifies whether to enable do
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -340,9 +317,6 @@ Accept wildcard characters: False
```
### -EnableSimilarDomainsSafetyTips
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for domain impersonation detections. Valid values are:
@@ -354,6 +328,7 @@ The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the saf
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -363,9 +338,6 @@ Accept wildcard characters: False
```
### -EnableSimilarUsersSafetyTips
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for user impersonation detections. Valid values are:
@@ -377,6 +349,7 @@ The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safet
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -386,9 +359,6 @@ Accept wildcard characters: False
```
### -EnableSpoofIntelligence
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This setting is part of spoof protection.
The EnableSpoofIntelligence parameter specifies whether to enable or disable antispoofing protection for the policy. Valid values are:
@@ -400,6 +370,7 @@ The EnableSpoofIntelligence parameter specifies whether to enable or disable ant
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -409,9 +380,6 @@ Accept wildcard characters: False
```
### -EnableTargetedDomainsProtection
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The EnableTargetedDomainsProtection parameter specifies whether to enable domain impersonation protection for a list of specified domains. Valid values are:
@@ -423,6 +391,7 @@ The EnableTargetedDomainsProtection parameter specifies whether to enable domain
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -432,9 +401,6 @@ Accept wildcard characters: False
```
### -EnableTargetedUserProtection
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The EnableTargetedUserProtection parameter specifies whether to enable user impersonation protection for a list of specified users. Valid values are:
@@ -446,6 +412,7 @@ The EnableTargetedUserProtection parameter specifies whether to enable user impe
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -455,9 +422,6 @@ Accept wildcard characters: False
```
### -EnableUnauthenticatedSender
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This setting is part of spoof protection.
The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are:
@@ -474,6 +438,7 @@ To prevent these identifiers from being added to messages from specific senders,
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -483,9 +448,6 @@ Accept wildcard characters: False
```
### -EnableUnusualCharactersSafetyTips
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for unusual characters in domain and user impersonation detections. Valid values are:
@@ -497,6 +459,7 @@ The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -506,9 +469,6 @@ Accept wildcard characters: False
```
### -EnableViaTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This setting is part of spoof protection.
The EnableViaTag parameter enables or disables adding the via tag to the From address in Outlook (chris@contso.com via fabrikam.com). Valid values are:
@@ -525,6 +485,7 @@ To prevent the via tag from being added to messages from specific senders, you h
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -534,9 +495,6 @@ Accept wildcard characters: False
```
### -ExcludedDomains
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The ExcludedDomains parameter specifies an exception for impersonation protection that looks for the specified domains in the message sender. You can specify multiple domains separated by commas.
@@ -549,6 +507,7 @@ The maximum number of entries is approximately 1000.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -558,9 +517,6 @@ Accept wildcard characters: False
```
### -ExcludedSenders
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The ExcludedSenders parameter specifies an exception for impersonation protection that looks for the specified message sender. You can specify multiple email addresses separated by commas.
@@ -571,6 +527,7 @@ The maximum number of entries is approximately 1000.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -580,9 +537,6 @@ Accept wildcard characters: False
```
### -HonorDmarcPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This setting is part of spoof protection.
The HonorDmarcPolicy enables or disables using the sender's DMARC policy to determine what to do to messages that fail DMARC checks. Valid values are:
@@ -594,6 +548,7 @@ The HonorDmarcPolicy enables or disables using the sender's DMARC policy to dete
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -603,9 +558,6 @@ Accept wildcard characters: False
```
### -ImpersonationProtectionState
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The ImpersonationProtectionState parameter specifies the configuration of impersonation protection. Valid values are:
@@ -618,6 +570,7 @@ The ImpersonationProtectionState parameter specifies the configuration of impers
Type: ImpersonationProtectionState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -627,9 +580,6 @@ Accept wildcard characters: False
```
### -MailboxIntelligenceProtectionAction
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The MailboxIntelligenceProtectionAction parameter specifies what to do with messages that fail mailbox intelligence protection. Valid values are:
@@ -647,6 +597,7 @@ This parameter is meaningful only if the EnableMailboxIntelligence and EnableMai
Type: ImpersonationAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -656,9 +607,6 @@ Accept wildcard characters: False
```
### -MailboxIntelligenceProtectionActionRecipients
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The MailboxIntelligenceProtectionActionRecipients parameter specifies the recipients to add to detected messages when the MailboxIntelligenceProtectionAction parameter is set to the value Redirect or BccMessage.
@@ -669,6 +617,7 @@ A valid value for this parameter is an email address. You can specify multiple e
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -678,9 +627,6 @@ Accept wildcard characters: False
```
### -MailboxIntelligenceQuarantineTag
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The MailboxIntelligenceQuarantineTag specifies the quarantine policy that's used on messages that are quarantined by mailbox intelligence (the MailboxIntelligenceProtectionAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
@@ -699,6 +645,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -708,9 +655,6 @@ Accept wildcard characters: False
```
### -MakeDefault
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MakeDefault switch makes this antiphish policy the default antiphish policy. You don't need to specify a value with this switch.
The default antiphish policy is applied to everyone (no corresponding antiphish rule), can't be renamed, and has the unmodifiable priority value Lowest (the default policy is always applied last).
@@ -719,6 +663,7 @@ The default antiphish policy is applied to everyone (no corresponding antiphish
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -728,9 +673,6 @@ Accept wildcard characters: False
```
### -PhishThresholdLevel
-
-> Applicable: Exchange Online
-
This setting is part of advanced settings and is available only in Microsoft Defender for Office 365.
The PhishThresholdLevel parameter specifies the tolerance level that's used by machine learning in the handling of phishing messages. Valid values are:
@@ -744,6 +686,7 @@ The PhishThresholdLevel parameter specifies the tolerance level that's used by m
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -753,15 +696,13 @@ Accept wildcard characters: False
```
### -PolicyTag
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -771,15 +712,13 @@ Accept wildcard characters: False
```
### -RecommendedPolicyType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecommendedPolicyType parameter is used for Standard and Strict policy creation as part of [Preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies). Don't use this parameter yourself.
```yaml
Type: RecommendedPolicyType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -789,15 +728,13 @@ Accept wildcard characters: False
```
### -SimilarUsersSafetyTipsCustomText
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -807,9 +744,6 @@ Accept wildcard characters: False
```
### -SpoofQuarantineTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SpoofQuarantineTag specifies the quarantine policy that's used on messages that are quarantined by spoof intelligence (the AuthenticationFailAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
- Name
@@ -826,6 +760,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -835,9 +770,6 @@ Accept wildcard characters: False
```
### -TargetedDomainActionRecipients
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The TargetedDomainActionRecipients parameter specifies the recipients to add to detected domain impersonation messages when the TargetedDomainProtectionAction parameter is set to the value Redirect or BccMessage.
@@ -848,6 +780,7 @@ A valid value for this parameter is an email address. You can specify multiple e
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -857,9 +790,6 @@ Accept wildcard characters: False
```
### -TargetedDomainProtectionAction
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The TargetedDomainProtectionAction parameter specifies the action to take on detected domain impersonation messages. You specify the protected domains in the TargetedDomainsToProtect parameter. Valid values are:
@@ -875,6 +805,7 @@ The TargetedDomainProtectionAction parameter specifies the action to take on det
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -884,9 +815,6 @@ Accept wildcard characters: False
```
### -TargetedDomainQuarantineTag
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The TargetedDomainQuarantineTag specifies the quarantine policy that's used on messages that are quarantined by domain impersonation protection (the TargetedDomainProtectionAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
@@ -905,6 +833,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -914,9 +843,6 @@ Accept wildcard characters: False
```
### -TargetedDomainsToProtect
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The TargetedDomainsToProtect parameter specifies the domains that are included in domain impersonation protection when the EnableTargetedDomainsProtection parameter is set to $true.
@@ -927,6 +853,7 @@ You can specify multiple domains separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -936,9 +863,6 @@ Accept wildcard characters: False
```
### -TargetedUserActionRecipients
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The TargetedUserActionRecipients parameter specifies the replacement or additional recipients for detected user impersonation messages when the TargetedUserProtectionAction parameter is set to the value Redirect or BccMessage.
@@ -949,6 +873,7 @@ A valid value for this parameter is an email address. You can specify multiple e
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -958,9 +883,6 @@ Accept wildcard characters: False
```
### -TargetedUserProtectionAction
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The TargetedUserProtectionAction parameter specifies the action to take on detected user impersonation messages. You specify the protected users in the TargetedUsersToProtect parameter. Valid values are:
@@ -976,6 +898,7 @@ The TargetedUserProtectionAction parameter specifies the action to take on detec
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -985,9 +908,6 @@ Accept wildcard characters: False
```
### -TargetedUserQuarantineTag
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The TargetedUserQuarantineTag specifies the quarantine policy that's used on messages that are quarantined by user impersonation protection (the TargetedUserProtectionAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
@@ -1006,6 +926,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -1015,9 +936,6 @@ Accept wildcard characters: False
```
### -TargetedUsersToProtect
-
-> Applicable: Exchange Online
-
This setting is part of impersonation protection and is available only in Microsoft Defender for Office 365.
The TargetedUsersToProtect parameter specifies the users that are included in user impersonation protection when the EnableTargetedUserProtection parameter is set to $true.
@@ -1032,6 +950,7 @@ This parameter uses the syntax: "DisplayName;EmailAddress".
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -1041,15 +960,13 @@ Accept wildcard characters: False
```
### -UnusualCharactersSafetyTipsCustomText
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -1059,15 +976,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md b/exchange/exchange-ps/exchange/New-AntiPhishRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md
rename to exchange/exchange-ps/exchange/New-AntiPhishRule.md
index b779bdcd5c..79afcd0346 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md
+++ b/exchange/exchange-ps/exchange/New-AntiPhishRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-antiphishrule
applicable: Exchange Online, Exchange Online Protection
+title: New-AntiPhishRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-antiphishrule
-schema: 2.0.0
-title: New-AntiPhishRule
+ms.reviewer:
---
# New-AntiPhishRule
@@ -60,15 +59,13 @@ This example creates an antiphish rule named Research Department with the follow
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Name parameter specifies a unique name for the antiphish rule. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -AntiPhishPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AntiPhishPolicy parameter specifies the antiphish policy that's associated with the antiphish rule.
You can use any value that uniquely identifies the policy. For example:
@@ -95,6 +89,7 @@ You can't specify the default antiphish policy. And, you can't specify an antiph
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -104,15 +99,13 @@ Accept wildcard characters: False
```
### -Comments
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Comments parameter specifies informative comments for the rule, such as what the rule is used for or how it has changed over time. The length of the comment can't exceed 1024 characters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -122,9 +115,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -134,6 +124,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -143,9 +134,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Enabled parameter specifies whether the rule is enabled. Valid values are:
- $true: The rule is enabled. This is the default value.
@@ -157,6 +145,7 @@ In the properties of the rule, the value of this parameter is visible in the Sta
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -166,15 +155,13 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientDomainIs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -184,9 +171,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentTo
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -202,6 +186,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -211,9 +196,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentToMemberOf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfSentToMemberOf parameter specifies an exception that looks for messages sent to members of distribution groups, mail-enabled security groups, or sent to Microsoft 365 Groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -231,6 +213,7 @@ If you remove the group after you create the rule, no exception is made for mess
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -240,9 +223,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules:
@@ -257,6 +237,7 @@ If you modify the priority value of a rule, the position of the rule in the list
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -266,15 +247,13 @@ Accept wildcard characters: False
```
### -RecipientDomainIs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientDomainIs parameter specifies a condition that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -284,9 +263,6 @@ Accept wildcard characters: False
```
### -SentTo
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SentTo parameter specifies a condition that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -302,6 +278,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -311,9 +288,6 @@ Accept wildcard characters: False
```
### -SentToMemberOf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SentToMemberOf parameter specifies a condition that looks for messages sent to members of distribution groups, mail-enabled security groups, or sent to Microsoft 365 Groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -331,6 +305,7 @@ If you remove the group after you create the rule, no action is taken on message
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -340,15 +315,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-App.md b/exchange/exchange-ps/exchange/New-App.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/New-App.md
rename to exchange/exchange-ps/exchange/New-App.md
index 36786d92f6..12f88e9b57 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-App.md
+++ b/exchange/exchange-ps/exchange/New-App.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-app
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: New-App
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-app
-schema: 2.0.0
-title: New-App
+ms.reviewer:
---
# New-App
@@ -147,9 +146,6 @@ This example installs the Contoso CRM app manifest.xml from a URL on the Contoso
## PARAMETERS
### -AddInOverrides
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill AddInOverrides Description }}
@@ -158,6 +154,7 @@ This parameter is available only in the cloud-based service.
Type: AddInOverrides
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -167,15 +164,13 @@ Accept wildcard characters: False
```
### -AllowReadWriteMailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AllowReadWriteMailbox switch specifies whether the app allows read/write mailbox permission. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -185,9 +180,6 @@ Accept wildcard characters: False
```
### -AllowSetting
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill AllowSetting Description }}
@@ -196,6 +188,7 @@ This parameter is available only in the cloud-based service.
Type: AllowSetting
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -205,9 +198,6 @@ Accept wildcard characters: False
```
### -AppState
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill AppState Description }}
@@ -216,6 +206,7 @@ This parameter is available only in the cloud-based service.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -225,9 +216,6 @@ Accept wildcard characters: False
```
### -AppType
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill AppType Description }}
@@ -236,6 +224,7 @@ This parameter is available only in the cloud-based service.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -245,9 +234,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -257,6 +243,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -266,9 +253,6 @@ Accept wildcard characters: False
```
### -DefaultStateForUser
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DefaultStateForUser parameter specifies the default initial state of an organization app. Valid values are:
- Enabled: The organization app is enabled by default.
@@ -281,6 +265,7 @@ You need to use the OrganizationApp switch when you use this parameter.
Type: DefaultStateForUser
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -290,9 +275,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -301,6 +283,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -310,9 +293,6 @@ Accept wildcard characters: False
```
### -DownloadOnly
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The DownloadOnly switch specifies whether to get the app manifest file and prompt the user for confirmation before committing to actual installation. You don't need to specify a value with this switch.
When you use this switch, the cmdlet only downloads the app manifest file and displays the app properties without installing the app.
@@ -321,6 +301,7 @@ When you use this switch, the cmdlet only downloads the app manifest file and di
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -330,9 +311,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Enabled parameter specifies whether the app is available to users in the organization. Valid values are:
- $true: The app is available to the specified users. This is the default value.
@@ -344,6 +322,7 @@ This setting overrides the ProvidedTo, UserList and DefaultStateForUser settings
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -353,15 +332,13 @@ Accept wildcard characters: False
```
### -Etoken
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: ExtensionOfficeMarketplace
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -371,9 +348,6 @@ Accept wildcard characters: False
```
### -FileData
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FileData parameter specifies the location of the app manifest file. You need to specify only one source location for the app manifest file. You can specify the app manifest file by using the MarketplaceServicesUrl, Url, or FileData parameter.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -382,6 +356,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: ExtensionFileData
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -391,15 +366,13 @@ Accept wildcard characters: False
```
### -FileStream
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FileStream parameter is used only by the Exchange admin center to support the app file uploader. Don't use this parameter to specify the app manifest file. You can specify the app manifest file by using the MarketplaceServicesUrl, Url or FileData parameter.
```yaml
Type: Stream
Parameter Sets: ExtensionFileStream
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -409,9 +382,6 @@ Accept wildcard characters: False
```
### -Identity
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill Identity Description }}
@@ -420,6 +390,7 @@ This parameter is available only in the cloud-based service.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -429,9 +400,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox where you want to install the app. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -449,6 +417,7 @@ The Mailbox parameter specifies the mailbox where you want to install the app. Y
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -458,15 +427,13 @@ Accept wildcard characters: False
```
### -MarketplaceAssetID
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The MarketplaceAssetID parameter specifies the Office Store identifier for the app. You need to use this parameter if you use theMarketplaceServicesUrl parameter.
```yaml
Type: String
Parameter Sets: ExtensionOfficeMarketplace
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -476,15 +443,13 @@ Accept wildcard characters: False
```
### -MarketplaceCorrelationID
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The MarketplaceCorrelationID parameter specifies the Office Store correlation identifier for the app.
```yaml
Type: String
Parameter Sets: ExtensionOfficeMarketplace
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -494,15 +459,13 @@ Accept wildcard characters: False
```
### -MarketplaceQueryMarket
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The MarketplaceQueryMarket parameter specifies the locale that an app is filed under at the office marketplace. For example, an app for the United States market in English uses the value en-US. The default value is en-US.
```yaml
Type: String
Parameter Sets: ExtensionOfficeMarketplace
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -512,15 +475,13 @@ Accept wildcard characters: False
```
### -MarketplaceServicesUrl
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The MarketplaceServicesUrl parameter specifies the full services URL for the app. You need to specify only one source location for the app manifest file. You can specify the app manifest file by using the MarketplaceServicesUrl, Url or FileData parameter.
```yaml
Type: String
Parameter Sets: ExtensionOfficeMarketplace
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -530,15 +491,13 @@ Accept wildcard characters: False
```
### -MarketplaceUserProfileType
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The MarketplaceUserProfileType parameter specifies the user profile type for the Office Store.
```yaml
Type: String
Parameter Sets: ExtensionOfficeMarketplace
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -548,15 +507,13 @@ Accept wildcard characters: False
```
### -OrganizationApp
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The OrganizationApp switch specifies that the scope of the app is organizational (not bound to a specific user). You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -566,15 +523,13 @@ Accept wildcard characters: False
```
### -PrivateCatalog
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The PrivateCatalog switch specifies whether the app is located in a private catalog. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -584,9 +539,6 @@ Accept wildcard characters: False
```
### -ProvidedTo
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ProvidedTo parameter specifies the availability of the app in your organization. Valid values are:
- Everyone: This is the default value. This app is provided to every user in the organization. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions.
@@ -598,6 +550,7 @@ You use this parameter with the OrganizationApp switch.
Type: ClientExtensionProvidedTo
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -607,9 +560,6 @@ Accept wildcard characters: False
```
### -UpdateAppState
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill UpdateAppState Description }}
@@ -618,6 +568,7 @@ This parameter is available only in the cloud-based service.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -627,9 +578,6 @@ Accept wildcard characters: False
```
### -Url
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Url parameter specifies the full URL location of the app manifest file that you want to install. You need to specify only one source location for the app manifest file. You can specify the app manifest file by using the MarketplaceServicesUrl, Url or FileData parameter.
**Note**: URLs with redirections are not supported in Exchange Server 2016, Exchange Server 2019, and Exchange Online. Use a direct URL to the manifest.
@@ -638,6 +586,7 @@ The Url parameter specifies the full URL location of the app manifest file that
Type: Uri
Parameter Sets: ExtensionPrivateURL
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -647,9 +596,6 @@ Accept wildcard characters: False
```
### -UserList
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The UserList parameter specifies who can use an organizational app. This parameter is limited to 1000 users. In the cloud-based service, this value is less relevant as Office Add-in management is moving to [Centralized Deployment](https://learn.microsoft.com/office/dev/add-ins/publish/centralized-deployment).
Valid values are mailboxes or mail users in your organization. You can use any value that uniquely identifies the user. For example:
@@ -673,6 +619,7 @@ You use this parameter with the OrganizationApp switch.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -682,9 +629,6 @@ Accept wildcard characters: False
```
### -Version
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill Version Description }}
@@ -693,6 +637,7 @@ This parameter is available only in the cloud-based service.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -702,15 +647,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md
rename to exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md
index 3e58c6fc38..669e94235e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-appretentioncompliancepolicy
applicable: Security & Compliance
+title: New-AppRetentionCompliancePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-appretentioncompliancepolicy
-schema: 2.0.0
-title: New-AppRetentionCompliancePolicy
+ms.reviewer:
---
# New-AppRetentionCompliancePolicy
@@ -71,15 +70,13 @@ After you create the retention policy, use the New-AppRetentionComplianceRule cm
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the app retention compliance policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -89,9 +86,6 @@ Accept wildcard characters: False
```
### -AdaptiveScopeLocation
-
-> Applicable: Security & Compliance
-
The AdaptiveScopeLocation parameter specifies the adaptive scope location to include in the policy. You create adaptive scopes by using the New-AdaptiveScope cmdlet. You can use any value that uniquely identifies the adaptive scope. For example:
- Name
@@ -102,6 +96,7 @@ The AdaptiveScopeLocation parameter specifies the adaptive scope location to inc
Type: MultiValuedProperty
Parameter Sets: AdaptiveScopeLocation
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -111,9 +106,6 @@ Accept wildcard characters: False
```
### -Applications
-
-> Applicable: Security & Compliance
-
The Applications parameter specifies the applications to include in the policy.
This parameter uses the following syntax: `"LocationType:App1,LocationType:App2,...LocationType:AppN`:
@@ -144,6 +136,7 @@ This parameter uses the following syntax: `"LocationType:App1,LocationType:App2,
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -153,15 +146,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -171,9 +162,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -183,6 +171,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -192,9 +181,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Security & Compliance
-
The Enabled parameter enables or disables the policy. Valid values are:
- $true: The policy is enabled. This is the default value.
@@ -204,6 +190,7 @@ The Enabled parameter enables or disables the policy. Valid values are:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -213,9 +200,6 @@ Accept wildcard characters: False
```
### -ExchangeLocation
-
-> Applicable: Security & Compliance
-
The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are:
- A mailbox
@@ -235,6 +219,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -244,9 +229,6 @@ Accept wildcard characters: False
```
### -ExchangeLocationException
-
-> Applicable: Security & Compliance
-
The ExchangeLocationException parameter specifies the mailboxes exclude from the policy when you use the value All for the ExchangeLocation parameter. Valid values are:
- A mailbox
@@ -265,6 +247,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -274,9 +257,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -285,6 +265,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -294,9 +275,6 @@ Accept wildcard characters: False
```
### -ModernGroupLocation
-
-> Applicable: Security & Compliance
-
The ModernGroupLocation parameter specifies the Microsoft 365 Groups to include in the policy. Valid values are:
- A Microsoft 365 Group
@@ -315,6 +293,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -324,9 +303,6 @@ Accept wildcard characters: False
```
### -ModernGroupLocationException
-
-> Applicable: Security & Compliance
-
The ModernGroupLocationException parameter specifies the Microsoft 365 Groups to exclude from the policy when you use the value All for the ModernGroupLocation parameter.
You can use any value that uniquely identifies the Microsoft 365 Group. For example:
@@ -342,6 +318,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -351,9 +328,6 @@ Accept wildcard characters: False
```
### -PolicyRBACScopes
-
-> Applicable: Security & Compliance
-
**Note**: Admin units aren't currently supported, so this parameter isn't functional. The information presented here is for informational purposes when support for admin units is released.
The PolicyRBACScopes parameter specifies the administrative units to assign to the policy. A valid value is the Microsoft Entra ObjectID (GUID value) of the administrative unit. You can specify multiple values separated by commas.
@@ -364,6 +338,7 @@ Administrative units are available only in Microsoft Entra ID P1 or P2. You crea
Type: MultiValuedProperty
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -373,9 +348,6 @@ Accept wildcard characters: False
```
### -RestrictiveRetention
-
-> Applicable: Security & Compliance
-
The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are:
- $true: Preservation Lock is enabled for the policy. No one -- including an administrator -- can turn off the policy or make it less restrictive.
@@ -389,6 +361,7 @@ Therefore, before you lock a policy, it's critical that you understand your orga
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -398,15 +371,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md b/exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md
rename to exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md
index 03b4a2058f..3d8602cf9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md
+++ b/exchange/exchange-ps/exchange/New-AppRetentionComplianceRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-appretentioncompliancerule
applicable: Security & Compliance
+title: New-AppRetentionComplianceRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-appretentioncompliancerule
-schema: 2.0.0
-title: New-AppRetentionComplianceRule
+ms.reviewer:
---
# New-AppRetentionComplianceRule
@@ -64,15 +63,13 @@ This example creates a new retention rule named RetUnlimited and adds it to the
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the app retention compliance rule. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter specifies the app retention compliance policy that contains the app retention compliance policy rule. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -95,6 +89,7 @@ The Policy parameter specifies the app retention compliance policy that contains
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -104,15 +99,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -122,9 +115,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -134,6 +124,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -143,9 +134,6 @@ Accept wildcard characters: False
```
### -ContentContainsSensitiveInformation
-
-> Applicable: Security & Compliance
-
The ContentContainsSensitiveInformation parameter specifies a condition for the rule that's based on a sensitive information type match in content. The rule is applied to content that contains the specified sensitive information type.
This parameter uses the basic syntax `@(@{Name="SensitiveInformationType1";[minCount="Value"],@{Name="SensitiveInformationType2";[minCount="Value"],...)`. For example, `@(@{Name="U.S. Social Security Number (SSN)"; minCount="2"},@{Name="Credit Card Number"})`.
@@ -156,6 +144,7 @@ Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information
Type: PswsHashtable[]
Parameter Sets: ComplianceTag
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -165,9 +154,6 @@ Accept wildcard characters: False
```
### -ContentMatchQuery
-
-> Applicable: Security & Compliance
-
The ContentMatchQuery parameter specifies a content search filter.
This parameter uses a text search string or a query that's formatted by using the Keyword Query Language (KQL). For more information, see [Keyword Query Language (KQL) syntax reference](https://learn.microsoft.com/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference) and [Keyword queries and search conditions for eDiscovery](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions).
@@ -176,6 +162,7 @@ This parameter uses a text search string or a query that's formatted by using th
Type: String
Parameter Sets: Default, ComplianceTag
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -185,9 +172,6 @@ Accept wildcard characters: False
```
### -ExcludedItemClasses
-
-> Applicable: Security & Compliance
-
The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
- IPM.Note.Microsoft.Conversation
@@ -207,6 +191,7 @@ You can specify multiple item class values by using the following syntax: `"Valu
Type: MultiValuedProperty
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -216,9 +201,6 @@ Accept wildcard characters: False
```
### -ExpirationDateOption
-
-> Applicable: Security & Compliance
-
The ExpirationDateOption parameter specifies whether the expiration date is calculated from the content creation date or last modification date. Valid values are:
- CreationAgeInDays
@@ -228,6 +210,7 @@ The ExpirationDateOption parameter specifies whether the expiration date is calc
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -237,15 +220,13 @@ Accept wildcard characters: False
```
### -MachineLearningModelIDs
-
-> Applicable: Security & Compliance
-
{{ Fill MachineLearningModelIDs Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: ComplianceTag
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -255,9 +236,6 @@ Accept wildcard characters: False
```
### -RetentionComplianceAction
-
-> Applicable: Security & Compliance
-
The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are:
- Delete
@@ -268,6 +246,7 @@ The RetentionComplianceAction parameter specifies the retention action for the r
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -277,9 +256,6 @@ Accept wildcard characters: False
```
### -RetentionDuration
-
-> Applicable: Security & Compliance
-
The RetentionDuration parameter specifies the hold duration for the retention rule. Valid values are:
- An integer: The hold duration in days.
@@ -289,6 +265,7 @@ The RetentionDuration parameter specifies the hold duration for the retention ru
Type: Unlimited
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -298,9 +275,6 @@ Accept wildcard characters: False
```
### -RetentionDurationDisplayHint
-
-> Applicable: Security & Compliance
-
The RetentionDurationDisplayHint parameter specifies the units that are used to display the retention duration in the Microsoft Purview compliance portal. Valid values are Days, Months or Years.
- Days
@@ -314,6 +288,7 @@ Type: HoldDurationHint
Parameter Sets: Default
Aliases:
Accepted values: Days, Months, Years
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -323,15 +298,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md
rename to exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md
index 7fb71820ea..3a8139e536 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-applicationaccesspolicy
applicable: Exchange Online, Exchange Online Protection
+title: New-ApplicationAccessPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-applicationaccesspolicy
-schema: 2.0.0
-title: New-ApplicationAccessPolicy
+ms.reviewer:
---
# New-ApplicationAccessPolicy
@@ -87,9 +86,6 @@ This example creates a new application access policy with the following settings
## PARAMETERS
### -AccessRight
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AccessRight parameter specifies the restriction type that you want to assign in the application access policy. Valid values are:
- RestrictAccess: Allows the associated app to only access data that's associated with mailboxes specified by the PolicyScopeGroupID parameter.
@@ -99,6 +95,7 @@ The AccessRight parameter specifies the restriction type that you want to assign
Type: ApplicationAccessPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -108,9 +105,6 @@ Accept wildcard characters: False
```
### -AppId
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Identity parameter specifies the GUID of the apps to include in the policy. To find the GUID value of an app, run the command Get-App | Format-Table -Auto DisplayName,AppId.
You can specify multiple app GUID values separated by commas or you can specify * to indicate all applications.
@@ -119,6 +113,7 @@ You can specify multiple app GUID values separated by commas or you can specify
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -128,9 +123,6 @@ Accept wildcard characters: False
```
### -PolicyScopeGroupID
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PolicyScopeGroupID parameter specifies the recipient to define in the policy. Valid recipient types are security principals in Exchange Online (users or groups, including nested groups, that can have permissions assigned to them). For example:
- Mailboxes with associated user accounts (UserMailbox)
@@ -164,6 +156,7 @@ If you need to scope the policy to shared mailboxes, you can add the shared mail
Type: RecipientIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -173,9 +166,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -185,6 +175,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -194,15 +185,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Description parameter specifies a description for the policy. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -212,15 +201,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md b/exchange/exchange-ps/exchange/New-AuthRedirect.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md
rename to exchange/exchange-ps/exchange/New-AuthRedirect.md
index ce878ff18c..d885bf6957 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md
+++ b/exchange/exchange-ps/exchange/New-AuthRedirect.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-authredirect
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-AuthRedirect
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-authredirect
-schema: 2.0.0
-title: New-AuthRedirect
+ms.reviewer:
---
# New-AuthRedirect
@@ -49,15 +48,13 @@ This example creates an OAuth redirection object with the following settings:
## PARAMETERS
### -AuthScheme
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AuthScheme parameter specifies the authentication scheme that's used by the authentication redirection object. Typically, this value is Bearer.
```yaml
Type: AuthScheme
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -67,15 +64,13 @@ Accept wildcard characters: False
```
### -TargetUrl
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TargetUrl parameter specifies the FQDN of the Exchange Client Access Server that's responsible for processing the redirected OAuth authentication requests.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -85,9 +80,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -97,6 +89,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -106,15 +99,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -124,15 +115,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md b/exchange/exchange-ps/exchange/New-AuthServer.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md
rename to exchange/exchange-ps/exchange/New-AuthServer.md
index cbcdf925ab..5837e8cdb9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md
+++ b/exchange/exchange-ps/exchange/New-AuthServer.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-authserver
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-AuthServer
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-authserver
-schema: 2.0.0
-title: New-AuthServer
+ms.reviewer:
---
# New-AuthServer
@@ -74,15 +73,13 @@ This command creates an authorization server object with the specified settings.
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies a unique name for the authorization server object. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -92,15 +89,13 @@ Accept wildcard characters: False
```
### -AuthMetadataUrl
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AuthMetadataUrl parameter specifies the URL for the Microsoft 365 authorization server for your cloud-based organization.
```yaml
Type: String
Parameter Sets: AuthMetadataUrl, NativeClientAuthServer
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -110,9 +105,6 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Type parameter specifies the type of authorization tokens that are issued by the authorization server. Valid values are:
- ADFS
@@ -125,6 +117,7 @@ The Type parameter specifies the type of authorization tokens that are issued by
Type: AuthServerType
Parameter Sets: NativeClientAuthServer, AppSecret
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -134,9 +127,6 @@ Accept wildcard characters: False
```
### -ApplicationIdentifier
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available in the April 18, 2025 Hotfix update (HU) for Exchange 2019 CU15 and Exchange 2016 CU23.
{{ Fill ApplicationIdentifier Description }}
@@ -145,6 +135,7 @@ This parameter is available in the April 18, 2025 Hotfix update (HU) for Exchang
Type: String
Parameter Sets: AppSecret
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -154,9 +145,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -166,6 +154,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -175,15 +164,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -193,15 +180,13 @@ Accept wildcard characters: False
```
### -DomainName
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
{{ Fill DomainName Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -211,9 +196,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Enabled parameter specifies whether the authorization server is enabled. Valid values are:
- $true: Authorization tokens that are issued by the authorization server are accepted. This is the default value
@@ -223,6 +205,7 @@ The Enabled parameter specifies whether the authorization server is enabled. Val
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -232,9 +215,6 @@ Accept wildcard characters: False
```
### -TrustAnySSLCertificate
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
We don't recommend using this switch in a production environment.
@@ -243,6 +223,7 @@ We don't recommend using this switch in a production environment.
Type: SwitchParameter
Parameter Sets: AuthMetadataUrl, NativeClientAuthServer
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -252,15 +233,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/New-AuthenticationPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md
rename to exchange/exchange-ps/exchange/New-AuthenticationPolicy.md
index e623800578..4c06f72d1a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/exchange/New-AuthenticationPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-authenticationpolicy
applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: New-AuthenticationPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-authenticationpolicy
-schema: 2.0.0
-title: New-AuthenticationPolicy
+ms.reviewer:
---
# New-AuthenticationPolicy
@@ -78,15 +77,13 @@ In Exchange 2019, this example creates a new authentication policy named Researc
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Name parameter specifies the unique name for the authentication policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -96,9 +93,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthActiveSync
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthActiveSync switch specifies whether to allow Basic authentication with Exchange ActiveSync. You don't need to specify a value with this switch.
@@ -109,6 +103,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -118,9 +113,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthAutodiscover
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthAutodiscover switch specifies whether to allow Basic authentication with Autodiscover. You don't need to specify a value with this switch.
@@ -131,6 +123,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -140,9 +133,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthImap
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthImap switch specifies whether to allow Basic authentication with IMAP. You don't need to specify a value with this switch.
@@ -153,6 +143,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -162,9 +153,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthMapi
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthMapi switch specifies whether to allow Basic authentication with MAPI. You don't need to specify a value with this switch.
@@ -175,6 +163,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -184,9 +173,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthOfflineAddressBook
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthOfflineAddressBook switch specifies whether to allow Basic authentication with Offline Address Books. You don't need to specify a value with this switch.
@@ -197,6 +183,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -206,9 +193,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthOutlookService
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthOutlookService switch specifies whether to allow Basic authentication with the Outlook service. You don't need to specify a value with this switch.
@@ -219,6 +203,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -228,9 +213,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthPop
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthPop switch specifies whether to allow Basic authentication with POP. You don't need to specify a value with this switch.
@@ -241,6 +223,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -250,9 +233,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthPowershell
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthPowerShell switch specifies whether to allow Basic authentication with PowerShell. You don't need to specify a value with this switch.
@@ -263,6 +243,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -272,9 +253,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthReportingWebServices
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthReporting Web Services switch specifies whether to allow Basic authentication with reporting web services. You don't need to specify a value with this switch.
@@ -285,6 +263,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -294,9 +273,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthRpc
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthRpc switch specifies whether to allow Basic authentication with RPC. You don't need to specify a value with this switch.
@@ -307,6 +283,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -316,9 +293,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthSmtp
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthSmtp switch specifies whether to allow Basic authentication with SMTP. You don't need to specify a value with this switch.
@@ -329,6 +303,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -338,9 +313,6 @@ Accept wildcard characters: False
```
### -AllowBasicAuthWebServices
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The AllowBasicAuthWebServices switch specifies whether to allow Basic authentication with Exchange Web Services (EWS). You don't need to specify a value with this switch.
@@ -351,6 +323,7 @@ By default, Basic authentication is blocked for the protocol. Use this switch to
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -360,9 +333,6 @@ Accept wildcard characters: False
```
### -BlockLegacyAuthActiveSync
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockLegacyAuthActiveSync switch specifies whether to allow only modern authentication with Exchange ActiveSync in Exchange 2019 CU2 or later hybrid environments. You don't need to specify a value with this switch.
@@ -379,6 +349,7 @@ Before you disable the legacy authentication methods for this protocol, verify t
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -388,9 +359,6 @@ Accept wildcard characters: False
```
### -BlockLegacyAuthAutodiscover
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockLegacyAuthAutodiscover switch specifies whether to allow only modern authentication with Autodiscover in Exchange 2019 CU2 or later hybrid environments. You don't need to specify a value with this switch.
@@ -407,6 +375,7 @@ Before you disable the legacy authentication methods for this protocol, verify t
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -416,9 +385,6 @@ Accept wildcard characters: False
```
### -BlockLegacyAuthImap
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockLegacyAuthImap switch specifies whether to allow only modern authentication with IMAP in Exchange 2019 CU2 or later hybrid environments. You don't need to specify a value with this switch.
@@ -435,6 +401,7 @@ Before you disable the legacy authentication methods for this protocol, verify t
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -444,9 +411,6 @@ Accept wildcard characters: False
```
### -BlockLegacyAuthMapi
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockLegacyAuthMapi switch specifies whether to allow only modern authentication with MAPI in Exchange 2019 CU2 or later hybrid environments. You don't need to specify a value with this switch.
@@ -463,6 +427,7 @@ Before you disable the legacy authentication methods for this protocol, verify t
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -472,9 +437,6 @@ Accept wildcard characters: False
```
### -BlockLegacyAuthOfflineAddressBook
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockLegacyAuthOfflineAddressBook switch specifies whether to allow only modern authentication with Offline Address Books in Exchange 2019 CU2 or later hybrid environments. You don't need to specify a value with this switch.
@@ -491,6 +453,7 @@ Before you disable the legacy authentication methods for this protocol, verify t
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -500,9 +463,6 @@ Accept wildcard characters: False
```
### -BlockLegacyAuthPop
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockLegacyAuthPop switch specifies whether to allow only modern authentication with POP in Exchange 2019 CU2 or later hybrid environments. You don't need to specify a value with this switch.
@@ -519,6 +479,7 @@ Before you disable the legacy authentication methods for this protocol, verify t
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -528,9 +489,6 @@ Accept wildcard characters: False
```
### -BlockLegacyAuthRpc
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockLegacyAuthRpc switch specifies whether to allow only modern authentication with RPC in Exchange 2019 CU2 or later hybrid environments. You don't need to specify a value with this switch.
@@ -547,6 +505,7 @@ Before you disable the legacy authentication methods for this protocol, verify t
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -556,9 +515,6 @@ Accept wildcard characters: False
```
### -BlockLegacyAuthWebServices
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockLegacyAuthWebServices switch specifies whether to allow only modern authentication with Exchange Web Services (EWS) in Exchange 2019 CU2 or later hybrid environments. You don't need to specify a value with this switch.
@@ -575,6 +531,7 @@ Before you disable the legacy authentication methods for this protocol, verify t
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -584,9 +541,6 @@ Accept wildcard characters: False
```
### -BlockModernAuthActiveSync
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockModernAuthActiveSync switch specifies whether to block modern authentication with Exchange ActiveSync in Exchange 2019 CU13 or later. You don't need to specify a value with this switch.
@@ -595,6 +549,7 @@ The BlockModernAuthActiveSync switch specifies whether to block modern authentic
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -604,9 +559,6 @@ Accept wildcard characters: False
```
### -BlockModernAuthAutodiscover
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockModernAuthAutodiscover switch specifies whether to block modern authentication with Autodiscover in Exchange 2019 CU13 or later. You don't need to specify a value with this switch.
@@ -615,6 +567,7 @@ The BlockModernAuthAutodiscover switch specifies whether to block modern authent
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -624,9 +577,6 @@ Accept wildcard characters: False
```
### -BlockModernAuthImap
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockModernAuthImap switch specifies whether to block modern authentication with IMAP in Exchange 2019 CU13 or later. You don't need to specify a value with this switch.
@@ -635,6 +585,7 @@ The BlockModernAuthImap switch specifies whether to block modern authentication
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -644,9 +595,6 @@ Accept wildcard characters: False
```
### -BlockModernAuthMapi
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockModernAuthMapi switch specifies whether to block modern authentication with MAPI in Exchange 2019 CU13 or later. You don't need to specify a value with this switch.
@@ -655,6 +603,7 @@ The BlockModernAuthMapi switch specifies whether to block modern authentication
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -664,9 +613,6 @@ Accept wildcard characters: False
```
### -BlockModernAuthOfflineAddressBook
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockModernAuthOfflineAddressBook switch specifies whether to block modern authentication with Offline Address Books in Exchange 2019 CU13 or later. You don't need to specify a value with this switch.
@@ -675,6 +621,7 @@ The BlockModernAuthOfflineAddressBook switch specifies whether to block modern a
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -684,9 +631,6 @@ Accept wildcard characters: False
```
### -BlockModernAuthPop
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockModernAuthPop switch specifies whether to block modern authentication with POP in Exchange 2019 CU13 or later. You don't need to specify a value with this switch.
@@ -695,6 +639,7 @@ The BlockModernAuthPop switch specifies whether to block modern authentication w
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -704,9 +649,6 @@ Accept wildcard characters: False
```
### -BlockModernAuthRpc
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockModernAuthRpc switch specifies whether to block modern authentication with RPC in Exchange 2019 CU13 or later. You don't need to specify a value with this switch.
@@ -715,6 +657,7 @@ The BlockModernAuthRpc switch specifies whether to block modern authentication w
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -724,9 +667,6 @@ Accept wildcard characters: False
```
### -BlockModernAuthWebServices
-
-> Applicable: Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The BlockModernAuthWebServices switch specifies whether to block modern authentication with Exchange Web Services (EWS) in Exchange 2019 CU13 or later. You don't need to specify a value with this switch.
@@ -735,6 +675,7 @@ The BlockModernAuthWebServices switch specifies whether to block modern authenti
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2019
Required: False
Position: Named
@@ -744,9 +685,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -756,6 +694,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -765,15 +704,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md
rename to exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md
index ed2a9f99e1..41c5654713 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md
+++ b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-autosensitivitylabelpolicy
applicable: Security & Compliance
+title: New-AutoSensitivityLabelPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-autosensitivitylabelpolicy
-schema: 2.0.0
-title: New-AutoSensitivityLabelPolicy
+ms.reviewer:
---
# New-AutoSensitivityLabelPolicy
@@ -72,15 +71,13 @@ This example creates an auto-labeling policy named GlobalPolicy for the specifie
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the auto-labeling policy. If the value contains spaces, enclose the value with quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -90,15 +87,13 @@ Accept wildcard characters: False
```
### -ApplySensitivityLabel
-
-> Applicable: Security & Compliance
-
The ApplySensitivityLabel parameter specifies the label to use for the auto-labeling policy.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -108,15 +103,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -126,9 +119,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -138,6 +128,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -147,9 +138,6 @@ Accept wildcard characters: False
```
### -ExceptIfOneDriveSharedBy
-
-> Applicable: Security & Compliance
-
The ExceptIfOneDriveSharedBy parameter specifies the users to exclude from the policy (the sites of the OneDrive user accounts are included in the policy). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
To use this parameter, OneDrive sites need to be included in the policy (the OneDriveLocation parameter value is All, which is the default value).
@@ -162,6 +150,7 @@ You can't use this parameter with the OneDriveSharedBy parameter.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -171,15 +160,13 @@ Accept wildcard characters: False
```
### -ExceptIfOneDriveSharedByMemberOf
-
-> Applicable: Security & Compliance
-
{{ Fill ExceptIfOneDriveSharedByMemberOf Description }}
```yaml
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -189,15 +176,13 @@ Accept wildcard characters: False
```
### -ExchangeAdaptiveScopes
-
-> Applicable: Security & Compliance
-
{{ Fill ExchangeAdaptiveScopes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -207,15 +192,13 @@ Accept wildcard characters: False
```
### -ExchangeAdaptiveScopesException
-
-> Applicable: Security & Compliance
-
{{ Fill ExchangeAdaptiveScopesException Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -225,9 +208,6 @@ Accept wildcard characters: False
```
### -ExchangeLocation
-
-> Applicable: Security & Compliance
-
The ExchangeLocation parameter specifies whether to include email messages in the policy. The valid value for this parameter is All. If you don't want to include email messages in the policy, don't use this parameter (the default value is blank or $null).
You can use this parameter in the following procedures:
@@ -248,6 +228,7 @@ You can't specify inclusions and exclusions in the same policy.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -257,9 +238,6 @@ Accept wildcard characters: False
```
### -ExchangeSender
-
-> Applicable: Security & Compliance
-
The ExchangeSender parameter specifies the users whose email is included in the policy. You identify the users by email address. You can specify internal or external email addresses.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -272,6 +250,7 @@ You can't use this parameter with the ExchangeSenderException or ExchangeSenderM
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -281,9 +260,6 @@ Accept wildcard characters: False
```
### -ExchangeSenderException
-
-> Applicable: Security & Compliance
-
The ExchangeSenderException parameter specifies the internal users whose email is excluded from the policy. You identify the users by email address.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -296,6 +272,7 @@ You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf p
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -305,9 +282,6 @@ Accept wildcard characters: False
```
### -ExchangeSenderMemberOf
-
-> Applicable: Security & Compliance
-
The ExchangeSenderMemberOf parameter specifies the distribution groups or mail-enabled security groups to include in the policy (email of the group members is included in the policy). You identify the groups by email address.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -322,6 +296,7 @@ You can't use this parameter to specify Microsoft 365 Groups.
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -331,9 +306,6 @@ Accept wildcard characters: False
```
### -ExchangeSenderMemberOfException
-
-> Applicable: Security & Compliance
-
The ExchangeSenderMemberOfException parameter specifies the distribution groups or mail-enabled security groups to exclude from the policy (email of the group members is excluded from the policy). You identify the groups by email address.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -348,6 +320,7 @@ You can't use this parameter to specify Microsoft 365 Groups.
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -357,9 +330,6 @@ Accept wildcard characters: False
```
### -ExternalMailRightsManagementOwner
-
-> Applicable: Security & Compliance
-
The ExternalMailRightsManagementOwner parameter specifies the email address of a user mailbox that's used to encrypt incoming email messages from external senders using RMS.
This parameter works only on Exchange locations, and the policy must apply a label that has an encryption action.
@@ -368,6 +338,7 @@ This parameter works only on Exchange locations, and the policy must apply a lab
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -377,9 +348,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -388,6 +356,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -397,15 +366,13 @@ Accept wildcard characters: False
```
### -Locations
-
-> Applicable: Security & Compliance
-
{{ Fill Locations Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -415,9 +382,6 @@ Accept wildcard characters: False
```
### -Mode
-
-> Applicable: Security & Compliance
-
The Mode parameter specifies the action and notification level of the auto-labeling policy. Valid values are:
- Enable: The policy is enabled for actions and notifications. This is the default value.
@@ -430,6 +394,7 @@ Type: PolicyMode
Parameter Sets: (All)
Aliases:
Accepted values: Enable, TestWithNotifications, TestWithoutNotifications, Disable, PendingDeletion
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -439,15 +404,13 @@ Accept wildcard characters: False
```
### -OneDriveAdaptiveScopes
-
-> Applicable: Security & Compliance
-
{{ Fill OneDriveAdaptiveScopes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -457,15 +420,13 @@ Accept wildcard characters: False
```
### -OneDriveAdaptiveScopesException
-
-> Applicable: Security & Compliance
-
{{ Fill OneDriveAdaptiveScopesException Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -475,9 +436,6 @@ Accept wildcard characters: False
```
### -OneDriveLocation
-
-> Applicable: Security & Compliance
-
The OneDriveLocation parameter specifies the OneDrive sites to include in the policy. You identify the site by its URL value, or you can use the value All to include all sites.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -486,6 +444,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -495,9 +454,6 @@ Accept wildcard characters: False
```
### -OneDriveLocationException
-
-> Applicable: Security & Compliance
-
This parameter specifies the OneDrive sites to exclude when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -506,6 +462,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -515,9 +472,6 @@ Accept wildcard characters: False
```
### -OneDriveSharedBy
-
-> Applicable: Security & Compliance
-
The OneDriveSharedBy parameter specifies the users to include in the policy (the sites of the OneDrive user accounts are included in the policy). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
To use this parameter, OneDrive sites need to be included in the policy (the OneDriveLocation parameter value is All, which is the default value).
@@ -530,6 +484,7 @@ You can't use this parameter with the ExceptIfOneDriveSharedBy parameter.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -539,15 +494,13 @@ Accept wildcard characters: False
```
### -OneDriveSharedByMemberOf
-
-> Applicable: Security & Compliance
-
{{ Fill OneDriveSharedByMemberOf Description }}
```yaml
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -557,9 +510,6 @@ Accept wildcard characters: False
```
### -OverwriteLabel
-
-> Applicable: Security & Compliance
-
The OverwriteLabel parameter specifies whether to overwrite a manual label. Valid values are:
- $true: Overwrite the manual label.
@@ -571,6 +521,7 @@ This parameter works only on Exchange locations.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -580,9 +531,6 @@ Accept wildcard characters: False
```
### -PolicyRBACScopes
-
-> Applicable: Security & Compliance
-
The PolicyRBACScopes parameter specifies the administrative units to assign to the policy. A valid value is the Microsoft Entra ObjectID (GUID value) of the administrative unit. You can specify multiple values separated by commas.
Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell.
@@ -591,6 +539,7 @@ Administrative units are available only in Microsoft Entra ID P1 or P2. You crea
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -600,15 +549,13 @@ Accept wildcard characters: False
```
### -PolicyTemplateInfo
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -618,15 +565,13 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Security & Compliance
-
The Priority parameter specifies the priority of the policy. The highest priority policy will take action over lower priority policies if two policies are applicable for a file.
```yaml
Type: System.Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -636,15 +581,13 @@ Accept wildcard characters: False
```
### -SharePointAdaptiveScopes
-
-> Applicable: Security & Compliance
-
{{ Fill SharePointAdaptiveScopes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -654,15 +597,13 @@ Accept wildcard characters: False
```
### -SharePointAdaptiveScopesException
-
-> Applicable: Security & Compliance
-
{{ Fill SharePointAdaptiveScopesException Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -672,9 +613,6 @@ Accept wildcard characters: False
```
### -SharePointLocation
-
-> Applicable: Security & Compliance
-
The SharePointLocation parameter specifies the SharePoint sites to include in the policy. You identify the site by its URL value, or you can use the value All to include all sites.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. SharePoint sites can't be added to a policy until they have been indexed.
@@ -683,6 +621,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -692,9 +631,6 @@ Accept wildcard characters: False
```
### -SharePointLocationException
-
-> Applicable: Security & Compliance
-
This parameter specifies the SharePoint sites to exclude when you use the value All for the SharePointLocation parameter. You identify the site by its URL value.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -703,6 +639,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -712,15 +649,13 @@ Accept wildcard characters: False
```
### -UnifiedAuditLogEnabled
-
-> Applicable: Security & Compliance
-
{{ Fill UnifiedAuditLogEnabled Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -730,15 +665,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md
rename to exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md
index b329df41b6..43a5384ec8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md
+++ b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-autosensitivitylabelrule
applicable: Security & Compliance
+title: New-AutoSensitivityLabelRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-autosensitivitylabelrule
-schema: 2.0.0
-title: New-AutoSensitivityLabelRule
+ms.reviewer:
---
# New-AutoSensitivityLabelRule
@@ -98,15 +97,13 @@ This example creates an autolabeling rule named "SocialSecurityRule" that is ass
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the auto-labeling policy rule. If the value contains spaces, enclose the value with quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -116,9 +113,6 @@ Accept wildcard characters: False
```
### -Workload
-
-> Applicable: Security & Compliance
-
The Workload parameter specifies the workload. Valid values are:
- Exchange
@@ -130,6 +124,7 @@ Type: Workload
Parameter Sets: (All)
Aliases:
Accepted values: Exchange, SharePoint, OneDriveForBusiness
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -139,9 +134,6 @@ Accept wildcard characters: False
```
### -AccessScope
-
-> Applicable: Security & Compliance
-
The AccessScope parameter specifies a condition for the auto-labeling policy rule that's based on the access scope of the content. The rule is applied to content that matches the specified access scope. Valid values are:
- InOrganization: The rule is applied to content that's accessible inside the organization.
@@ -153,6 +145,7 @@ Type: AccessScope
Parameter Sets: (All)
Aliases:
Accepted values: InOrganization, NotInOrganization, None
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -162,15 +155,13 @@ Accept wildcard characters: False
```
### -ActivationDate
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -180,9 +171,6 @@ Accept wildcard characters: False
```
### -AnyOfRecipientAddressContainsWords
-
-> Applicable: Security & Compliance
-
The AnyOfRecipientAddressContainsWords parameter specifies a condition for the auto-labeling policy rule that looks for words or phrases in recipient email addresses. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -197,6 +185,7 @@ You can use this condition in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -206,9 +195,6 @@ Accept wildcard characters: False
```
### -AnyOfRecipientAddressMatchesPatterns
-
-> Applicable: Security & Compliance
-
The AnyOfRecipientAddressMatchesPatterns parameter specifies a condition for the auto-labeling policy rule that looks for text patterns in recipient email addresses by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 10.
@@ -219,6 +205,7 @@ You can use this condition in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -228,15 +215,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -246,9 +231,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -258,6 +240,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -267,9 +250,6 @@ Accept wildcard characters: False
```
### -ContentContainsSensitiveInformation
-
-> Applicable: Security & Compliance
-
The ContentContainsSensitiveInformation parameter specifies a condition for the rule that's based on a sensitive information type match in content. The rule is applied to content that contains the specified sensitive information type.
This parameter uses the basic syntax `@(@{Name="SensitiveInformationType1";[minCount="Value"],@{Name="SensitiveInformationType2";[minCount="Value"],...)`. For example, `@(@{Name="U.S. Social Security Number (SSN)"; minCount="2"},@{Name="Credit Card Number"; minCount="1"; minConfidence="85"})`.
@@ -282,6 +262,7 @@ Exact Data Match sensitive information types are supported only groups. For exam
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -291,15 +272,13 @@ Accept wildcard characters: False
```
### -ContentExtensionMatchesWords
-
-> Applicable: Security & Compliance
-
The ContentExtensionMatchesWords parameter specifies a condition for the auto-labeling policy rule that looks for words in file name extensions. You can specify multiple words separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -309,9 +288,6 @@ Accept wildcard characters: False
```
### -ContentPropertyContainsWords
-
-> Applicable: Security & Compliance
-
The ContentPropertyContainsWords parameter specifies a condition for the auto-labeling policy rule that's based on a property match in content. The rule is applied to content that contains the specified property.
This parameter accepts values in the format: `"Property1:Value1,Value2","Property2:Value3,Value4",..."PropertyN:ValueN,ValueN"`.
@@ -320,6 +296,7 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -329,9 +306,6 @@ Accept wildcard characters: False
```
### -Disabled
-
-> Applicable: Security & Compliance
-
The Disabled parameter specifies whether the auto-labeling policy rule is enabled or disabled. Valid values are:
- $true: The rule is disabled.
@@ -341,6 +315,7 @@ The Disabled parameter specifies whether the auto-labeling policy rule is enable
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -350,15 +325,13 @@ Accept wildcard characters: False
```
### -DocumentCreatedBy
-
-> Applicable: Security & Compliance
-
{{ Fill DocumentCreatedBy Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -368,9 +341,6 @@ Accept wildcard characters: False
```
### -DocumentIsPasswordProtected
-
-> Applicable: Security & Compliance
-
The DocumentIsPasswordProtected parameter specifies a condition for the auto-labeling policy rule that looks for password protected files (because the contents of the file can't be inspected). Password detection works for Office documents, compressed files (.zip, .7z, .rar, .tar, etc.), and .pdf files. Valid values are:
- $true: Look for password protected files.
@@ -380,6 +350,7 @@ The DocumentIsPasswordProtected parameter specifies a condition for the auto-lab
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -389,9 +360,6 @@ Accept wildcard characters: False
```
### -DocumentIsUnsupported
-
-> Applicable: Security & Compliance
-
The DocumentIsUnsupported parameter specifies a condition for the auto-labeling policy rule that looks for files that can't be scanned. Valid values are:
- $true: Look for unsupported files that can't be scanned.
@@ -401,6 +369,7 @@ The DocumentIsUnsupported parameter specifies a condition for the auto-labeling
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -410,9 +379,6 @@ Accept wildcard characters: False
```
### -DocumentNameMatchesWords
-
-> Applicable: Security & Compliance
-
The DocumentNameMatchesWords parameter specifies a condition for the auto-labeling policy rule that looks for words or phrases in the name of message attachments. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -425,6 +391,7 @@ The maximum individual word or phrase length is 128 characters. The maximum numb
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -434,9 +401,6 @@ Accept wildcard characters: False
```
### -DocumentSizeOver
-
-> Applicable: Security & Compliance
-
The DocumentSizeOver parameter specifies a condition for the auto-labeling policy rule that looks for messages where any attachment is greater than the specified size.
When you enter a value, qualify the value with one of the following units:
@@ -455,6 +419,7 @@ You can use this condition in auto-labeling policy rules that are scoped only to
Type: Microsoft.Exchange.Data.ByteQuantifiedSize
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -464,9 +429,6 @@ Accept wildcard characters: False
```
### -ExceptIfAccessScope
-
-> Applicable: Security & Compliance
-
The ExceptIfAccessScopeAccessScope parameter specifies an exception for the auto-labeling policy rule that's based on the access scope of the content. The rule isn't applied to content that matches the specified access scope. Valid values are:
- InOrganization: The rule isn't applied to content that's accessible inside the organization.
@@ -478,6 +440,7 @@ Type: AccessScope
Parameter Sets: (All)
Aliases:
Accepted values: InOrganization, NotInOrganization, None
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -487,9 +450,6 @@ Accept wildcard characters: False
```
### -ExceptIfAnyOfRecipientAddressContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfAnyOfRecipientAddressContainsWords parameter specifies an exception for the auto-labeling policy rule that looks for words or phrases in recipient email addresses. You can specify multiple words separated by commas.
- Single word: `"no_reply"`
@@ -504,6 +464,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -513,9 +474,6 @@ Accept wildcard characters: False
```
### -ExceptIfAnyOfRecipientAddressMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfAnyOfRecipientAddressMatchesPatterns parameter specifies an exception for the auto-labeling policy rule that looks for text patterns in recipient email addresses by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 10.
@@ -526,6 +484,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -535,9 +494,6 @@ Accept wildcard characters: False
```
### -ExceptIfContentContainsSensitiveInformation
-
-> Applicable: Security & Compliance
-
The ExceptIfContentContainsSensitiveInformation parameter specifies an exception for the auto-labeling policy rule that's based on a sensitive information type match in content. The rule isn't applied to content that contains the specified sensitive information type.
This parameter uses the basic syntax `@(@{Name="SensitiveInformationType1";[minCount="Value"],@{Name="SensitiveInformationType2";[minCount="Value"],...)`. For example, `@(@{Name="U.S. Social Security Number (SSN)"; minCount="2"},@{Name="Credit Card Number"})`.
@@ -546,6 +502,7 @@ This parameter uses the basic syntax `@(@{Name="SensitiveInformationType1";[minC
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -555,15 +512,13 @@ Accept wildcard characters: False
```
### -ExceptIfContentExtensionMatchesWords
-
-> Applicable: Security & Compliance
-
The ExceptIfContentExtensionMatchesWords parameter specifies an exception for the auto-labeling policy rule that looks for words in file name extensions. You can specify multiple words separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -573,9 +528,6 @@ Accept wildcard characters: False
```
### -ExceptIfContentPropertyContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfContentPropertyContainsWords parameter specifies an exception for the auto-labeling policy rule that's based on a property match in content. The rule is not applied to content that contains the specified property.
This parameter accepts values in the format: `"Property1:Value1,Value2","Property2:Value3,Value4",..."PropertyN:ValueN,ValueN"`.
@@ -584,6 +536,7 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -593,15 +546,13 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentCreatedBy
-
-> Applicable: Security & Compliance
-
{{ Fill ExceptIfDocumentCreatedBy Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -611,9 +562,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentIsPasswordProtected
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentIsPasswordProtected parameter specifies an exception for the auto-labeling policy rule that looks for password protected files (because the contents of the file can't be inspected). Password detection works for Office documents, compressed files (.zip, .7z, .rar, .tar, etc.), and .pdf files. Valid values are:
- $true: Look for password protected files.
@@ -623,6 +571,7 @@ The ExceptIfDocumentIsPasswordProtected parameter specifies an exception for the
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -632,9 +581,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentIsUnsupported
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentIsUnsupported parameter specifies an exception for the auto-labeling policy rule that looks for files that can't be scanned. Valid values are:
- $true: Look for unsupported files that can't be scanned.
@@ -644,6 +590,7 @@ The ExceptIfDocumentIsUnsupported parameter specifies an exception for the auto-
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -653,9 +600,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentNameMatchesWords
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentNameMatchesWords parameter specifies an exception for the auto-labeling policy rule that looks for words or phrases in the name of message attachments. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -668,6 +612,7 @@ The maximum individual word or phrase length is 128 characters. The maximum numb
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -677,9 +622,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentSizeOver
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentSizeOver parameter specifies an exception for the auto-labeling policy rule that looks for messages where any attachment is greater than the specified size.
When you enter a value, qualify the value with one of the following units:
@@ -698,6 +640,7 @@ You can use this exception in auto-labeling policy rules that are scoped only to
Type: Microsoft.Exchange.Data.ByteQuantifiedSize
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -707,9 +650,6 @@ Accept wildcard characters: False
```
### -ExceptIfFrom
-
-> Applicable: Security & Compliance
-
The ExceptIfFrom parameter specifies an exception for the auto-labeling policy rule that looks for messages from specific senders. You can use any value that uniquely identifies the sender. For example:
- Name
@@ -723,6 +663,7 @@ The ExceptIfFrom parameter specifies an exception for the auto-labeling policy r
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -732,9 +673,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromAddressContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfFromAddressContainsWords parameter specifies an exception for the auto-labeling policy rule that looks for words or phrases in the sender's email address. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -749,6 +687,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -758,9 +697,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromAddressMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfFromAddressMatchesPatterns parameter specifies an exception for the auto-labeling policy rule that looks for text patterns in the sender's email address by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 10.
@@ -771,6 +707,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -780,9 +717,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromMemberOf
-
-> Applicable: Security & Compliance
-
The ExceptIfFromMemberOf parameter specifies an exception for the auto-labeling policy rule that looks for messages sent by group members. You identify the group members by their email addresses.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -791,6 +725,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -800,9 +735,6 @@ Accept wildcard characters: False
```
### -ExceptIfHeaderMatchesPatterns
-
-> Applicable: Security & Compliance
-
The HeaderMatchesPatterns parameter specifies an exception for the auto-labeling policy rule that looks for text patterns in a header field by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1","regular expression2",..."regular expressionN"`.
You can use this exception in auto-labeling policies that are scoped only to Exchange.
@@ -811,6 +743,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -820,9 +753,6 @@ Accept wildcard characters: False
```
### -ExceptIfProcessingLimitExceeded
-
-> Applicable: Security & Compliance
-
The ExceptIfProcessingLimitExceeded parameter specifies an exception for the auto-labeling policy rule that looks for files where scanning couldn't complete. Valid values are:
- $true: Look for files where scanning couldn't complete.
@@ -832,6 +762,7 @@ The ExceptIfProcessingLimitExceeded parameter specifies an exception for the aut
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -841,15 +772,13 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientDomainIs
-
-> Applicable: Security & Compliance
-
The ExceptIfRecipientDomainIs parameter specifies an exception for the auto-labeling policy rule that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -859,9 +788,6 @@ Accept wildcard characters: False
```
### -ExceptIfSenderDomainIs
-
-> Applicable: Security & Compliance
-
The ExceptIfSenderDomainIs parameter specifies an exception for the auto-labeling policy rule that looks for messages from senders with email address in the specified domains. You can specify multiple values separated by commas.
You can use this exception in auto-labeling policies that are scoped only to Exchange.
@@ -870,6 +796,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -879,9 +806,6 @@ Accept wildcard characters: False
```
### -ExceptIfSenderIPRanges
-
-> Applicable: Security & Compliance
-
The ExceptIfSenderIpRanges parameter specifies an exception for the auto-labeling policy rule that looks for senders whose IP addresses matches the specified value, or fall within the specified ranges. Valid values are:
- Single IP address: For example, 192.168.1.1.
@@ -894,6 +818,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -903,9 +828,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentTo
-
-> Applicable: Security & Compliance
-
The ExceptIfSentTo parameter specifies an exception for the auto-labeling policy rule that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -923,6 +845,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -932,9 +855,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentToMemberOf
-
-> Applicable: Security & Compliance
-
The ExceptIfSentToMemberOf parameter specifies an exception for the auto-labeling policy rule that looks for messages sent to members of distribution groups, dynamic distribution groups, or mail-enabled security groups. You identify the groups by email address. You can specify multiple values separated by commas.
You can use this exception in auto-labeling policies that are scoped only to Exchange.
@@ -943,6 +863,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -952,9 +873,6 @@ Accept wildcard characters: False
```
### -ExceptIfSubjectMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfSubjectMatchesPatterns parameter specifies an exception for the auto-labeling policy rule that looks for text patterns in the Subject field of messages by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 10.
@@ -965,6 +883,7 @@ You can use this exception in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -974,15 +893,13 @@ Accept wildcard characters: False
```
### -ExpiryDate
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -992,15 +909,13 @@ Accept wildcard characters: False
```
### -From
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1010,9 +925,6 @@ Accept wildcard characters: False
```
### -FromAddressContainsWords
-
-> Applicable: Security & Compliance
-
The FromAddressContainsWords parameter specifies a condition for the auto-labeling policy rule that looks for words or phrases in the sender's email address. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -1027,6 +939,7 @@ You can use this condition in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1036,9 +949,6 @@ Accept wildcard characters: False
```
### -FromAddressMatchesPatterns
-
-> Applicable: Security & Compliance
-
The FromAddressMatchesPatterns parameter specifies a condition for the auto-labeling policy rule that looks for text patterns in the sender's email address by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 10.
@@ -1049,6 +959,7 @@ You can use this condition in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1058,15 +969,13 @@ Accept wildcard characters: False
```
### -FromMemberOf
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1076,9 +985,6 @@ Accept wildcard characters: False
```
### -HeaderMatchesPatterns
-
-> Applicable: Security & Compliance
-
The HeaderMatchesPatterns parameter specifies a condition for the auto-labeling policy rule that looks for text patterns in a header field by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1","regular expression2",..."regular expressionN"`.
You can use this condition in auto-labeling policies that are scoped only to Exchange.
@@ -1087,6 +993,7 @@ You can use this condition in auto-labeling policies that are scoped only to Exc
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1096,15 +1003,13 @@ Accept wildcard characters: False
```
### -ImmutableId
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: System.Guid
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1114,9 +1019,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter specifies the auto-labeling policy that contains the auto-labeling policy rule. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -1127,6 +1029,7 @@ The Policy parameter specifies the auto-labeling policy that contains the auto-l
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -1136,15 +1039,13 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: System.Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1154,9 +1055,6 @@ Accept wildcard characters: False
```
### -ProcessingLimitExceeded
-
-> Applicable: Security & Compliance
-
The ProcessingLimitExceeded parameter specifies a condition for the auto-labeling policy rule that looks for files where scanning couldn't complete. You can use this condition to create rules that work together to identify and process messages where the content couldn't be fully scanned. Valid values are:
- $true: Look for files where scanning couldn't complete.
@@ -1166,6 +1064,7 @@ The ProcessingLimitExceeded parameter specifies a condition for the auto-labelin
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1175,15 +1074,13 @@ Accept wildcard characters: False
```
### -RecipientDomainIs
-
-> Applicable: Security & Compliance
-
The RecipientDomainIs parameter specifies a condition for the auto-labeling policy rule that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1193,9 +1090,6 @@ Accept wildcard characters: False
```
### -ReportSeverityLevel
-
-> Applicable: Security & Compliance
-
The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are:
- None: You can't select this value if the rule has no actions configured.
@@ -1208,6 +1102,7 @@ Type: RuleSeverity
Parameter Sets: (All)
Aliases:
Accepted values: Low, Medium, High, None, Informational, Information
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1217,9 +1112,6 @@ Accept wildcard characters: False
```
### -RuleErrorAction
-
-> Applicable: Security & Compliance
-
The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are:
- Ignore
@@ -1231,6 +1123,7 @@ Type: PolicyRuleErrorAction
Parameter Sets: (All)
Aliases:
Accepted values: Ignore, RetryThenBlock
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1240,9 +1133,6 @@ Accept wildcard characters: False
```
### -SenderDomainIs
-
-> Applicable: Security & Compliance
-
The SenderDomainIs parameter specifies a condition for the auto-labeling policy rule that looks for messages from senders with email address in the specified domains. You can specify multiple values separated by commas.
You can use this condition in auto-labeling policies that are scoped only to Exchange.
@@ -1251,6 +1141,7 @@ You can use this condition in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1260,9 +1151,6 @@ Accept wildcard characters: False
```
### -SenderIPRanges
-
-> Applicable: Security & Compliance
-
The SenderIpRanges parameter specifies a condition for the auto-sensitivity policy rule that looks for senders whose IP addresses matches the specified value, or fall within the specified ranges. Valid values are:
- Single IP address: For example, 192.168.1.1.
@@ -1275,6 +1163,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1284,9 +1173,6 @@ Accept wildcard characters: False
```
### -SentTo
-
-> Applicable: Security & Compliance
-
The SentTo parameter specifies a condition for the auto-sensitivity policy rule that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -1304,6 +1190,7 @@ You can use this condition in auto-sensitivity policies that are scoped only to
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1313,9 +1200,6 @@ Accept wildcard characters: False
```
### -SentToMemberOf
-
-> Applicable: Security & Compliance
-
The SentToMemberOf parameter specifies a condition for the auto-labeling policy rule that looks for messages sent to members of distribution groups, dynamic distribution groups, or mail-enabled security groups. You identify the groups by email address. You can specify multiple values separated by commas.
You can use this condition in auto-labeling policies that are scoped only to Exchange.
@@ -1324,6 +1208,7 @@ You can use this condition in auto-labeling policies that are scoped only to Exc
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1333,15 +1218,13 @@ Accept wildcard characters: False
```
### -SourceType
-
-> Applicable: Security & Compliance
-
{{ Fill SourceType Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1351,9 +1234,6 @@ Accept wildcard characters: False
```
### -SubjectMatchesPatterns
-
-> Applicable: Security & Compliance
-
The SubjectMatchesPatterns parameter specifies a condition for the auto-labeling policy rule that looks for text patterns in the Subject field of messages by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 10.
@@ -1364,6 +1244,7 @@ You can use this condition in auto-labeling policies that are scoped only to Exc
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1373,15 +1254,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md
rename to exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md
index 80f2a0f3bf..d79e23f643 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/New-AutodiscoverVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-autodiscovervirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-AutodiscoverVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-autodiscovervirtualdirectory
-schema: 2.0.0
-title: New-AutodiscoverVirtualDirectory
+ms.reviewer:
---
# New-AutodiscoverVirtualDirectory
@@ -63,15 +62,13 @@ This example creates the virtual directory autodiscover under the website autodi
## PARAMETERS
### -ApplicationRoot
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ApplicationRoot parameter specifies the metabase path of the virtual directory. By default, this path is the same as the website in which the virtual directory is created.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -81,15 +78,13 @@ Accept wildcard characters: False
```
### -AppPoolId
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AppPoolId parameter specifies the IIS application pool in which the virtual directory runs. We recommend that you leave this parameter at its default setting.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -99,9 +94,6 @@ Accept wildcard characters: False
```
### -BasicAuthentication
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
- $true: Basic authentication is enabled. This is the default value.
@@ -111,6 +103,7 @@ The BasicAuthentication parameter specifies whether Basic authentication is enab
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -120,9 +113,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -132,6 +122,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,9 +132,6 @@ Accept wildcard characters: False
```
### -DigestAuthentication
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
- $true: Digest authentication is enabled.
@@ -153,6 +141,7 @@ The DigestAuthentication parameter specifies whether Digest authentication is en
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -162,15 +151,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -180,9 +167,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionFlags
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
- None: This is the default setting.
@@ -195,6 +179,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -204,9 +189,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionSPNList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
- $null: This is the default value.
@@ -216,6 +198,7 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -225,9 +208,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionTokenChecking
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
@@ -240,6 +220,7 @@ The ExtendedProtectionTokenChecking parameter defines how you want to use Extend
Type: ExtendedProtectionTokenCheckingMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -249,9 +230,6 @@ Accept wildcard characters: False
```
### -ExternalUrl
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The ExternalUrl parameter specifies the URL used to connect to the virtual directory from outside the network firewall.
@@ -260,6 +238,7 @@ The ExternalUrl parameter specifies the URL used to connect to the virtual direc
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -269,9 +248,6 @@ Accept wildcard characters: False
```
### -InternalUrl
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The InternalUrl parameter specifies the URL used to connect to the virtual directory from inside the network firewall.
@@ -280,6 +256,7 @@ The InternalUrl parameter specifies the URL used to connect to the virtual direc
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -289,9 +266,6 @@ Accept wildcard characters: False
```
### -OAuthAuthentication
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
- $true: OAuth authentication is enabled. This is the default value.
@@ -301,6 +275,7 @@ The OAuthAuthentication parameter specifies whether OAuth authentication is enab
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -310,15 +285,13 @@ Accept wildcard characters: False
```
### -Path
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Path parameter specifies the file system path of the virtual directory. We recommend using this parameter only when you need to use a custom location for the virtual directory files. The default value is blank ($null), which indicates the default location is used.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -328,9 +301,6 @@ Accept wildcard characters: False
```
### -Role
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Role parameter species the configuration for the virtual directory. Valid values are:
- ClientAccess: Configure the virtual directory for the Client Access (frontend) services on the Mailbox server.
@@ -342,6 +312,7 @@ Client connections are proxied from the Client Access services to the backend se
Type: VirtualDirectoryRole
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -351,9 +322,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -365,6 +333,7 @@ The Server parameter specifies the Exchange server that hosts the virtual direct
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -374,15 +343,13 @@ Accept wildcard characters: False
```
### -WebSiteName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WebSiteName parameter specifies the name of the IIS website under which the virtual directory is created. You don't need to use this parameter to create the virtual directory under the default website.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -392,15 +359,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -410,9 +375,6 @@ Accept wildcard characters: False
```
### -WindowsAuthentication
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
- $true: Integrated Windows authentication is enabled. This is the default value.
@@ -422,6 +384,7 @@ The WindowsAuthentication parameter specifies whether Integrated Windows authent
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -431,9 +394,6 @@ Accept wildcard characters: False
```
### -WSSecurityAuthentication
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
- $true: WS-Security authentication is enabled. This is the default value.
@@ -443,6 +403,7 @@ The WSSecurityAuthentication parameter specifies whether WS-Security (Web Servic
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md b/exchange/exchange-ps/exchange/New-AvailabilityConfig.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md
rename to exchange/exchange-ps/exchange/New-AvailabilityConfig.md
index 1617b9203b..7019d149b7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md
+++ b/exchange/exchange-ps/exchange/New-AvailabilityConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-availabilityconfig
applicable: Exchange Online
+title: New-AvailabilityConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-availabilityconfig
-schema: 2.0.0
-title: New-AvailabilityConfig
+ms.reviewer:
---
# New-AvailabilityConfig
@@ -45,15 +44,13 @@ This example creates a new availability configuration to share free/busy informa
## PARAMETERS
### -AllowedTenantIds
-
-> Applicable: Exchange Online
-
The AllowedTenantIds parameter specifies the tenant ID values of Microsoft 365 organization that you want to share free/busy information with (for example, d6b0a40e-029b-43f2-9852-f3724f68ead9). You can specify multiple values separated by commas. A maximum of 25 values are allowed.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -63,9 +60,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -75,6 +69,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -84,15 +79,13 @@ Accept wildcard characters: False
```
### -OrgWideAccount
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SecurityPrincipalIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -102,15 +95,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md b/exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md
rename to exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md
index f41f532d23..4c31737bf7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md
+++ b/exchange/exchange-ps/exchange/New-AvailabilityReportOutage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-availabilityreportoutage
applicable: Exchange Server 2010
+title: New-AvailabilityReportOutage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-availabilityreportoutage
-schema: 2.0.0
-title: New-AvailabilityReportOutage
+ms.reviewer:
---
# New-AvailabilityReportOutage
@@ -46,15 +45,13 @@ This example creates a timed injected outage scoped to site Site1 on the selecte
## PARAMETERS
### -SiteName
-
-> Applicable: Exchange Server 2010
-
The SiteName parameter specifies the name of the Active Directory site to associate the outage report with.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: 1
@@ -64,15 +61,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Exchange Server 2010
-
The Comment parameter specifies why the outage was inserted.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -82,15 +77,13 @@ Accept wildcard characters: False
```
### -DowntimeMinutes
-
-> Applicable: Exchange Server 2010
-
The DowntimeMinutes parameter specifies the number of minutes of downtime to insert into the outage report.
```yaml
Type: Double
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -100,15 +93,13 @@ Accept wildcard characters: False
```
### -ReportDate
-
-> Applicable: Exchange Server 2010
-
The ReportDate parameter specifies the date to query for the outage report.
```yaml
Type: ExDateTime
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -118,9 +109,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -130,6 +118,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -139,9 +128,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -150,6 +136,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -159,15 +146,13 @@ Accept wildcard characters: False
```
### -ReportingDatabase
-
-> Applicable: Exchange Server 2010
-
The ReportingDatabase parameter specifies the name of the database on the reporting server.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -177,15 +162,13 @@ Accept wildcard characters: False
```
### -ReportingServer
-
-> Applicable: Exchange Server 2010
-
The ReportingServer parameter specifies the name of the reporting database server to connect to.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -195,15 +178,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md b/exchange/exchange-ps/exchange/New-CaseHoldPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md
rename to exchange/exchange-ps/exchange/New-CaseHoldPolicy.md
index a2a84309b5..87605314fc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md
+++ b/exchange/exchange-ps/exchange/New-CaseHoldPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-caseholdpolicy
applicable: Security & Compliance
+title: New-CaseHoldPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-caseholdpolicy
-schema: 2.0.0
-title: New-CaseHoldPolicy
+ms.reviewer:
---
# New-CaseHoldPolicy
@@ -20,7 +19,7 @@ Use the New-CaseHoldPolicy cmdlet to create new case hold policies in the Micros
> [!NOTE]
> After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. **If you don't create a rule for the policy, the hold won't be created, and content locations won't be placed on hold**.
>
-> Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to create multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. For information about the distribution status, see [Get-CaseHoldPolicy](https://learn.microsoft.com/powershell/module/exchangepowershell/get-caseholdpolicy).
+> Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to create multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. For information about the distribution status, see [Get-CaseHoldPolicy](https://learn.microsoft.com/powershell/module/exchange/get-caseholdpolicy).
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
@@ -56,15 +55,13 @@ Remember, after you create the policy, you need to create a rule for the policy
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies the unique name of the case hold policy. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -Case
-
-> Applicable: Security & Compliance
-
The Case parameter specifies the eDiscovery case that you want to associate with the case hold policy. You can use the following values to identify the eDiscovery case:
- Name
@@ -88,6 +82,7 @@ You can find these values by running the command: Get-ComplianceCase | Format-Ta
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -127,6 +117,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -136,9 +127,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Security & Compliance
-
The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are:
- $true: The policy is enabled. This is the default value.
@@ -148,6 +136,7 @@ The Enabled parameter specifies whether the policy is enabled or disabled. Valid
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -157,9 +146,6 @@ Accept wildcard characters: False
```
### -ExchangeLocation
-
-> Applicable: Security & Compliance
-
The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are:
- A mailbox
@@ -179,6 +165,7 @@ If no mailboxes are specified, then no mailboxes are placed on hold.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -188,9 +175,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -199,6 +183,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -208,15 +193,13 @@ Accept wildcard characters: False
```
### -PublicFolderLocation
-
-> Applicable: Security & Compliance
-
The PublicFolderLocation parameter specifies that you want to include all public folders in the case hold policy. You use the value All for this parameter.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -226,9 +209,6 @@ Accept wildcard characters: False
```
### -SharePointLocation
-
-> Applicable: Security & Compliance
-
The SharePointLocation parameter specifies the SharePoint and OneDrive sites to include. You identify a site by its URL value.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -239,6 +219,7 @@ Sites can't be added to the policy until they have been indexed. If no sites are
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -248,15 +229,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md b/exchange/exchange-ps/exchange/New-CaseHoldRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md
rename to exchange/exchange-ps/exchange/New-CaseHoldRule.md
index 917d74060d..c169c5dfff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md
+++ b/exchange/exchange-ps/exchange/New-CaseHoldRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-caseholdrule
applicable: Security & Compliance
+title: New-CaseHoldRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-caseholdrule
-schema: 2.0.0
-title: New-CaseHoldRule
+ms.reviewer:
---
# New-CaseHoldRule
@@ -55,15 +54,13 @@ This example places email messages received by the recipients between December 1
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the case hold rule. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter specifies the case hold policy that contains the rule. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -86,6 +80,7 @@ The Policy parameter specifies the case hold policy that contains the rule. You
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -95,15 +90,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -113,9 +106,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -125,6 +115,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -134,9 +125,6 @@ Accept wildcard characters: False
```
### -ContentMatchQuery
-
-> Applicable: Security & Compliance
-
The ContentMatchQuery parameter specifies a content search filter. Use this parameter to create a query-based hold so only the content that matches the specified search query is placed on hold.
This parameter uses a text search string or a query that's formatted by using the Keyword Query Language (KQL). For more information, see [Keyword Query Language (KQL) syntax reference](https://learn.microsoft.com/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference) and [Keyword queries and search conditions for eDiscovery](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions).
@@ -145,6 +133,7 @@ This parameter uses a text search string or a query that's formatted by using th
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -154,9 +143,6 @@ Accept wildcard characters: False
```
### -Disabled
-
-> Applicable: Security & Compliance
-
The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are:
- $true: The rule is disabled.
@@ -166,6 +152,7 @@ The Disabled parameter specifies whether the case hold rule is enabled or disabl
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -175,15 +162,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md b/exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md
rename to exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md
index 9cfa7a8d54..2f589a0ceb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/exchange/New-ClassificationRuleCollection.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-classificationrulecollection
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-ClassificationRuleCollection
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-classificationrulecollection
-schema: 2.0.0
-title: New-ClassificationRuleCollection
+ms.reviewer:
---
# New-ClassificationRuleCollection
@@ -46,9 +45,6 @@ This example imports the classification rule collection file C:\\My Documents\\E
## PARAMETERS
### -FileData
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FileData parameter specifies the classification rule collection file you want to import.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -57,6 +53,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -66,9 +63,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -80,6 +74,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -89,9 +84,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -100,6 +92,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -109,15 +102,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md b/exchange/exchange-ps/exchange/New-ClientAccessArray.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md
rename to exchange/exchange-ps/exchange/New-ClientAccessArray.md
index a81bd4b402..93bc940c38 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md
+++ b/exchange/exchange-ps/exchange/New-ClientAccessArray.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-clientaccessarray
applicable: Exchange Server 2010
+title: New-ClientAccessArray
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-clientaccessarray
-schema: 2.0.0
-title: New-ClientAccessArray
+ms.reviewer:
---
# New-ClientAccessArray
@@ -55,9 +54,6 @@ This example creates a Client Access array named China CAS Array with the FQDN v
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010
-
The Name parameter specifies the descriptive name of the Client Access array. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks ("). If the value contains spaces, you can't use the Name value to identify the Client Access array for the Get-ClientAccessArray, Remove-ClientAccessArray, or Set-ClientAccessArray cmdlets.
If you don't use this parameter, the default value is the host part of the Fqdn parameter value. For example, if the Fqdn value is casarray01.contoso.com, the default name value is casarray01.
@@ -66,6 +62,7 @@ If you don't use this parameter, the default value is the host part of the Fqdn
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: 1
@@ -75,15 +72,13 @@ Accept wildcard characters: False
```
### -Fqdn
-
-> Applicable: Exchange Server 2010
-
The Fqdn parameter specifies the fully qualified domain name of the Client Access array (for example, casarray01.contoso.com). This is the value that RPC over TCP clients use to connect to the Client Access servers in the array.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -93,9 +88,6 @@ Accept wildcard characters: False
```
### -Site
-
-> Applicable: Exchange Server 2010
-
The Site parameter specifies the Active Directory site that contains the Client Access array. You can use any value that uniquely identifies the site. For example:
- Name
@@ -108,6 +100,7 @@ To see a list of available sites, use the Get-ADSite cmdlet.
Type: AdSiteIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: True
Position: Named
@@ -117,9 +110,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -129,6 +119,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -138,15 +129,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -156,15 +145,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md b/exchange/exchange-ps/exchange/New-ClientAccessRule.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md
rename to exchange/exchange-ps/exchange/New-ClientAccessRule.md
index 38b6934b7f..af5e934438 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md
+++ b/exchange/exchange-ps/exchange/New-ClientAccessRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-clientaccessrule
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: New-ClientAccessRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-clientaccessrule
-schema: 2.0.0
-title: New-ClientAccessRule
+ms.reviewer:
---
# New-ClientAccessRule
@@ -92,15 +91,13 @@ This example creates a new client access rule named Block ActiveSync that blocks
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Name parameter specifies a unique name for the client access rule.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -110,15 +107,13 @@ Accept wildcard characters: False
```
### -Action
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Action parameter specifies the action for the client access rule. Valid values for this parameter are AllowAccess and DenyAccess.
```yaml
Type: ClientAccessRulesAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -128,9 +123,6 @@ Accept wildcard characters: False
```
### -AnyOfAuthenticationTypes
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection
-
This parameter is functional only in the cloud-based service.
The AnyOfAuthenticationTypes parameter specifies a condition for the client access rule that's based on the client's authentication type.
@@ -151,6 +143,7 @@ You can enter multiple values separated by commas. Don't use quotation marks.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -160,9 +153,6 @@ Accept wildcard characters: False
```
### -AnyOfClientIPAddressesOrRanges
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The AnyOfClientIPAddressesOrRanges parameter specifies a condition for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are:
- Single IP address: For example, 192.168.1.1 or 2001:DB8::2AA:FF:C0A8:640A.
@@ -177,6 +167,7 @@ For more information about IPv6 addresses and syntax, see this Exchange 2013 top
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -186,9 +177,6 @@ Accept wildcard characters: False
```
### -AnyOfProtocols
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The AnyOfProtocols parameter specifies a condition for the client access rule that's based on the client's protocol.
Valid values for this parameter are:
@@ -214,6 +202,7 @@ You can enter multiple values separated by commas. Don't use quotation marks.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -223,15 +212,13 @@ Accept wildcard characters: False
```
### -AnyOfSourceTcpPortNumbers
-
-> Applicable: Exchange Server 2013
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013
Required: False
Position: Named
@@ -241,9 +228,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -255,6 +239,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -264,9 +249,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -275,6 +257,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -284,15 +267,13 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Enabled parameter specifies whether the client access rule is enabled or disabled. Valid values for this parameter are $true or $false. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -302,9 +283,6 @@ Accept wildcard characters: False
```
### -ExceptAnyOfAuthenticationTypes
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection
-
This parameter is functional only in the cloud-based service.
The ExceptAnyOfAuthenticationTypes parameter specifies an exception for the client access rule that's based on the client's authentication type.
@@ -325,6 +303,7 @@ You can enter multiple values separated by commas. Don't use quotation marks.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -334,9 +313,6 @@ Accept wildcard characters: False
```
### -ExceptAnyOfClientIPAddressesOrRanges
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ExceptAnyOfClientIPAddressesOrRanges parameter specifies an exception for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are:
- Single IP address: For example, 192.168.1.1 or 2001:DB8::2AA:FF:C0A8:640A.
@@ -351,6 +327,7 @@ For more information about IPv6 addresses and syntax, see this Exchange 2013 top
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -360,9 +337,6 @@ Accept wildcard characters: False
```
### -ExceptAnyOfProtocols
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection
-
This parameter is functional only in the cloud-based service.
The ExceptAnyOfProtocols parameter specifies an exception for the client access rule that's based on the client's protocol.
@@ -388,6 +362,7 @@ You can enter multiple values separated by commas. Don't use quotation marks.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -397,15 +372,13 @@ Accept wildcard characters: False
```
### -ExceptAnyOfSourceTcpPortNumbers
-
-> Applicable: Exchange Server 2013
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013
Required: False
Position: Named
@@ -415,15 +388,13 @@ Accept wildcard characters: False
```
### -ExceptUserIsMemberOf
-
-> Applicable: Exchange Server 2013
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013
Required: False
Position: Named
@@ -433,9 +404,6 @@ Accept wildcard characters: False
```
### -ExceptUsernameMatchesAnyOfPatterns
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is functional only in the cloud-based service.
The ExceptUsernameMatchesAnyOfPatterns parameter specifies an exception for the client access rule that's based on the user's account name in the format `\` (for example, `contoso.com\jeff`). This parameter accepts text and the wildcard character (\*) (for example, `*jeff*`, but not `jeff*`). Non-alphanumeric characters don't require an escape character.
@@ -446,6 +414,7 @@ You can enter multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -455,9 +424,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules:
@@ -472,6 +438,7 @@ If you modify the priority value of a rule, the position of the rule in the list
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -481,9 +448,6 @@ Accept wildcard characters: False
```
### -Scope
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Scope parameter specifies the scope of the client access rule. Valid values are:
- Users: The rule only applies to end-user connections.
@@ -493,6 +457,7 @@ The Scope parameter specifies the scope of the client access rule. Valid values
Type: ClientAccessRulesScope
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -502,15 +467,13 @@ Accept wildcard characters: False
```
### -UserIsMemberOf
-
-> Applicable: Exchange Server 2013
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013
Required: False
Position: Named
@@ -520,9 +483,6 @@ Accept wildcard characters: False
```
### -UsernameMatchesAnyOfPatterns
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is functional only in the cloud-based service.
The UsernameMatchesAnyOfPatterns parameter specifies a condition for the client access rule that's based on the user's account name in the format `\` (for example, `contoso.com\jeff`). This parameter accepts text and the wildcard character (\*) (for example, `*jeff*`, but not `jeff*`). Non-alphanumeric characters don't require an escape character. This parameter does not work with the -AnyOfProtocols UniversalOutlook parameter.
@@ -533,6 +493,7 @@ You can enter multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -542,9 +503,6 @@ Accept wildcard characters: True
```
### -UserRecipientFilter
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
This parameter is functional only in the cloud-based service.
The UserRecipientFilter parameter specifies a condition for the client access rule that uses OPATH filter syntax to identify the user based on a limited set of recipient properties. Client Access Rules don't support the full list of available recipient properties.
@@ -584,6 +542,7 @@ For detailed information about OPATH filter syntax in Exchange, see [Additional
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -593,15 +552,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md b/exchange/exchange-ps/exchange/New-ComplianceCase.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md
rename to exchange/exchange-ps/exchange/New-ComplianceCase.md
index 28d59c54ab..6366bff3d0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md
+++ b/exchange/exchange-ps/exchange/New-ComplianceCase.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancecase
applicable: Security & Compliance
+title: New-ComplianceCase
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-compliancecase
-schema: 2.0.0
-title: New-ComplianceCase
+ms.reviewer:
---
# New-ComplianceCase
@@ -56,15 +55,13 @@ This example creates a new eDiscovery Premium case named Coho Case 03082020 and
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies the unique name of the compliance case. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -CaseType
-
-> Applicable: Security & Compliance
-
The CaseType parameter specifies the type of compliance case that you want to create. Valid values are:
- AdvancedEdiscovery: eDiscovery Premium cases are used to manage legal or other types of investigations.
@@ -93,6 +87,7 @@ The CaseType parameter specifies the type of compliance case that you want to cr
Type: ComplianceCaseType
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -102,9 +97,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -114,6 +106,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -123,15 +116,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Security & Compliance
-
The Description parameter specifies a description for the compliance case. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -141,15 +132,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -159,15 +148,13 @@ Accept wildcard characters: False
```
### -ExternalId
-
-> Applicable: Security & Compliance
-
The ExternalId parameter specifies an optional ID or external case number that you can associate with the new compliance case.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -177,15 +164,13 @@ Accept wildcard characters: False
```
### -SecondaryCaseType
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -195,15 +180,13 @@ Accept wildcard characters: False
```
### -SourceCaseType
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -213,15 +196,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md b/exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md
rename to exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md
index 175e4be26e..f1f5f46411 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md
+++ b/exchange/exchange-ps/exchange/New-ComplianceRetentionEvent.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-complianceretentionevent
applicable: Security & Compliance
+title: New-ComplianceRetentionEvent
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-complianceretentionevent
-schema: 2.0.0
-title: New-ComplianceRetentionEvent
+ms.reviewer:
---
# New-ComplianceRetentionEvent
@@ -56,15 +55,13 @@ This example creates a compliance retention event named Research Project Employe
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the compliance retention event. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -74,9 +71,6 @@ Accept wildcard characters: False
```
### -AssetId
-
-> Applicable: Security & Compliance
-
The AssetId parameter specifies the Property:Value pair found in the properties of SharePoint or OneDrive documents that's used for retention. For example:
- Product codes that you can use to retain content for only a specific product.
@@ -87,6 +81,7 @@ The AssetId parameter specifies the Property:Value pair found in the properties
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -96,15 +91,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -114,9 +107,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -126,6 +116,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -135,15 +126,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -153,9 +142,6 @@ Accept wildcard characters: False
```
### -EventDateTime
-
-> Applicable: Security & Compliance
-
The EventDateTime parameter specifies the date-time of the event.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -164,6 +150,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -173,9 +160,6 @@ Accept wildcard characters: False
```
### -EventTags
-
-> Applicable: Security & Compliance
-
The EventTags parameter specifies the GUID value of the labels that are associated with the compliance retention event. Run the following command to see the available GUID values: `Get-ComplianceTag | Format-Table Name,GUID`.
You can specify multiple values separated by commas.
@@ -184,6 +168,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -193,15 +178,13 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Security & Compliance
-
The EventType parameter specifies the GUID value of the event that will start the retention period for labels that use this event type. Run the following command to see the available GUID values: `Get-ComplianceRetentionEventType | Format-Table Name,GUID`.
```yaml
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -211,15 +194,13 @@ Accept wildcard characters: False
```
### -ExchangeAssetIdQuery
-
-> Applicable: Security & Compliance
-
The ExchangeAssetIdQuery parameter specifies the keywords that are used to scope Exchange content for the compliance retention event. For details, see [Keyword queries and search conditions for Content Search](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -229,15 +210,13 @@ Accept wildcard characters: False
```
### -PreviewOnly
-
-> Applicable: Security & Compliance
-
{{ Fill PreviewOnly Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -247,15 +226,13 @@ Accept wildcard characters: False
```
### -SharePointAssetIdQuery
-
-> Applicable: Security & Compliance
-
The SharePointAssetIdQuery parameter specifies one or more the Property:Value pairs that you've specified in the properties (also known as Columns) of SharePoint and OneDrive documents to scope the compliance retention event.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -265,15 +242,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEventType.md b/exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEventType.md
rename to exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md
index 6d4515cd3e..f8097fbf29 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEventType.md
+++ b/exchange/exchange-ps/exchange/New-ComplianceRetentionEventType.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-complianceretentioneventtype
applicable: Security & Compliance
+title: New-ComplianceRetentionEventType
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-complianceretentioneventtype
-schema: 2.0.0
-title: New-ComplianceRetentionEventType
+ms.reviewer:
---
# New-ComplianceRetentionEventType
@@ -44,15 +43,13 @@ This example creates a new retention event type name Fabrikam Project
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies the unique name of the retention event type. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -62,15 +59,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -80,9 +75,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -92,6 +84,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -101,15 +94,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md b/exchange/exchange-ps/exchange/New-ComplianceSearch.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md
rename to exchange/exchange-ps/exchange/New-ComplianceSearch.md
index dde0f3b69a..bb3b8def59 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md
+++ b/exchange/exchange-ps/exchange/New-ComplianceSearch.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancesearch
applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+title: New-ComplianceSearch
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-compliancesearch
-schema: 2.0.0
-title: New-ComplianceSearch
+ms.reviewer:
---
# New-ComplianceSearch
@@ -82,9 +81,6 @@ This example creates a new compliance search named AnnBeebe-InactiveMailbox that
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Name parameter specifies the name of the compliance search. If the value contains spaces, enclose the value in quotation marks.
Don't use spaces in the value of this parameter if you plan on using the Case parameter. If the Name parameter contains spaces, the value of the ExchangeLocation parameter is cleared when you use the Case parameter.
@@ -93,6 +89,7 @@ Don't use spaces in the value of this parameter if you plan on using the Case pa
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: True
Position: 1
@@ -102,9 +99,6 @@ Accept wildcard characters: False
```
### -AllowNotFoundExchangeLocationsEnabled
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The AllowNotFoundExchangeLocationsEnabled parameter specifies whether to include mailboxes other than regular user mailboxes in the compliance search. Valid values are:
- $true: The search doesn't try to validate the existence of the mailbox before proceeding. This value is required if you want to search mailboxes that don't resolve as regular mailboxes.
@@ -121,6 +115,7 @@ The mailbox types that are affected by the value of this parameter include:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -130,9 +125,6 @@ Accept wildcard characters: False
```
### -Case
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The Case parameter specifies the name of an eDiscovery Standard case to associate the new compliance search with. If the value contains spaces, enclose the value in quotation marks.
@@ -145,6 +137,7 @@ If the Name parameter contains spaces, the value of the ExchangeLocation paramet
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -154,9 +147,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -166,6 +156,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -175,9 +166,6 @@ Accept wildcard characters: False
```
### -ContentMatchQuery
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The ContentMatchQuery parameter specifies a content search filter.
This parameter uses a text search string or a query that's formatted by using the Keyword Query Language (KQL). For more information, see [Keyword Query Language (KQL) syntax reference](https://learn.microsoft.com/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference) and [Keyword queries and search conditions for eDiscovery](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions).
@@ -186,6 +174,7 @@ This parameter uses a text search string or a query that's formatted by using th
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -195,15 +184,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Description parameter specifies an optional description for the compliance search. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -213,9 +200,6 @@ Accept wildcard characters: False
```
### -ExchangeLocation
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The ExchangeLocation parameter specifies the mailboxes to include. Valid values are:
- A regular user mailbox. Including other types of mailboxes (for example, inactive mailboxes or Microsoft 365 guest users) is controlled by the AllowNotFoundExchangeLocationsEnabled parameter.
@@ -228,6 +212,7 @@ To specify a mailbox or distribution group, use the email address. You can speci
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -237,9 +222,6 @@ Accept wildcard characters: False
```
### -ExchangeLocationExclusion
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
This parameter is functional only in on-premises Exchange.
This parameter specifies the mailboxes to exclude when you use the value All for the ExchangeLocation parameter. Valid values are:
@@ -253,6 +235,7 @@ To specify a mailbox or distribution group, use the email address. You can speci
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -262,9 +245,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -273,6 +253,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -282,9 +263,6 @@ Accept wildcard characters: False
```
### -HoldNames
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The HoldNames parameter specifies that the content locations that have been placed on hold in the specified eDiscovery case will be searched. You use the value All for this parameter. You also need to specify the name of an eDiscovery case by using the Case parameter.
@@ -295,6 +273,7 @@ Also, if a content location was placed on a query-based case hold, only items th
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -304,15 +283,13 @@ Accept wildcard characters: False
```
### -IncludeOrgContent
-
-> Applicable: Security & Compliance
-
{{ Fill IncludeOrgContent Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -322,9 +299,6 @@ Accept wildcard characters: False
```
### -IncludeUserAppContent
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The IncludeUserAppContent parameter specifies that you want to search the cloud-based storage location for users who don't have a regular Microsoft 365 user account in your organization. These types of users include users without an Exchange Online license who use Office applications, Microsoft 365 guest users, and on-premises users whose identity is synchronized with your Microsoft 365 organization. Valid values are:
@@ -336,6 +310,7 @@ The IncludeUserAppContent parameter specifies that you want to search the cloud-
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -345,9 +320,6 @@ Accept wildcard characters: False
```
### -Language
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Language parameter specifies the language for the compliance search.
Valid input for this parameter is a supported culture code value from the Microsoft .NET Framework CultureInfo class. For example, da-DK for Danish or ja-JP for Japanese. For more information, see [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo).
@@ -356,6 +328,7 @@ Valid input for this parameter is a supported culture code value from the Micros
Type: CultureInfo
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -365,9 +338,6 @@ Accept wildcard characters: False
```
### -LogLevel
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -376,6 +346,7 @@ This parameter is reserved for internal Microsoft use.
Type: ComplianceJobLogLevel
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -385,9 +356,6 @@ Accept wildcard characters: False
```
### -PublicFolderLocation
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The PublicFolderLocation parameter specifies that you want to include all public folders in the search. You use the value All for this parameter.
@@ -396,6 +364,7 @@ The PublicFolderLocation parameter specifies that you want to include all public
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -405,9 +374,6 @@ Accept wildcard characters: False
```
### -RefinerNames
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -416,6 +382,7 @@ This parameter is reserved for internal Microsoft use.
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -425,9 +392,6 @@ Accept wildcard characters: False
```
### -SharePointLocation
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The SharePointLocation parameter specifies the SharePoint sites to include. You identify the site by its URL value, or you can use the value All to include all sites.
@@ -438,6 +402,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -447,9 +412,6 @@ Accept wildcard characters: False
```
### -SharePointLocationExclusion
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -458,6 +420,7 @@ This parameter is reserved for internal Microsoft use.
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -467,9 +430,6 @@ Accept wildcard characters: False
```
### -StatusMailRecipients
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
This parameter is reserved for internal Microsoft use.
@@ -478,6 +438,7 @@ This parameter is reserved for internal Microsoft use.
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -487,15 +448,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md b/exchange/exchange-ps/exchange/New-ComplianceSearchAction.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md
rename to exchange/exchange-ps/exchange/New-ComplianceSearchAction.md
index 0ed529ffc5..e2b6541d63 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/exchange/New-ComplianceSearchAction.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancesearchaction
applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+title: New-ComplianceSearchAction
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-compliancesearchaction
-schema: 2.0.0
-title: New-ComplianceSearchAction
+ms.reviewer:
---
# New-ComplianceSearchAction
@@ -142,9 +141,6 @@ This example exports the results returned by the content search named "Case 321
## PARAMETERS
### -SearchName
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The SearchName parameter specifies the name of the existing content search to associate with the content search action. You can specify multiple content searches separated by commas.
You can find the content search by running the command Get-ComplianceSearch | Format-Table -Auto Name,Status.
@@ -153,6 +149,7 @@ You can find the content search by running the command Get-ComplianceSearch | Fo
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: True
Position: 1
@@ -162,9 +159,6 @@ Accept wildcard characters: False
```
### -ActionName
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The ActionName parameter specifies a name for the content search action. You use this parameter only when you specify multiple content searches in the SearchName parameter.
@@ -173,6 +167,7 @@ The ActionName parameter specifies a name for the content search action. You use
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -182,9 +177,6 @@ Accept wildcard characters: False
```
### -ArchiveFormat
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
This parameter has been deprecated and is no longer used.
To specify the format for Exchange search results, use the ExchangeArchiveFormat parameter. To specify the format for SharePoint and OneDrive search results, use the SharePointArchiveFormat parameter.
@@ -193,6 +185,7 @@ To specify the format for Exchange search results, use the ExchangeArchiveFormat
Type: ComplianceExportArchiveFormat
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -202,9 +195,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -216,6 +206,7 @@ This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmat
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -225,9 +216,6 @@ Accept wildcard characters: False
```
### -EnableDedupe
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -236,6 +224,7 @@ This parameter is reserved for internal Microsoft use.
Type: Boolean
Parameter Sets: Export
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -246,8 +235,6 @@ Accept wildcard characters: False
### -ExchangeArchiveFormat
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
This parameter is functional only in the cloud-based service.
@@ -269,6 +256,7 @@ To specify the format for SharePoint and OneDrive search results, use the ShareP
Type: ComplianceExportArchiveFormat
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -278,9 +266,6 @@ Accept wildcard characters: False
```
### -Export
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
This parameter is functional only in the cloud-based service.
@@ -295,6 +280,7 @@ To only return the information about each detected item in a report, use the Rep
Type: SwitchParameter
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -304,9 +290,6 @@ Accept wildcard characters: False
```
### -FileTypeExclusionsForUnindexedItems
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
The FileTypeExclusionsForUnindexedItems specifies the file types to exclude because they can't be indexed. You can specify multiple values separated by commas.
@@ -315,6 +298,7 @@ The FileTypeExclusionsForUnindexedItems specifies the file types to exclude beca
Type: String[]
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -324,9 +308,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -335,6 +316,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -344,9 +326,6 @@ Accept wildcard characters: False
```
### -Format
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
In Security & Compliance PowerShell, this parameter requires the Export role. By default, this role is assigned only to the eDiscovery Manager role group.
The Format parameter specifies the format of the search results when you use the Export switch. Valid values are:
@@ -359,6 +338,7 @@ The Format parameter specifies the format of the search results when you use the
Type: ComplianceDataTransferFormat
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -368,15 +348,13 @@ Accept wildcard characters: False
```
### -IncludeCredential
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The IncludeCredential switch specifies whether to include the credential in the results. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -386,9 +364,6 @@ Accept wildcard characters: False
```
### -IncludeSharePointDocumentVersions
-
-> Applicable: Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
This parameter is available only in the cloud-based service.
@@ -402,6 +377,7 @@ The IncludeSharePointDocumentVersions parameter specifies whether to export prev
Type: Boolean
Parameter Sets: Export
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -411,15 +387,13 @@ Accept wildcard characters: False
```
### -JobOptions
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -429,9 +403,6 @@ Accept wildcard characters: False
```
### -NotifyEmail
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
In Security & Compliance PowerShell, this parameter requires the Export role. By default, this is assigned only to the eDiscovery Manager role group.
@@ -444,6 +415,7 @@ The recipient you specify is in the To: field of the message.
Type: String
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -453,9 +425,6 @@ Accept wildcard characters: False
```
### -NotifyEmailCC
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
In Security & Compliance PowerShell, this parameter requires the Export role. By default, this role is assigned only to the eDiscovery Manager role group.
@@ -468,6 +437,7 @@ The recipient you specify is in the Cc: field of the message.
Type: String
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -477,9 +447,6 @@ Accept wildcard characters: False
```
### -Preview
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
In Security & Compliance PowerShell, this parameter requires the Preview role. By default, this role is assigned only to the eDiscovery Manager role group.
The Preview switch specifies the action for the content search is to preview the results that match the search criteria. You don't need to specify a value with this switch.
@@ -488,6 +455,7 @@ The Preview switch specifies the action for the content search is to preview the
Type: SwitchParameter
Parameter Sets: Preview
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -497,9 +465,6 @@ Accept wildcard characters: False
```
### -Purge
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: In Security & Compliance PowerShell, this switch is available only in the Search and Purge role. By default, this role is assigned only to the Organization Management and Data Investigator role groups.
The Purge switch specifies the action for the content search is to remove items that match the search criteria. You don't need to specify a value with this switch.
@@ -516,6 +481,7 @@ The Purge switch specifies the action for the content search is to remove items
Type: SwitchParameter
Parameter Sets: Purge
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -525,9 +491,6 @@ Accept wildcard characters: False
```
### -PurgeType
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: In Security & Compliance PowerShell, this parameter is available only in the Search and Purge role. By default, this role is assigned only to the Organization Management and Data Investigator role groups.
The PurgeType parameter specifies how to remove items when the action is Purge. Valid values are:
@@ -539,6 +502,7 @@ The PurgeType parameter specifies how to remove items when the action is Purge.
Type: ComplianceDestroyType
Parameter Sets: Purge
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -548,15 +512,13 @@ Accept wildcard characters: False
```
### -ReferenceActionName
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -566,15 +528,13 @@ Accept wildcard characters: False
```
### -Region
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -584,9 +544,6 @@ Accept wildcard characters: False
```
### -Report
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
This parameter is functional only in the cloud-based service.
@@ -597,6 +554,7 @@ The Report switch specifies the action for the content search is to export a rep
Type: SwitchParameter
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -606,9 +564,6 @@ Accept wildcard characters: False
```
### -RetentionReport
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
The RetentionReport switch specifies the action for the content search is to export a retention report. You don't need to specify a value with this switch.
@@ -617,6 +572,7 @@ The RetentionReport switch specifies the action for the content search is to exp
Type: SwitchParameter
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -626,15 +582,13 @@ Accept wildcard characters: False
```
### -RetryOnError
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The RetryOnError switch specifies whether to retry the action on any items that failed without re-running the entire action all over again. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -644,9 +598,6 @@ Accept wildcard characters: False
```
### -Scenario
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
In Security & Compliance PowerShell, this parameter requires the Preview role. By default, this role is assigned only to the eDiscovery Manager role group.
The Scenario parameter specifies the scenario type. Valid values are:
@@ -662,6 +613,7 @@ The Scenario parameter specifies the scenario type. Valid values are:
Type: ComplianceSearchActionScenario
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -671,9 +623,6 @@ Accept wildcard characters: False
```
### -Scope
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
The Scope parameter specifies the items to include when the action is Export. Valid values are:
@@ -686,6 +635,7 @@ The Scope parameter specifies the items to include when the action is Export. Va
Type: ComplianceExportScope
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -695,9 +645,6 @@ Accept wildcard characters: False
```
### -SearchNames
-
-> Applicable: Security & Compliance
-
This parameter is available only in the cloud-based service.
The SearchNames parameter specifies the names of the existing content searches to associate with the content search action. You separate the content search names by commas.
@@ -708,6 +655,7 @@ You can find content search names by running the command Get-ComplianceSearch |
Type: String[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -717,9 +665,6 @@ Accept wildcard characters: False
```
### -SharePointArchiveFormat
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
This parameter is functional only in the cloud-based service.
@@ -738,6 +683,7 @@ To specify the format for Exchange search results, use the ExchangeArchiveFormat
Type: ComplianceExportArchiveFormat
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -747,9 +693,6 @@ Accept wildcard characters: False
```
### -ShareRootPath
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
**Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
@@ -760,6 +703,7 @@ This parameter is available only in on-premises Exchange.
Type: String
Parameter Sets: Export
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -769,15 +713,13 @@ Accept wildcard characters: False
```
### -Version
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -787,9 +729,6 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
@@ -798,6 +737,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md b/exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md
rename to exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md
index fb2266e405..cf258e62c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md
+++ b/exchange/exchange-ps/exchange/New-ComplianceSecurityFilter.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancesecurityfilter
applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+title: New-ComplianceSecurityFilter
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-compliancesecurityfilter
-schema: 2.0.0
-title: New-ComplianceSecurityFilter
+ms.reviewer:
---
# New-ComplianceSecurityFilter
@@ -76,9 +75,6 @@ This example prevents the user from performing any compliance search actions on
## PARAMETERS
### -Action
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Action parameter specifies that type of search action that the filter is applied to. Valid values are:
- Export: The filter is applied when exporting search results, or preparing them for analysis in eDiscovery Premium.
@@ -91,6 +87,7 @@ The Action parameter specifies that type of search action that the filter is app
Type: ComplianceSecurityFilterActionType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: True
Position: Named
@@ -100,15 +97,13 @@ Accept wildcard characters: False
```
### -FilterName
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The FilterName parameter specifies the name for the compliance security filter. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: True
Position: Named
@@ -118,9 +113,6 @@ Accept wildcard characters: False
```
### -Users
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Users parameter specifies the user who gets this filter applied to their searches. Valid values are:
- One or more users: Identify users by their alias or email address. You can specify multiple values separated by commas.
@@ -133,6 +125,7 @@ You can't specify distribution groups with this parameter.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: True
Position: Named
@@ -142,9 +135,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -154,6 +144,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -163,15 +154,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Description parameter specifies a description for the compliance security filter. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -181,9 +170,6 @@ Accept wildcard characters: False
```
### -Filters
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Filters parameter specifies the search criteria for the compliance security filter. The filters are applied to the users specified by the Users parameter. You can create three different types of filters:
- Mailbox filter: Specifies the mailboxes that can be searched by the assigned users. Valid syntax is `Mailbox_`, where `` is a mailbox property value. For example,`"Mailbox_CustomAttribute10 -eq 'OttawaUsers'"` allows users to only search mailboxes that have the value OttawaUsers in the CustomAttribute10 property. For a list of supported mailbox properties, see [Filterable properties for the RecipientFilter parameter](https://learn.microsoft.com/powershell/exchange/recipientfilter-properties).
@@ -198,6 +184,7 @@ You need to create a search permissions filter to explicitly prevent users from
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -207,9 +194,6 @@ Accept wildcard characters: False
```
### -Region
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The Region parameter specifies the satellite location for multi-geo tenants to conduct eDiscovery searches in. Valid values are:
- APC: Asia-Pacific
@@ -229,6 +213,7 @@ If you don't use this parameter in a multi-geo tenant, eDiscovery searches are p
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
@@ -238,15 +223,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md b/exchange/exchange-ps/exchange/New-ComplianceTag.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md
rename to exchange/exchange-ps/exchange/New-ComplianceTag.md
index e58199a8c7..9de8c0fca4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md
+++ b/exchange/exchange-ps/exchange/New-ComplianceTag.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-compliancetag
applicable: Security & Compliance
+title: New-ComplianceTag
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-compliancetag
-schema: 2.0.0
-title: New-ComplianceTag
+ms.reviewer:
---
# New-ComplianceTag
@@ -76,15 +75,13 @@ This example creates a new label named HR Content with the following settings:
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the label. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -94,15 +91,13 @@ Accept wildcard characters: False
```
### -PriorityCleanup
-
-> Applicable: Security & Compliance
-
{{ Fill PriorityCleanup Description }}
```yaml
Type: SwitchParameter
Parameter Sets: PriorityCleanup
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -112,9 +107,6 @@ Accept wildcard characters: False
```
### -RetentionAction
-
-> Applicable: Security & Compliance
-
The RetentionAction parameter specifies the action for the label. Valid values are:
- Delete
@@ -123,8 +115,9 @@ The RetentionAction parameter specifies the action for the label. Valid values a
```yaml
Type: String
-Parameter Sets: Default, PriorityCleanup
+Parameter Sets: PriorityCleanup
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -133,10 +126,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -RetentionDuration
+```yaml
+Type: String
+Parameter Sets: Default
+Aliases:
+Applicable: Security & Compliance
-> Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -RetentionDuration
The RetentionDuration parameter specifies the number of days to retain the content. Valid values are:
- A positive integer.
@@ -144,8 +147,9 @@ The RetentionDuration parameter specifies the number of days to retain the conte
```yaml
Type: Unlimited
-Parameter Sets: Default, PriorityCleanup
+Parameter Sets: PriorityCleanup
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -154,10 +158,20 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -RetentionType
+```yaml
+Type: Unlimited
+Parameter Sets: Default
+Aliases:
+Applicable: Security & Compliance
-> Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -RetentionType
The RetentionType parameter specifies whether the retention duration is calculated from the content creation date, tagged date, or last modification date. Valid values are:
- CreationAgeInDays
@@ -167,8 +181,9 @@ The RetentionType parameter specifies whether the retention duration is calculat
```yaml
Type: String
-Parameter Sets: Default, PriorityCleanup
+Parameter Sets: PriorityCleanup
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -177,16 +192,27 @@ Accept pipeline input: False
Accept wildcard characters: False
```
-### -AutoApprovalPeriod
+```yaml
+Type: String
+Parameter Sets: Default
+Aliases:
+Applicable: Security & Compliance
-> Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+### -AutoApprovalPeriod
{{ Fill AutoApprovalPeriod Description }}
```yaml
Type: System.Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -196,15 +222,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -214,15 +238,13 @@ Accept wildcard characters: False
```
### -ComplianceTagForNextStage
-
-> Applicable: Security & Compliance
-
{{ Fill ComplianceTagForNextStage Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -232,9 +254,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -244,6 +263,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -253,9 +273,6 @@ Accept wildcard characters: False
```
### -EventType
-
-> Applicable: Security & Compliance
-
The EventType specifies the retention rule that's associated with the label. You can use any value that uniquely identifies the rule. For example:
- Name
@@ -268,6 +285,7 @@ You can use the Get-RetentionComplianceRule cmdlet to view the available retenti
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -277,9 +295,6 @@ Accept wildcard characters: False
```
### -FilePlanProperty
-
-> Applicable: Security & Compliance
-
The FilePlanProperty parameter specifies the file plan properties to include in the label. To view the file plan property names that you need to use in this parameter, run the following commands:
- `Get-FilePlanPropertyAuthority | Format-List Name`
@@ -313,6 +328,7 @@ You use the second variable as the value for this parameter.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -322,9 +338,6 @@ Accept wildcard characters: False
```
### -FlowId
-
-> Applicable: Security & Compliance
-
**Note**: This parameter is currently in Preview, is not available in all organizations, and is subject to change.
The FlowId parameter specifies the Power Automate flow to run at the end of the retention period. A valid value for this parameter is the GUID value of the flow.
@@ -338,6 +351,7 @@ You can find the GUID value of the flow by using either of the following methods
Type: System.Guid
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -347,9 +361,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -358,6 +369,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -367,9 +379,6 @@ Accept wildcard characters: False
```
### -IsRecordLabel
-
-> Applicable: Security & Compliance
-
The IsRecordLabel parameter specifies whether the label is a record label. Valid values are:
- $true: The label is a record label. Once the label is applied to content, the label can't be removed.
@@ -379,6 +388,7 @@ The IsRecordLabel parameter specifies whether the label is a record label. Valid
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -388,15 +398,13 @@ Accept wildcard characters: False
```
### -IsRecordUnlockedAsDefault
-
-> Applicable: Security & Compliance
-
{{ Fill IsRecordUnlockedAsDefault Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -406,9 +414,6 @@ Accept wildcard characters: False
```
### -MultiStageReviewProperty
-
-> Applicable: Security & Compliance
-
The MultiStageReviewProperty parameter specifies the multi-stage review properties to include in the label. This parameter uses the following syntax:
`'{"MultiStageReviewSettings":[{"StageName":"Stage1","Reviewers":[reviewer1,reviewer2,...reviewerN]},{"StageName":"Stage2","Reviewers":[reviewer1,reviewer2,...reviewerN]},]}'`
@@ -423,6 +428,7 @@ This syntax is a JSON object that defines each review stage id, review stage nam
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -432,15 +438,13 @@ Accept wildcard characters: False
```
### -Notes
-
-> Applicable: Security & Compliance
-
The Notes parameter specifies additional information about the object. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -450,15 +454,13 @@ Accept wildcard characters: False
```
### -Regulatory
-
-> Applicable: Security & Compliance
-
{{ Fill Regulatory Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -468,15 +470,13 @@ Accept wildcard characters: False
```
### -ReviewerEmail
-
-> Applicable: Security & Compliance
-
The ReviewerEmail parameter specifies the email address of a reviewer for Delete and KeepAndDelete retention actions. You can specify multiple email addresses separated by commas.
```yaml
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -486,15 +486,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md b/exchange/exchange-ps/exchange/New-DataClassification.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md
rename to exchange/exchange-ps/exchange/New-DataClassification.md
index ef07895c85..ee21f6fc1a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md
+++ b/exchange/exchange-ps/exchange/New-DataClassification.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dataclassification
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-DataClassification
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dataclassification
-schema: 2.0.0
-title: New-DataClassification
+ms.reviewer:
---
# New-DataClassification
@@ -15,7 +14,7 @@ title: New-DataClassification
## SYNOPSIS
This cmdlet is functional only in on-premises Exchange.
-In Exchange Online, this cmdlet has been replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
+In Exchange Online, this cmdlet has been replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchange/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
Use the New-DataClassification cmdlet to create data classification rules that use document fingerprints.
@@ -58,15 +57,13 @@ This example creates a new data classification rule named "Contoso Employee-Cust
## PARAMETERS
### -Description
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Description parameter specifies a description for the data classification rule.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -76,15 +73,13 @@ Accept wildcard characters: False
```
### -Fingerprints
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
-The Fingerprints parameter specifies the byte-encoded files to use as document fingerprints. You can use multiple document fingerprints separated by commas. For instructions on how to import documents to use as templates for fingerprints, see [New-Fingerprint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-fingerprint) or the Examples section.
+The Fingerprints parameter specifies the byte-encoded files to use as document fingerprints. You can use multiple document fingerprints separated by commas. For instructions on how to import documents to use as templates for fingerprints, see [New-Fingerprint](https://learn.microsoft.com/powershell/module/exchange/new-fingerprint) or the Examples section.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -94,9 +89,6 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies a name for the data classification rule. The value must be less than 256 characters.
The value of this parameter is used in the Policy Tip that's presented to users in Outlook on the web.
@@ -105,6 +97,7 @@ The value of this parameter is used in the Policy Tip that's presented to users
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -114,15 +107,13 @@ Accept wildcard characters: False
```
### -ClassificationRuleCollectionIdentity
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: ClassificationRuleCollectionIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -132,9 +123,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -144,6 +132,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -153,15 +142,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -171,9 +158,6 @@ Accept wildcard characters: False
```
### -Locale
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Locale parameter specifies the language that's associated with the data classification rule.
Valid input for this parameter is a supported culture code value from the Microsoft .NET Framework CultureInfo class. For example, da-DK for Danish or ja-JP for Japanese. For more information, see [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo).
@@ -184,6 +168,7 @@ You can add additional language translations to the data classification rule by
Type: CultureInfo
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -193,15 +178,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md b/exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md
rename to exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md
index f042b32c86..fb8c9ddfeb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md
+++ b/exchange/exchange-ps/exchange/New-DataEncryptionPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.WebClient-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dataencryptionpolicy
applicable: Exchange Online
+title: New-DataEncryptionPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.WebClient-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dataencryptionpolicy
-schema: 2.0.0
-title: New-DataEncryptionPolicy
+ms.reviewer:
---
# New-DataEncryptionPolicy
@@ -50,15 +49,13 @@ This example creates a data encryption policy named US Mailboxes with the specif
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online
-
The Name parameter specifies the unique name for the data encryption policy. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: 1
@@ -68,9 +65,6 @@ Accept wildcard characters: False
```
### -AzureKeyIDs
-
-> Applicable: Exchange Online
-
The AzureKeyIDs parameter specifies the URI values of the Azure Key Vault keys to associate with the data encryption policy. You need to specify at least two Azure Key Vault keys separated by commas. For example, `"https://contosoWestUSvault01.vault.azure.net/keys/USA_Key_01","https://contosoEastUSvault01.vault.azure.net/keys/USA_Key_02"`.
To find the URI value for an Azure Key Vault, replace `` with the name of the vault, and run this command in Azure Rights Management PowerShell: `Get-AzureKeyVaultKey -VaultName ).id`. For more information, see [About Azure Key Vault](https://learn.microsoft.com/azure/key-vault/general/overview).
@@ -79,6 +73,7 @@ To find the URI value for an Azure Key Vault, replace `` with the nam
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -88,9 +83,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -100,6 +92,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -109,15 +102,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Exchange Online
-
The Description parameter specifies an optional description for the data encryption policy. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -127,15 +118,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -145,9 +134,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online
-
The Enabled parameter enables or disable the data encryption policy. Valid values are:
- $true: The policy is enabled. This is the default value.
@@ -157,6 +143,7 @@ The Enabled parameter enables or disable the data encryption policy. Valid value
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -166,15 +153,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md
rename to exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md
index e5d42b21af..13c5232ad5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-databaseavailabilitygroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-DatabaseAvailabilityGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-databaseavailabilitygroup
-schema: 2.0.0
-title: New-DatabaseAvailabilityGroup
+ms.reviewer:
---
# New-DatabaseAvailabilityGroup
@@ -82,15 +81,13 @@ This example creates a DAG named DAG3. DAG3 is configured to use SERVER1 for the
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies a unique name for the new DAG of up to 15 characters. The name you use must not conflict with any computer name in the organization.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -100,15 +97,13 @@ Accept wildcard characters: False
```
### -ActivityState
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: ActivityStateOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -118,9 +113,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -130,6 +122,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -139,15 +132,13 @@ Accept wildcard characters: False
```
### -DagConfiguration
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: DatabaseAvailabilityGroupConfigurationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -157,15 +148,13 @@ Accept wildcard characters: False
```
### -DatabaseAvailabilityGroupIpAddresses
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DatabaseAvailabilityGroupIpAddresses parameter specifies one or more static IPv4 addresses to the DAG when a Mailbox server is added to a DAG. If you specify the value Any or 0.0.0.0, the system attempts to lease one or more IPv4 addresses from a DHCP server to assign to the DAG. If you don't use this parameter, or if you specify the value 255.255.255.255 or None, the DAG is created without a cluster administrative access point.
```yaml
Type: IPAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -175,15 +164,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -193,9 +180,6 @@ Accept wildcard characters: False
```
### -FileSystem
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The FileSystem parameter specifies the file system that's used for the DAG. Valid values are:
- NTFS
@@ -205,6 +189,7 @@ The FileSystem parameter specifies the file system that's used for the DAG. Vali
Type: FileSystemMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -214,15 +199,13 @@ Accept wildcard characters: False
```
### -ThirdPartyReplication
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ThirdPartyReplication parameter specifies to configure and enable a DAG to use non-Microsoft replication that leverages the Exchange Third Party Replication API instead of the built-in continuous replication. Valid values are Enabled and Disabled. After this mode is enabled, it can't be changed.
```yaml
Type: ThirdPartyReplicationMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -232,15 +215,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -250,15 +231,13 @@ Accept wildcard characters: False
```
### -WitnessDirectory
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WitnessDirectory parameter specifies the name of the directory on the witness server used to store file share witness data. The directory and share should be hosted on an Exchange server other than any of the Mailbox servers in the DAG. This allows an Exchange administrator to maintain operational control over the directory. The specified directory can't be used by any other DAGs, or used for any purpose other than for the witness server. If you don't use this parameter, the default witness directory is used.
```yaml
Type: NonRootLocalLongFullPath
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -268,15 +247,13 @@ Accept wildcard characters: False
```
### -WitnessServer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WitnessServer parameter specifies the name of a server used as a quorum witness when the DAG contains an even number of members. The specified server can't be a member of the DAG that's configured to use it. A stand-alone Mailbox server, or a Mailbox server in another DAG is recommended.
```yaml
Type: FileShareWitnessServerName
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md
similarity index 85%
rename from exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md
rename to exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md
index 8363b20c66..cdf95fa60f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/exchange/New-DatabaseAvailabilityGroupNetwork.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-databaseavailabilitygroupnetwork
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-DatabaseAvailabilityGroupNetwork
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-databaseavailabilitygroupnetwork
-schema: 2.0.0
-title: New-DatabaseAvailabilityGroupNetwork
+ms.reviewer:
---
# New-DatabaseAvailabilityGroupNetwork
@@ -48,15 +47,13 @@ This example creates the DAG network DAG1Repl in the DAG DAG1. A subnet of 10.0.
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies the name of the DAG network being created.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -66,15 +63,13 @@ Accept wildcard characters: False
```
### -DatabaseAvailabilityGroup
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DatabaseAvailabilityGroup parameter specifies the name of the DAG that'll use the network being created.
```yaml
Type: DatabaseAvailabilityGroupIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 2
@@ -84,9 +79,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -96,6 +88,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -105,15 +98,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Description parameter specifies an optional description of up to 256 characters for the DAG network being created.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -123,15 +114,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,15 +130,13 @@ Accept wildcard characters: False
```
### -IgnoreNetwork
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IgnoreNetwork parameter excludes the DAG network from use by the DAG.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -159,15 +146,13 @@ Accept wildcard characters: False
```
### -ReplicationEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReplicationEnabled parameter specifies whether the DAG network being created is enabled for continuous replication.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -177,15 +162,13 @@ Accept wildcard characters: False
```
### -Subnets
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Subnets parameter specifies the subnets for the DAG network being created.
```yaml
Type: DatabaseAvailabilityGroupSubnetId[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -195,15 +178,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md b/exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md
rename to exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md
index 8727a41a18..42534c6c9d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/exchange/New-DeliveryAgentConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-deliveryagentconnector
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-DeliveryAgentConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-deliveryagentconnector
-schema: 2.0.0
-title: New-DeliveryAgentConnector
+ms.reviewer:
---
# New-DeliveryAgentConnector
@@ -63,15 +62,13 @@ The address space for the connector is c=US;a=Fabrikam;p=Contoso.
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies the name of this delivery agent connector. The value for the Name parameter can't exceed 64 characters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -81,15 +78,13 @@ Accept wildcard characters: False
```
### -AddressSpaces
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AddressSpaces parameter specifies the domain names that the delivery agent connector is responsible for. The complete syntax for entering an address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. Enclose each address space in quotation marks (").
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -99,15 +94,13 @@ Accept wildcard characters: False
```
### -DeliveryProtocol
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DeliveryProtocol parameter specifies the communication protocol that determines which delivery agents are responsible for servicing the connector.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -117,15 +110,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -135,9 +126,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -147,6 +135,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -156,9 +145,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -167,6 +153,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -176,9 +163,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Enabled parameter specifies whether the delivery agent connector is enabled.
The default value is $true.
@@ -187,6 +171,7 @@ The default value is $true.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -196,15 +181,13 @@ Accept wildcard characters: False
```
### -IsScopedConnector
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IsScopedConnector parameter specifies the availability of the connector to other Mailbox servers. If the value of this parameter is $false, the connector can be used by all Mailbox servers in your organization. If the value of this parameter is $true, the connector can only be used by Mailbox servers in the same Active Directory site. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -214,15 +197,13 @@ Accept wildcard characters: False
```
### -MaxConcurrentConnections
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MaxConcurrentConnections parameter specifies the maximum number of concurrent connections this connector accepts from a specific IP address. The default value is 5.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -232,9 +213,6 @@ Accept wildcard characters: False
```
### -MaxMessageSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MaxMessageSize parameter specifies the maximum size of a message that's allowed to pass through this connector. When you enter a value, qualify the value with one of the following units:
- B (bytes)
@@ -248,6 +226,7 @@ Unqualified values are treated as bytes. The valid input range for this paramete
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -257,15 +236,13 @@ Accept wildcard characters: False
```
### -MaxMessagesPerConnection
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MaxMessagesPerConnection parameter specifies the maximum number of messages this connector accepts per connection. The connector terminates the connection after this limit is reached, and the sending server has to initiate a new connection to send more messages. The default value is 20.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -275,9 +252,6 @@ Accept wildcard characters: False
```
### -SourceTransportServers
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SourceTransportServers parameter specifies the list of Mailbox servers that host this connector. You can specify more than one server by separating their names with commas.
By default, only the local server on which the command is executed is added to this parameter.
@@ -286,6 +260,7 @@ By default, only the local server on which the command is executed is added to t
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -295,15 +270,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md
rename to exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md
index c39103379a..b8386092bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md
+++ b/exchange/exchange-ps/exchange/New-DeviceConditionalAccessPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconditionalaccesspolicy
applicable: Security & Compliance
+title: New-DeviceConditionalAccessPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-deviceconditionalaccesspolicy
-schema: 2.0.0
-title: New-DeviceConditionalAccessPolicy
+ms.reviewer:
---
# New-DeviceConditionalAccessPolicy
@@ -55,15 +54,13 @@ This example creates a new mobile device conditional access policy named Human R
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the policy. If the value contains spaces, enclose the value in double quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -91,9 +86,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -103,6 +95,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -112,9 +105,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Security & Compliance
-
The Enabled parameter specifies whether the policy is enabled. Valid values are:
- $true: The policy is enabled. This is the default value.
@@ -124,6 +114,7 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -133,9 +124,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -144,6 +132,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -153,15 +142,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md b/exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md
rename to exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md
index 1b89079368..102c007035 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md
+++ b/exchange/exchange-ps/exchange/New-DeviceConditionalAccessRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconditionalaccessrule
applicable: Security & Compliance
+title: New-DeviceConditionalAccessRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-deviceconditionalaccessrule
-schema: 2.0.0
-title: New-DeviceConditionalAccessRule
+ms.reviewer:
---
# New-DeviceConditionalAccessRule
@@ -104,9 +103,6 @@ This example creates a new mobile device conditional access rule with the follow
## PARAMETERS
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter specifies the mobile device conditional access policy that this rule is associated with. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -117,6 +113,7 @@ The Policy parameter specifies the mobile device conditional access policy that
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -126,9 +123,6 @@ Accept wildcard characters: False
```
### -TargetGroups
-
-> Applicable: Security & Compliance
-
The TargetGroups parameter specifies the security groups that this rule applies to. This parameter uses the GUID value of the group. To find this GUID value, run the command Get-Group | Format-Table Name,GUID.
You can specify multiple groups separated by commas.
@@ -137,6 +131,7 @@ You can specify multiple groups separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -146,9 +141,6 @@ Accept wildcard characters: False
```
### -AccountName
-
-> Applicable: Security & Compliance
-
The AccountName parameter specifies the account name. Valid values for this parameter are:
- A text value.
@@ -158,6 +150,7 @@ The AccountName parameter specifies the account name. Valid values for this para
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -167,9 +160,6 @@ Accept wildcard characters: False
```
### -AccountUserName
-
-> Applicable: Security & Compliance
-
The AccountUserName parameter specifies the account user name. Valid values for this parameter are:
- A text value.
@@ -179,6 +169,7 @@ The AccountUserName parameter specifies the account user name. Valid values for
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -188,9 +179,6 @@ Accept wildcard characters: False
```
### -AllowAppStore
-
-> Applicable: Security & Compliance
-
The AllowAppStore parameter specifies whether to allow access to the app store on devices. Valid values for this parameter are:
- $true: Access to the app store is allowed.
@@ -206,6 +194,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -215,9 +204,6 @@ Accept wildcard characters: False
```
### -AllowAssistantWhileLocked
-
-> Applicable: Security & Compliance
-
The AllowAssistantWhileLocked parameter specifies whether to allow the use of the voice assistant while devices are locked. Valid values for this parameter are:
- $true: The voice assistant can be used while devices are locked.
@@ -230,6 +216,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -239,9 +226,6 @@ Accept wildcard characters: False
```
### -AllowConvenienceLogon
-
-> Applicable: Security & Compliance
-
The AllowConvenienceLogon parameter specifies whether to allow convenience logons on devices. Valid values for this parameter are:
- $true: Convenience logons are allowed.
@@ -254,6 +238,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -263,9 +248,6 @@ Accept wildcard characters: False
```
### -AllowDiagnosticSubmission
-
-> Applicable: Security & Compliance
-
The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic submissions from devices. Valid values for this parameter are:
- $true: Diagnostic submissions are allowed.
@@ -282,6 +264,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -291,9 +274,6 @@ Accept wildcard characters: False
```
### -AllowiCloudBackup
-
-> Applicable: Security & Compliance
-
The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup from devices. Valid values for this parameter are:
- $true: iCloud Backup is allowed.
@@ -309,6 +289,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -318,9 +299,6 @@ Accept wildcard characters: False
```
### -AllowiCloudDocSync
-
-> Applicable: Security & Compliance
-
The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documents & Data sync on devices. Valid values for this parameter are:
- $true: iCloud Documents & Data sync is allowed.
@@ -336,6 +314,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -345,9 +324,6 @@ Accept wildcard characters: False
```
### -AllowiCloudPhotoSync
-
-> Applicable: Security & Compliance
-
The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photos sync on devices. Valid values for this parameter are:
- $true: iCloud Photos sync is allowed.
@@ -363,6 +339,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -372,9 +349,6 @@ Accept wildcard characters: False
```
### -AllowJailbroken
-
-> Applicable: Security & Compliance
-
The AllowJailbroken parameter specifies whether to allow access to your organization by jailbroken or rooted devices.
- $true: Jailbroken devices are allowed.
@@ -390,6 +364,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -399,9 +374,6 @@ Accept wildcard characters: False
```
### -AllowPassbookWhileLocked
-
-> Applicable: Security & Compliance
-
The AllowPassbookWhileLocked parameter specifies whether to allow the use of Apple Passbook while devices are locked. Valid values for this parameter are:
- $true: Passbook is available while devices are locked.
@@ -414,6 +386,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -423,9 +396,6 @@ Accept wildcard characters: False
```
### -AllowScreenshot
-
-> Applicable: Security & Compliance
-
The AllowScreenshot parameter specifies whether to allow screenshots on devices. Valid values for this parameter are:
- $true: Screenshots are allowed.
@@ -441,6 +411,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -450,9 +421,6 @@ Accept wildcard characters: False
```
### -AllowSimplePassword
-
-> Applicable: Security & Compliance
-
The AllowSimplePassword parameter specifies whether to allow simple or non-complex passwords on devices. Valid values for this parameter are:
- $true: Simple passwords are allowed.
@@ -469,6 +437,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -478,9 +447,6 @@ Accept wildcard characters: False
```
### -AllowVideoConferencing
-
-> Applicable: Security & Compliance
-
The AllowVideoConferencing parameter specifies whether to allow video conferencing on devices. Valid values for this parameter are:
- $true: Video conferencing is allowed.
@@ -493,6 +459,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -502,9 +469,6 @@ Accept wildcard characters: False
```
### -AllowVoiceAssistant
-
-> Applicable: Security & Compliance
-
The AllowVoiceAssistant parameter specifies whether to allow using the voice assistant on devices. Valid values for this parameter are:
- $true: The voice assistant is allowed.
@@ -517,6 +481,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -526,9 +491,6 @@ Accept wildcard characters: False
```
### -AllowVoiceDialing
-
-> Applicable: Security & Compliance
-
The AllowVoiceDialing parameter specifies whether to allow voice-activated telephone dialing. Valid values for this parameter are:
- $true: Voice dialing is allowed.
@@ -541,6 +503,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -550,9 +513,6 @@ Accept wildcard characters: False
```
### -AntiVirusSignatureStatus
-
-> Applicable: Security & Compliance
-
The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are:
- An integer.
@@ -564,6 +524,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Int64
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -573,9 +534,6 @@ Accept wildcard characters: False
```
### -AntiVirusStatus
-
-> Applicable: Security & Compliance
-
The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are:
- An integer.
@@ -587,6 +545,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Int64
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -596,9 +555,6 @@ Accept wildcard characters: False
```
### -AppsRating
-
-> Applicable: Security & Compliance
-
The AppsRating parameter species the maximum or most restrictive rating of apps that are allowed on devices. Valid values for this parameter are:
- AllowAll
@@ -614,6 +570,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: CARatingAppsEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -623,9 +580,6 @@ Accept wildcard characters: False
```
### -AutoUpdateStatus
-
-> Applicable: Security & Compliance
-
The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are:
- AutomaticCheckForUpdates
@@ -641,6 +595,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: CAAutoUpdateStatusEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -650,9 +605,6 @@ Accept wildcard characters: False
```
### -BluetoothEnabled
-
-> Applicable: Security & Compliance
-
The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth on devices. Valid values for this parameter are:
- $true: Bluetooth is enabled.
@@ -665,6 +617,7 @@ This setting is available only on Windows Phone 8.1 devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -674,9 +627,6 @@ Accept wildcard characters: False
```
### -CameraEnabled
-
-> Applicable: Security & Compliance
-
The CameraEnabled parameter specifies whether to enable or disable cameras on devices. Valid values for this parameter are:
- $true: Cameras are enabled.
@@ -693,6 +643,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -702,9 +653,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -714,6 +662,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -723,15 +672,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -741,9 +688,6 @@ Accept wildcard characters: False
```
### -EmailAddress
-
-> Applicable: Security & Compliance
-
The EmailAddress parameter specifies the email address. Valid values are:
- An email address: For example, julia@contoso.com.
@@ -753,6 +697,7 @@ The EmailAddress parameter specifies the email address. Valid values are:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -762,9 +707,6 @@ Accept wildcard characters: False
```
### -EnableRemovableStorage
-
-> Applicable: Security & Compliance
-
The EnableRemovableStorage parameter specifies whether removable storage can be used by devices. Valid values for this parameter are:
- $true: Removable storage can be used.
@@ -777,6 +719,7 @@ This setting is available only on Windows Phone 8.1 devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -786,9 +729,6 @@ Accept wildcard characters: False
```
### -ExchangeActiveSyncHost
-
-> Applicable: Security & Compliance
-
The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are:
- A text value.
@@ -798,6 +738,7 @@ The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Val
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -807,9 +748,6 @@ Accept wildcard characters: False
```
### -FirewallStatus
-
-> Applicable: Security & Compliance
-
The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are:
- Required
@@ -821,6 +759,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Required
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -830,9 +769,6 @@ Accept wildcard characters: False
```
### -ForceAppStorePassword
-
-> Applicable: Security & Compliance
-
The ForceAppStorePassword parameter specifies whether to require a password to use the app store on devices. Valid values for this parameter are:
- $true: App store passwords are required.
@@ -845,6 +781,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -854,9 +791,6 @@ Accept wildcard characters: False
```
### -ForceEncryptedBackup
-
-> Applicable: Security & Compliance
-
The ForceEncryptedBackup parameter specifies whether to force encrypted backups for devices. Valid values for this parameter are:
- $true: Encrypted backups are required.
@@ -872,6 +806,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -881,9 +816,6 @@ Accept wildcard characters: False
```
### -MaxPasswordAttemptsBeforeWipe
-
-> Applicable: Security & Compliance
-
The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are:
- An integer.
@@ -900,6 +832,7 @@ This setting is available on the following types of devices:
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -909,9 +842,6 @@ Accept wildcard characters: False
```
### -MaxPasswordGracePeriod
-
-> Applicable: Security & Compliance
-
The MaxPasswordGracePeriod parameter specifies the length of time users are allowed to reset expired passwords on devices.
This setting is available only on Apple iOS 6+ devices.
@@ -922,6 +852,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: TimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -931,9 +862,6 @@ Accept wildcard characters: False
```
### -MoviesRating
-
-> Applicable: Security & Compliance
-
The MoviesRating parameter species the maximum or most restrictive rating of movies that are allowed on devices. You specify the country/region rating system to use with the RegionRatings parameter.
Valid values for the MoviesRating parameter are:
@@ -1024,6 +952,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: CARatingMovieEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1033,9 +962,6 @@ Accept wildcard characters: False
```
### -PasswordComplexity
-
-> Applicable: Security & Compliance
-
The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are:
- An integer.
@@ -1045,6 +971,7 @@ The PasswordComplexity parameter specifies the password complexity. Valid values
Type: Int64
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1054,9 +981,6 @@ Accept wildcard characters: False
```
### -PasswordExpirationDays
-
-> Applicable: Security & Compliance
-
The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are:
- An integer.
@@ -1073,6 +997,7 @@ This setting is available on the following types of devices:
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1082,9 +1007,6 @@ Accept wildcard characters: False
```
### -PasswordHistoryCount
-
-> Applicable: Security & Compliance
-
The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are:
- An integer.
@@ -1101,6 +1023,7 @@ This setting is available on the following types of devices:
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1110,9 +1033,6 @@ Accept wildcard characters: False
```
### -PasswordMinComplexChars
-
-> Applicable: Security & Compliance
-
The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are:
- An integer.
@@ -1122,6 +1042,7 @@ The PasswordMinComplexChars parameter specifies the minimum number of complex ch
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1131,9 +1052,6 @@ Accept wildcard characters: False
```
### -PasswordMinimumLength
-
-> Applicable: Security & Compliance
-
The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are:
- An integer.
@@ -1150,6 +1068,7 @@ This setting is available on the following types of devices:
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1159,9 +1078,6 @@ Accept wildcard characters: False
```
### -PasswordQuality
-
-> Applicable: Security & Compliance
-
The PasswordQuality parameter specifies the minimum password quality rating that's required for device passwords. Password quality is a numeric scale that indicates the security and complexity of the password. A higher quality value indicates a more secure password.
Valid values for this parameter are:
@@ -1175,6 +1091,7 @@ This setting is available only on Android 4+ devices.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1184,9 +1101,6 @@ Accept wildcard characters: False
```
### -PasswordRequired
-
-> Applicable: Security & Compliance
-
The PasswordRequired parameter specifies whether a password is required to access devices. Valid values for this parameter are:
- $true: Device passwords are required.
@@ -1203,6 +1117,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1212,9 +1127,6 @@ Accept wildcard characters: False
```
### -PasswordTimeout
-
-> Applicable: Security & Compliance
-
The PasswordTimeout parameter specifies the length of time that devices can be inactive before a password is required to reactivate them.
This setting is available on the following types of devices:
@@ -1230,6 +1142,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: TimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1239,9 +1152,6 @@ Accept wildcard characters: False
```
### -PhoneMemoryEncrypted
-
-> Applicable: Security & Compliance
-
The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on devices. Valid values for this parameter are:
- $true: Memory is encrypted.
@@ -1257,6 +1167,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1266,9 +1177,6 @@ Accept wildcard characters: False
```
### -RegionRatings
-
-> Applicable: Security & Compliance
-
The RegionRatings parameter specifies the rating system (country/region) to use for movie and television ratings with the MoviesRating and TVShowsRating parameters.
Valid values for the RegionRating parameter are:
@@ -1290,6 +1198,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: CARatingRegionEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1299,9 +1208,6 @@ Accept wildcard characters: False
```
### -RequireEmailProfile
-
-> Applicable: Security & Compliance
-
The RequireEmailProfile parameter specifies whether an email profile is required on devices. Valid values for this parameter are:
- $true: An email profile is required. This value is required for selective wipe on iOS devices.
@@ -1312,6 +1218,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1321,9 +1228,6 @@ Accept wildcard characters: False
```
### -SmartScreenEnabled
-
-> Applicable: Security & Compliance
-
The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen on devices. Valid values for this parameter are:
- $true: SmartScreen is enabled.
@@ -1336,6 +1240,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1345,9 +1250,6 @@ Accept wildcard characters: False
```
### -SystemSecurityTLS
-
-> Applicable: Security & Compliance
-
The SystemSecurityTLS parameter specifies whether TLS encryption is used on devices. Valid values for this parameter are:
- $true: TLS encryption is used.
@@ -1360,6 +1262,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1369,9 +1272,6 @@ Accept wildcard characters: False
```
### -TVShowsRating
-
-> Applicable: Security & Compliance
-
The TVShowsRating parameter species the maximum or most restrictive rating of television shows that are allowed on devices. You specify the country/region rating system to use with the RegionRatings parameter.
Valid values for the TVShowsRating parameter are:
@@ -1451,6 +1351,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: CARatingTvShowEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1460,9 +1361,6 @@ Accept wildcard characters: False
```
### -UserAccountControlStatus
-
-> Applicable: Security & Compliance
-
The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are:
- $null (blank): The setting isn't configured. This is the default value.
@@ -1477,6 +1375,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: CAUserAccountControlStatusEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1486,15 +1385,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1504,9 +1401,6 @@ Accept wildcard characters: False
```
### -WLANEnabled
-
-> Applicable: Security & Compliance
-
The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid values for this parameter are:
- $true: Wi-Fi is enabled.
@@ -1519,6 +1413,7 @@ This setting is available only on Microsoft Windows Phone 8.1 devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1528,9 +1423,6 @@ Accept wildcard characters: False
```
### -WorkFoldersSyncUrl
-
-> Applicable: Security & Compliance
-
The WorkFoldersSyncUrl parameter specifies the URL that's used to synchronize company data on devices.
Valid input for this parameter a URL. For example, `https://workfolders.contoso.com`.
@@ -1541,6 +1433,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md b/exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md
rename to exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md
index f3e3e885f1..67e19df788 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md
+++ b/exchange/exchange-ps/exchange/New-DeviceConfigurationPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconfigurationpolicy
applicable: Security & Compliance
+title: New-DeviceConfigurationPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-deviceconfigurationpolicy
-schema: 2.0.0
-title: New-DeviceConfigurationPolicy
+ms.reviewer:
---
# New-DeviceConfigurationPolicy
@@ -55,15 +54,13 @@ This example creates a new mobile device configuration policy named Engineering
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the policy. If the value contains spaces, enclose the value in double quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -73,15 +70,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -91,9 +86,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -103,6 +95,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -112,9 +105,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Security & Compliance
-
The Enabled parameter specifies whether the policy is enabled. Valid values are:
- $true: The policy is enabled. This is the default value.
@@ -124,6 +114,7 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -133,9 +124,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -144,6 +132,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -153,15 +142,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md b/exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md
rename to exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md
index 47cb277d91..e4505ceb8f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md
+++ b/exchange/exchange-ps/exchange/New-DeviceConfigurationRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-deviceconfigurationrule
applicable: Security & Compliance
+title: New-DeviceConfigurationRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-deviceconfigurationrule
-schema: 2.0.0
-title: New-DeviceConfigurationRule
+ms.reviewer:
---
# New-DeviceConfigurationRule
@@ -103,9 +102,6 @@ This example creates a new mobile device configuration rule with the following s
## PARAMETERS
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter specifies the mobile device configuration policy that this rule is associated with. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -116,6 +112,7 @@ The Policy parameter specifies the mobile device configuration policy that this
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -125,9 +122,6 @@ Accept wildcard characters: False
```
### -TargetGroups
-
-> Applicable: Security & Compliance
-
The TargetGroups parameter specifies the security groups that this rule applies to. This parameter uses the GUID value of the group. To find this GUID value, run the command Get-Group | Format-Table Name,GUID.
You can specify multiple groups separated by commas.
@@ -136,6 +130,7 @@ You can specify multiple groups separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -145,9 +140,6 @@ Accept wildcard characters: False
```
### -AccountName
-
-> Applicable: Security & Compliance
-
The AccountName parameter specifies the account name. Valid values for this parameter are:
- A text value.
@@ -157,6 +149,7 @@ The AccountName parameter specifies the account name. Valid values for this para
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -166,9 +159,6 @@ Accept wildcard characters: False
```
### -AccountUserName
-
-> Applicable: Security & Compliance
-
The AccountUserName parameter specifies the account user name. Valid values for this parameter are:
- A text value.
@@ -178,6 +168,7 @@ The AccountUserName parameter specifies the account user name. Valid values for
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -187,9 +178,6 @@ Accept wildcard characters: False
```
### -AllowAppStore
-
-> Applicable: Security & Compliance
-
The AllowAppStore parameter specifies whether to allow access to the app store on devices. Valid values for this parameter are:
- $true: Access to the app store is allowed.
@@ -205,6 +193,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -214,9 +203,6 @@ Accept wildcard characters: False
```
### -AllowAssistantWhileLocked
-
-> Applicable: Security & Compliance
-
The AllowAssistantWhileLocked parameter specifies whether to allow the use of the voice assistant while devices are locked. Valid values for this parameter are:
- $true: The voice assistant can be used while devices are locked.
@@ -229,6 +215,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -238,9 +225,6 @@ Accept wildcard characters: False
```
### -AllowConvenienceLogon
-
-> Applicable: Security & Compliance
-
The AllowConvenienceLogon parameter specifies whether to allow convenience logons on devices. Valid values for this parameter are:
- $true: Convenience logons are allowed.
@@ -253,6 +237,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -262,9 +247,6 @@ Accept wildcard characters: False
```
### -AllowDiagnosticSubmission
-
-> Applicable: Security & Compliance
-
The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic submissions from devices. Valid values for this parameter are:
- $true: Diagnostic submissions are allowed.
@@ -281,6 +263,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -290,9 +273,6 @@ Accept wildcard characters: False
```
### -AllowiCloudBackup
-
-> Applicable: Security & Compliance
-
The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup from devices. Valid values for this parameter are:
- $true: iCloud Backup is allowed.
@@ -308,6 +288,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -317,9 +298,6 @@ Accept wildcard characters: False
```
### -AllowiCloudDocSync
-
-> Applicable: Security & Compliance
-
The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documents & Data sync on devices. Valid values for this parameter are:
- $true: iCloud Documents & Data sync is allowed.
@@ -335,6 +313,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -344,9 +323,6 @@ Accept wildcard characters: False
```
### -AllowiCloudPhotoSync
-
-> Applicable: Security & Compliance
-
The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photos sync on devices. Valid values for this parameter are:
- $true: iCloud Photos sync is allowed.
@@ -362,6 +338,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -371,9 +348,6 @@ Accept wildcard characters: False
```
### -AllowPassbookWhileLocked
-
-> Applicable: Security & Compliance
-
The AllowPassbookWhileLocked parameter specifies whether to allow the use of Apple Passbook while devices are locked. Valid values for this parameter are:
- $true: Passbook is available while devices are locked.
@@ -386,6 +360,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -395,9 +370,6 @@ Accept wildcard characters: False
```
### -AllowScreenshot
-
-> Applicable: Security & Compliance
-
The AllowScreenshot parameter specifies whether to allow screenshots on devices. Valid values for this parameter are:
- $true: Screenshots are allowed.
@@ -413,6 +385,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -422,9 +395,6 @@ Accept wildcard characters: False
```
### -AllowSimplePassword
-
-> Applicable: Security & Compliance
-
The AllowSimplePassword parameter specifies whether to allow simple or non-complex passwords on devices. Valid values for this parameter are:
- $true: Simple passwords are allowed.
@@ -441,6 +411,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -450,9 +421,6 @@ Accept wildcard characters: False
```
### -AllowVideoConferencing
-
-> Applicable: Security & Compliance
-
The AllowVideoConferencing parameter specifies whether to allow video conferencing on devices. Valid values for this parameter are:
- $true: Video conferencing is allowed.
@@ -465,6 +433,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -474,9 +443,6 @@ Accept wildcard characters: False
```
### -AllowVoiceAssistant
-
-> Applicable: Security & Compliance
-
The AllowVoiceAssistant parameter specifies whether to allow using the voice assistant on devices. Valid values for this parameter are:
- $true: The voice assistant is allowed.
@@ -489,6 +455,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -498,9 +465,6 @@ Accept wildcard characters: False
```
### -AllowVoiceDialing
-
-> Applicable: Security & Compliance
-
The AllowVoiceDialing parameter specifies whether to allow voice-activated telephone dialing. Valid values for this parameter are:
- $true: Voice dialing is allowed.
@@ -513,6 +477,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -522,9 +487,6 @@ Accept wildcard characters: False
```
### -AntiVirusSignatureStatus
-
-> Applicable: Security & Compliance
-
The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are:
- An integer.
@@ -536,6 +498,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Int64
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -545,9 +508,6 @@ Accept wildcard characters: False
```
### -AntiVirusStatus
-
-> Applicable: Security & Compliance
-
The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are:
- An integer.
@@ -559,6 +519,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Int64
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -568,9 +529,6 @@ Accept wildcard characters: False
```
### -AppsRating
-
-> Applicable: Security & Compliance
-
The AppsRating parameter species the maximum or most restrictive rating of apps that are allowed on devices. Valid values for this parameter are:
- AllowAll
@@ -586,6 +544,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: RatingAppsEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -595,9 +554,6 @@ Accept wildcard characters: False
```
### -AutoUpdateStatus
-
-> Applicable: Security & Compliance
-
The AutoUpdateStatus parameter specifies the update settings for devices. Valid values for this parameter are:
- AutomaticCheckForUpdates
@@ -613,6 +569,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: AutoUpdateStatusEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -622,9 +579,6 @@ Accept wildcard characters: False
```
### -BluetoothEnabled
-
-> Applicable: Security & Compliance
-
The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth on devices. Valid values for this parameter are:
- $true: Bluetooth is enabled.
@@ -637,6 +591,7 @@ This setting is available only on Windows Phone 8.1 devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -646,9 +601,6 @@ Accept wildcard characters: False
```
### -CameraEnabled
-
-> Applicable: Security & Compliance
-
The CameraEnabled parameter specifies whether to enable or disable cameras on devices. Valid values for this parameter are:
- $true: Cameras are enabled.
@@ -665,6 +617,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -674,9 +627,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -686,6 +636,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -695,15 +646,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -713,9 +662,6 @@ Accept wildcard characters: False
```
### -EmailAddress
-
-> Applicable: Security & Compliance
-
The EmailAddress parameter specifies the email address. Valid values are:
- An email address: For example, julia@contoso.com.
@@ -725,6 +671,7 @@ The EmailAddress parameter specifies the email address. Valid values are:
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -734,9 +681,6 @@ Accept wildcard characters: False
```
### -EnableRemovableStorage
-
-> Applicable: Security & Compliance
-
The EnableRemovableStorage parameter specifies whether removable storage can be used by devices. Valid values for this parameter are:
- $true: Removable storage can be used.
@@ -749,6 +693,7 @@ This setting is available only on Windows Phone 8.1 devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -758,9 +703,6 @@ Accept wildcard characters: False
```
### -ExchangeActiveSyncHost
-
-> Applicable: Security & Compliance
-
The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are:
- A text value.
@@ -770,6 +712,7 @@ The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Val
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -779,9 +722,6 @@ Accept wildcard characters: False
```
### -FirewallStatus
-
-> Applicable: Security & Compliance
-
The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are:
- Required
@@ -793,6 +733,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Required
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -802,9 +743,6 @@ Accept wildcard characters: False
```
### -ForceAppStorePassword
-
-> Applicable: Security & Compliance
-
The ForceAppStorePassword parameter specifies whether to require a password to use the app store on devices. Valid values for this parameter are:
- $true: App store passwords are required.
@@ -817,6 +755,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -826,9 +765,6 @@ Accept wildcard characters: False
```
### -ForceEncryptedBackup
-
-> Applicable: Security & Compliance
-
The ForceEncryptedBackup parameter specifies whether to force encrypted backups for devices. Valid values for this parameter are:
- $true: Encrypted backups are required.
@@ -844,6 +780,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -853,9 +790,6 @@ Accept wildcard characters: False
```
### -MaxPasswordAttemptsBeforeWipe
-
-> Applicable: Security & Compliance
-
The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are:
- An integer.
@@ -872,6 +806,7 @@ This setting is available on the following types of devices:
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -881,9 +816,6 @@ Accept wildcard characters: False
```
### -MaxPasswordGracePeriod
-
-> Applicable: Security & Compliance
-
The MaxPasswordGracePeriod parameter specifies the length of time users are allowed to reset expired passwords on devices.
This setting is available only on Apple iOS 6+ devices.
@@ -894,6 +826,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: TimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -903,9 +836,6 @@ Accept wildcard characters: False
```
### -MoviesRating
-
-> Applicable: Security & Compliance
-
The MoviesRating parameter species the maximum or most restrictive rating of movies that are allowed on devices. You specify the country/region rating system to use with the RegionRatings parameter.
Valid values for the MoviesRating parameter are:
@@ -996,6 +926,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: RatingMovieEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1005,9 +936,6 @@ Accept wildcard characters: False
```
### -PasswordComplexity
-
-> Applicable: Security & Compliance
-
The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are:
- An integer.
@@ -1017,6 +945,7 @@ The PasswordComplexity parameter specifies the password complexity. Valid values
Type: Int64
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1026,9 +955,6 @@ Accept wildcard characters: False
```
### -PasswordExpirationDays
-
-> Applicable: Security & Compliance
-
The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are:
- An integer.
@@ -1045,6 +971,7 @@ This setting is available on the following types of devices:
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1054,9 +981,6 @@ Accept wildcard characters: False
```
### -PasswordHistoryCount
-
-> Applicable: Security & Compliance
-
The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are:
- An integer.
@@ -1073,6 +997,7 @@ This setting is available on the following types of devices:
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1082,9 +1007,6 @@ Accept wildcard characters: False
```
### -PasswordMinComplexChars
-
-> Applicable: Security & Compliance
-
The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are:
- An integer.
@@ -1094,6 +1016,7 @@ The PasswordMinComplexChars parameter specifies the minimum number of complex ch
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1103,9 +1026,6 @@ Accept wildcard characters: False
```
### -PasswordMinimumLength
-
-> Applicable: Security & Compliance
-
The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are:
- An integer.
@@ -1122,6 +1042,7 @@ This setting is available on the following types of devices:
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1131,9 +1052,6 @@ Accept wildcard characters: False
```
### -PasswordQuality
-
-> Applicable: Security & Compliance
-
The PasswordQuality parameter specifies the minimum password quality rating that's required for device passwords. Password quality is a numeric scale that indicates the security and complexity of the password. A higher quality value indicates a more secure password.
Valid values for this parameter are:
@@ -1147,6 +1065,7 @@ This setting is available only on Android 4+ devices.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1156,9 +1075,6 @@ Accept wildcard characters: False
```
### -PasswordRequired
-
-> Applicable: Security & Compliance
-
The PasswordRequired parameter specifies whether a password is required to access devices. Valid values for this parameter are:
- $true: Device passwords are required.
@@ -1175,6 +1091,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1184,9 +1101,6 @@ Accept wildcard characters: False
```
### -PasswordTimeout
-
-> Applicable: Security & Compliance
-
The PasswordTimeout parameter specifies the length of time that devices can be inactive before a password is required to reactivate them.
This setting is available on the following types of devices:
@@ -1202,6 +1116,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: TimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1211,9 +1126,6 @@ Accept wildcard characters: False
```
### -PhoneMemoryEncrypted
-
-> Applicable: Security & Compliance
-
The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on devices. Valid values for this parameter are:
- $true: Memory is encrypted.
@@ -1229,6 +1141,7 @@ This setting is available on the following types of devices:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1238,9 +1151,6 @@ Accept wildcard characters: False
```
### -RegionRatings
-
-> Applicable: Security & Compliance
-
The RegionRatings parameter specifies the rating system (country/region) to use for movie and television ratings with the MoviesRating and TVShowsRating parameters.
Valid values for the RegionRating parameter are:
@@ -1262,6 +1172,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: RatingRegionEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1271,9 +1182,6 @@ Accept wildcard characters: False
```
### -RequireEmailProfile
-
-> Applicable: Security & Compliance
-
The RequireEmailProfile parameter specifies whether an email profile is required on devices. Valid values for this parameter are:
- $true: An email profile is required. This value is required for selective wipe on iOS devices.
@@ -1284,6 +1192,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1293,9 +1202,6 @@ Accept wildcard characters: False
```
### -SmartScreenEnabled
-
-> Applicable: Security & Compliance
-
The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen on devices. Valid values for this parameter are:
- $true: SmartScreen is enabled.
@@ -1308,6 +1214,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1317,9 +1224,6 @@ Accept wildcard characters: False
```
### -SystemSecurityTLS
-
-> Applicable: Security & Compliance
-
The SystemSecurityTLS parameter specifies whether TLS encryption is used on devices. Valid values for this parameter are:
- $true: TLS encryption is used.
@@ -1332,6 +1236,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1341,9 +1246,6 @@ Accept wildcard characters: False
```
### -TVShowsRating
-
-> Applicable: Security & Compliance
-
The TVShowsRating parameter species the maximum or most restrictive rating of television shows that are allowed on devices. You specify the country/region rating system to use with the RegionRatings parameter.
Valid values for the TVShowsRating parameter are:
@@ -1423,6 +1325,7 @@ This setting is available only on Apple iOS 6+ devices.
Type: RatingTvShowEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1432,9 +1335,6 @@ Accept wildcard characters: False
```
### -UserAccountControlStatus
-
-> Applicable: Security & Compliance
-
The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are:
- $null (blank): The setting isn't configured. This is the default value.
@@ -1449,6 +1349,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: UserAccountControlStatusEntry
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1458,15 +1359,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1476,9 +1375,6 @@ Accept wildcard characters: False
```
### -WLANEnabled
-
-> Applicable: Security & Compliance
-
The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid values for this parameter are:
- $true: Wi-Fi is enabled.
@@ -1491,6 +1387,7 @@ This setting is available only on Microsoft Windows Phone 8.1 devices.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1500,9 +1397,6 @@ Accept wildcard characters: False
```
### -WorkFoldersSyncUrl
-
-> Applicable: Security & Compliance
-
The WorkFoldersSyncUrl parameter specifies the URL that's used to synchronize company data on devices.
Valid input for this parameter a URL. For example, `https://workfolders.contoso.com`.
@@ -1513,6 +1407,7 @@ This setting is available only on Windows 8.1 RT devices.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md b/exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md
rename to exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md
index dbfdd374b4..13317afc2d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md
+++ b/exchange/exchange-ps/exchange/New-DeviceTenantPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-devicetenantpolicy
applicable: Security & Compliance
+title: New-DeviceTenantPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-devicetenantpolicy
-schema: 2.0.0
-title: New-DeviceTenantPolicy
+ms.reviewer:
---
# New-DeviceTenantPolicy
@@ -54,15 +53,13 @@ This example creates your organization's mobile device tenant policy. You can ha
## PARAMETERS
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -84,6 +78,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -93,9 +88,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Security & Compliance
-
The Enabled parameter specifies whether the policy is enabled. Valid values are:
- $true: The policy is enabled. This is the default value.
@@ -105,6 +97,7 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -114,9 +107,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -125,6 +115,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -134,15 +125,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantRule.md b/exchange/exchange-ps/exchange/New-DeviceTenantRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantRule.md
rename to exchange/exchange-ps/exchange/New-DeviceTenantRule.md
index 6cde541a4c..214a1d7524 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantRule.md
+++ b/exchange/exchange-ps/exchange/New-DeviceTenantRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-devicetenantrule
applicable: Security & Compliance
+title: New-DeviceTenantRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-devicetenantrule
-schema: 2.0.0
-title: New-DeviceTenantRule
+ms.reviewer:
---
# New-DeviceTenantRule
@@ -57,9 +56,6 @@ You can have only one mobile device tenant rule in your organization.
## PARAMETERS
### -ApplyPolicyTo
-
-> Applicable: Security & Compliance
-
The ApplyPolicyTo parameter specifies where to apply the policy in your organization. Valid values for this parameter are:
- ExchangeOnline
@@ -70,6 +66,7 @@ The ApplyPolicyTo parameter specifies where to apply the policy in your organiza
Type: PolicyResourceScope
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -79,9 +76,6 @@ Accept wildcard characters: False
```
### -BlockUnsupportedDevices
-
-> Applicable: Security & Compliance
-
The BlockUnsupportedDevices parameter specifies whether to block access to your organization by unsupported devices. Valid values for this parameter are:
- $true: Unsupported devices are blocked.
@@ -91,6 +85,7 @@ The BlockUnsupportedDevices parameter specifies whether to block access to your
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -100,9 +95,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -112,6 +104,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -121,15 +114,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -139,9 +130,6 @@ Accept wildcard characters: False
```
### -ExclusionList
-
-> Applicable: Security & Compliance
-
The ExclusionList parameter specifies the security groups to exclude from this policy. Members of the specified security groups who have non-compliant devices are not affected by block access actions.
This parameter uses the GUID value of the group. To find this GUID value, run the command Get-Group | Format-Table Name,GUID.
@@ -152,6 +140,7 @@ You can specify multiple groups separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -161,15 +150,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md b/exchange/exchange-ps/exchange/New-DistributionGroup.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md
rename to exchange/exchange-ps/exchange/New-DistributionGroup.md
index ac577a237c..f6466a1301 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md
+++ b/exchange/exchange-ps/exchange/New-DistributionGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-distributiongroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: New-DistributionGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-distributiongroup
-schema: 2.0.0
-title: New-DistributionGroup
+ms.reviewer:
---
# New-DistributionGroup
@@ -85,9 +84,6 @@ This example creates a distribution group named ITDepartment and specifies the m
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Name parameter specifies the unique name of the group. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
This value is also used for the DisplayName property if you don't use the DisplayName parameter.
@@ -96,6 +92,7 @@ This value is also used for the DisplayName property if you don't use the Displa
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -105,9 +102,6 @@ Accept wildcard characters: False
```
### -Alias
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
The Alias value can contain letters, numbers and the following characters:
@@ -132,6 +126,7 @@ The Alias parameter never generates or updates the primary email address of a ma
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -141,9 +136,6 @@ Accept wildcard characters: False
```
### -ArbitrationMailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ArbitrationMailbox parameter specifies the arbitration mailbox that's used to manage the moderation process for this recipient. You can use any value that uniquely identifies the arbitration mailbox. For example:
@@ -163,6 +155,7 @@ The ArbitrationMailbox parameter specifies the arbitration mailbox that's used t
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -172,9 +165,6 @@ Accept wildcard characters: False
```
### -BccBlocked
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The BccBlocked parameter specifies whether members of the group don't receive messages if the group is used in the Bcc line. Valid values are:
@@ -186,6 +176,7 @@ The BccBlocked parameter specifies whether members of the group don't receive me
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -195,9 +186,6 @@ Accept wildcard characters: False
```
### -BypassNestedModerationEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ByPassNestedModerationEnabled parameter specifies how to handle message approval when a moderated group contains other moderated groups as members. Valid values are:
- $true: After a moderator approves a message sent to the group, the message is automatically approved for all other moderated groups that are members of the group.
@@ -209,6 +197,7 @@ This parameter can be used only by top-level organization and tenant administrat
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -218,9 +207,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -230,6 +216,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -239,15 +226,13 @@ Accept wildcard characters: False
```
### -CopyOwnerToMember
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The CopyOwnerToMember switch specifies whether group owners specified by the ManagedBy parameter are also members of the group. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -257,9 +242,6 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
{{ Fill Description Description }}
@@ -268,6 +250,7 @@ This parameter is available only in the cloud-based service.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -277,9 +260,6 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The DisplayName parameter specifies the display name of the group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
If you don't use the DisplayName parameter, the value of the Name parameter is used for the display name.
@@ -290,6 +270,7 @@ If a group naming policy is enforced in your organization, users need to follow
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -299,9 +280,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -310,6 +288,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -319,9 +298,6 @@ Accept wildcard characters: False
```
### -HiddenGroupMembershipEnabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
The HiddenGroupMembershipEnabled switch specifies whether to hide the members of the distribution group from users who aren't members of the group. You don't need to specify a value with this switch.
@@ -334,6 +310,7 @@ You can use this setting to help comply with regulations that require you to hid
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -343,9 +320,6 @@ Accept wildcard characters: False
```
### -IgnoreNamingPolicy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The IgnoreNamingPolicy switch specifies whether to prevent this group from being affected by your organization's group naming policy. You don't need to specify a value with this switch.
The group naming policy is defined by the DistributionGroupNamingPolicy and DistributionGroupNameBlockedWordList parameters on the Set-OrganizationConfig cmdlet.
@@ -354,6 +328,7 @@ The group naming policy is defined by the DistributionGroupNamingPolicy and Dist
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -363,9 +338,6 @@ Accept wildcard characters: False
```
### -ManagedBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ManagedBy parameter specifies an owner for the group. A group must have at least one owner. If you don't use this parameter to specify the owner when you create the group, the user account that created the group is the owner. The group owner is able to:
- Modify the properties of the group
@@ -404,6 +376,7 @@ Owners that you specify with this parameter are not automatically added as group
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -413,9 +386,6 @@ Accept wildcard characters: False
```
### -MemberDepartRestriction
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The MemberDepartRestriction parameter specifies the restrictions that you put on requests to leave the group. Valid values are:
- Open: Members can leave the group without approval from one of the group owners. This is the default value for universal distribution groups. You can't use this value on universal security groups.
@@ -425,6 +395,7 @@ The MemberDepartRestriction parameter specifies the restrictions that you put on
Type: MemberUpdateType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -434,9 +405,6 @@ Accept wildcard characters: False
```
### -MemberJoinRestriction
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The MemberJoinRestriction parameter specifies the restrictions that you put on requests to join the group. Valid values are:
- Open: Users can add themselves to the group without approval from a group owner. You can't use this value on universal security groups.
@@ -447,6 +415,7 @@ The MemberJoinRestriction parameter specifies the restrictions that you put on r
Type: MemberUpdateType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -456,9 +425,6 @@ Accept wildcard characters: False
```
### -Members
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Members parameter specifies the recipients (mail-enabled objects) that are members of the group. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -480,6 +446,7 @@ The maximum number of entries for this parameter is 10000.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -489,9 +456,6 @@ Accept wildcard characters: False
```
### -ModeratedBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ModeratedBy parameter specifies one or more moderators for this group. A moderator approves messages sent to the group before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
- Name
@@ -511,6 +475,7 @@ For distribution groups, if you set the ModerationEnabled parameter to the value
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -520,9 +485,6 @@ Accept wildcard characters: False
```
### -ModerationEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
- $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
@@ -534,6 +496,7 @@ You use the ModeratedBy parameter to specify the moderators.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -543,15 +506,13 @@ Accept wildcard characters: False
```
### -Notes
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Notes parameters specifies additional information about the object. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -561,9 +522,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter specifies the location in Active Directory where the group is created.
Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
@@ -577,6 +535,7 @@ Valid input for this parameter is an organizational unit (OU) or domain that's r
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -586,15 +545,13 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
```yaml
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -604,9 +561,6 @@ Accept wildcard characters: False
```
### -RequireSenderAuthenticationEnabled
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
- $true: Messages are accepted only from authenticated (internal) senders. Messages from unauthenticated (external) senders are rejected.
@@ -618,6 +572,7 @@ The default value is $true.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -627,9 +582,6 @@ Accept wildcard characters: False
```
### -RoomList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RoomList switch specifies that all members of this distribution group are room mailboxes. You don't need to specify a value with this switch.
You can create a distribution group for an office building in your organization and add all rooms in that building to the distribution group. Room list distribution groups are used to generate a list of building locations for meeting requests in Outlook 2010 or later. Room lists allow a user to select a building and get availability information for all rooms in that building, without having to add each room individually.
@@ -638,6 +590,7 @@ You can create a distribution group for an office building in your organization
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -647,9 +600,6 @@ Accept wildcard characters: False
```
### -SamAccountName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match).
@@ -658,6 +608,7 @@ The SamAccountName parameter (also known as the pre-Windows 2000 user account or
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -667,9 +618,6 @@ Accept wildcard characters: False
```
### -SendModerationNotifications
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
- Always: Notify all senders when their messages aren't approved. This is the default value.
@@ -682,6 +630,7 @@ This parameter is only meaningful when moderation is enabled (the ModerationEnab
Type: TransportModerationNotificationFlags
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -691,9 +640,6 @@ Accept wildcard characters: False
```
### -Type
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Type parameter specifies the type of group that you want to create. Valid values are:
- Distribution: A distribution group. These groups can't have permissions assigned. This is the default value.
@@ -705,6 +651,7 @@ The group's scope is always Universal.
Type: GroupType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -714,15 +661,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md b/exchange/exchange-ps/exchange/New-DkimSigningConfig.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md
rename to exchange/exchange-ps/exchange/New-DkimSigningConfig.md
index 0dfaee8eb1..5bd296a8ba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md
+++ b/exchange/exchange-ps/exchange/New-DkimSigningConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dkimsigningconfig
applicable: Exchange Online, Exchange Online Protection
+title: New-DkimSigningConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dkimsigningconfig
-schema: 2.0.0
-title: New-DkimSigningConfig
+ms.reviewer:
---
# New-DkimSigningConfig
@@ -49,9 +48,6 @@ This example enables DKIM message signing for the contoso.com domain.
## PARAMETERS
### -DomainName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The DomainName parameter specifies the domain in your organization that you want to enable DKIM message signing for.
By default, DKIM message signing is enabled for the initial \*.onmicrosoft.com domain in the organization (for example, contoso.onmicrosoft.com).
@@ -62,6 +58,7 @@ For custom domains that don't have DKIM messaging signing enabled, the DKIM sign
Type: SmtpDomainWithSubdomains
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Enabled parameter specifies whether the policy is enabled. Valid values are:
- $true: The policy is enabled.
@@ -83,6 +77,7 @@ The Enabled parameter specifies whether the policy is enabled. Valid values are:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 2
@@ -92,15 +87,13 @@ Accept wildcard characters: False
```
### -AdminDisplayName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AdminDisplayName parameter specifies a description for the policy. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -110,9 +103,6 @@ Accept wildcard characters: False
```
### -BodyCanonicalization
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The BodyCanonicalization parameter specifies the canonicalization algorithm that's used to create and verify the message body part of the DKIM signature. This value effectively controls the sensitivity of DKIM to changes to the message body in transit. Valid values are:
- Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This is the default value.
@@ -122,6 +112,7 @@ The BodyCanonicalization parameter specifies the canonicalization algorithm that
Type: CanonicalizationType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -131,9 +122,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -143,6 +131,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -152,9 +141,6 @@ Accept wildcard characters: False
```
### -HeaderCanonicalization
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HeaderCanonicalization parameter specifies the canonicalization algorithm that's used to create and verify the message header part of the DKIM signature. This value effectively controls the sensitivity of DKIM to changes to the message headers in transit. Valid values are:
- Relaxed: Common modifications to the message header are tolerated (for example, Header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields). This is the default value.
@@ -164,6 +150,7 @@ The HeaderCanonicalization parameter specifies the canonicalization algorithm th
Type: CanonicalizationType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -173,9 +160,6 @@ Accept wildcard characters: False
```
### -KeySize
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The KeySize parameter specifies the size in bits of the public key that's used in the DKIM signing policy. Valid values are:
- 1024 (this is the default value)
@@ -187,6 +171,7 @@ RSA keys are supported. Ed25519 keys aren't supported.
Type: UInt16
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -196,15 +181,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md
rename to exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md
index bc1368c34b..17a536c78d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md
+++ b/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpcompliancepolicy
applicable: Security & Compliance
+title: New-DlpCompliancePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpcompliancepolicy
-schema: 2.0.0
-title: New-DlpCompliancePolicy
+ms.reviewer:
---
# New-DlpCompliancePolicy
@@ -154,15 +153,13 @@ This example creates a DLP policy for Microsoft 365 Copilot (Preview) in several
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies the unique name of the DLP policy. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -172,15 +169,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -190,9 +185,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -202,6 +194,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -211,15 +204,13 @@ Accept wildcard characters: False
```
### -EndpointDlpAdaptiveScopes
-
-> Applicable: Security & Compliance
-
{{ Fill EndpointDlpAdaptiveScopes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -229,15 +220,13 @@ Accept wildcard characters: False
```
### -EndpointDlpAdaptiveScopesException
-
-> Applicable: Security & Compliance
-
{{ Fill EndpointDlpAdaptiveScopesException Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -247,15 +236,13 @@ Accept wildcard characters: False
```
### -EndpointDlpExtendedLocations
-
-> Applicable: Security & Compliance
-
{{ Fill EndpointDlpExtendedLocations Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -265,9 +252,6 @@ Accept wildcard characters: False
```
### -EndpointDlpLocation
-
-> Applicable: Security & Compliance
-
**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
The EndpointDLPLocation parameter specifies the user accounts to include in the DLP policy for Endpoint DLP when they are logged on to an onboarded device. You identify the account by name or email address. You can use the value All to include all user accounts.
@@ -280,6 +264,7 @@ For more information about Endpoint DLP, see [Learn about Endpoint data loss pre
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -289,9 +274,6 @@ Accept wildcard characters: False
```
### -EndpointDlpLocationException
-
-> Applicable: Security & Compliance
-
**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
The EndpointDlpLocationException parameter specifies the user accounts to exclude from Endpoint DLP when you use the value All for the EndpointDlpLocation parameter. You identify the account by name or email address.
@@ -304,6 +286,7 @@ For more information about Endpoint DLP, see [Learn about Endpoint data loss pre
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -313,9 +296,6 @@ Accept wildcard characters: False
```
### -EnforcementPlanes
-
-> Applicable: Security & Compliance
-
The EnforcementPlanes parameter defines the layer where policy actions are run. This parameter uses the following syntax:
`-EnforcementPlanes @("")`.
@@ -329,6 +309,7 @@ Currently, supported values are:
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -338,9 +319,6 @@ Accept wildcard characters: False
```
### -ExceptIfOneDriveSharedBy
-
-> Applicable: Security & Compliance
-
The ExceptIfOneDriveSharedBy parameter specifies the users to exclude from the DLP policy (the sites of the OneDrive user accounts are included in the policy). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
To use this parameter, OneDrive sites need to be included in the policy (the OneDriveLocation parameter value is All, which is the default value).
@@ -353,6 +331,7 @@ You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMember
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -362,9 +341,6 @@ Accept wildcard characters: False
```
### -ExceptIfOneDriveSharedByMemberOf
-
-> Applicable: Security & Compliance
-
The ExceptIfOneDriveSharedByMemberOf parameter specifies the distribution groups or mail-enabled security groups to exclude from the DLP policy (the OneDrive sites of group members are excluded from the policy). You identify the groups by email address.
To use this parameter, OneDrive sites need to be included in the policy (the OneDriveLocation parameter value is All, which is the default value).
@@ -379,6 +355,7 @@ You can't use this parameter to specify Microsoft 365 Groups.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -388,15 +365,13 @@ Accept wildcard characters: False
```
### -ExchangeAdaptiveScopes
-
-> Applicable: Security & Compliance
-
{{ Fill ExchangeAdaptiveScopes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -406,15 +381,13 @@ Accept wildcard characters: False
```
### -ExchangeAdaptiveScopesException
-
-> Applicable: Security & Compliance
-
{{ Fill ExchangeAdaptiveScopesException Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -424,9 +397,6 @@ Accept wildcard characters: False
```
### -ExchangeLocation
-
-> Applicable: Security & Compliance
-
The ExchangeLocation parameter specifies whether to include email messages in the DLP policy. The valid value for this parameter is All. If you don't want to include email messages in the policy, don't use this parameter (the default value is blank or $null).
You can use this parameter in the following procedures:
@@ -443,6 +413,7 @@ You can't specify inclusions and exclusions in the same policy.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -452,9 +423,6 @@ Accept wildcard characters: False
```
### -ExchangeSenderMemberOf
-
-> Applicable: Security & Compliance
-
The ExchangeSenderMemberOf parameter specifies the distribution groups or security groups to include in the policy (email of the group members is included in the policy). You identify the groups by email address.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -469,6 +437,7 @@ You can't use this parameter to specify Microsoft 365 Groups.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -478,9 +447,6 @@ Accept wildcard characters: False
```
### -ExchangeSenderMemberOfException
-
-> Applicable: Security & Compliance
-
The ExchangeSenderMemberOfException parameter specifies the distribution groups or security groups to exclude from the policy (email of the group members is excluded from the policy). You identify the groups by email address.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -495,6 +461,7 @@ You can't use this parameter to specify Microsoft 365 Groups.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -504,9 +471,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -515,6 +479,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -524,15 +489,13 @@ Accept wildcard characters: False
```
### -IsFromSmartInsights
-
-> Applicable: Security & Compliance
-
{{ Fill IsFromSmartInsights Description }}
```yaml
Type: System.Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -542,9 +505,6 @@ Accept wildcard characters: False
```
### -Locations
-
-> Applicable: Security & Compliance
-
The Locations parameter specifies to whom, what, and where the DLP policy applies. This parameter uses the following properties:
- Workload: What the DLP policy applies to. Use the value `Applications`.
@@ -572,6 +532,7 @@ After you create the `$loc` variable as shown in the previous examples, use the
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -581,9 +542,6 @@ Accept wildcard characters: False
```
### -Mode
-
-> Applicable: Security & Compliance
-
The Mode parameter specifies the action and notification level of the DLP policy. Valid values are:
- Enable: The policy is enabled for actions and notifications. This is the default value.
@@ -595,6 +553,7 @@ The Mode parameter specifies the action and notification level of the DLP policy
Type: PolicyMode
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -604,15 +563,13 @@ Accept wildcard characters: False
```
### -OneDriveAdaptiveScopes
-
-> Applicable: Security & Compliance
-
{{ Fill OneDriveAdaptiveScopes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -622,15 +579,13 @@ Accept wildcard characters: False
```
### -OneDriveAdaptiveScopesException
-
-> Applicable: Security & Compliance
-
{{ Fill OneDriveAdaptiveScopesException Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -640,9 +595,6 @@ Accept wildcard characters: False
```
### -OneDriveLocation
-
-> Applicable: Security & Compliance
-
The OneDriveLocation parameter specifies whether to include OneDrive sites in the policy. A valid value for this parameter is All, which is also the default value.
You can use this parameter in the following procedures:
@@ -665,6 +617,7 @@ You can't specify inclusions and exclusions in the same policy.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
Default value: None
@@ -673,15 +626,13 @@ Accept wildcard characters: False
```
### -OneDriveLocationException
-
-> Applicable: Security & Compliance
-
Don't use this parameter. See the OneDriveLocation parameter for an explanation.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
Default value: None
@@ -690,9 +641,6 @@ Accept wildcard characters: False
```
### -OneDriveSharedBy
-
-> Applicable: Security & Compliance
-
The OneDriveSharedBy parameter specifies the users to include in the DLP policy (the sites of the OneDrive user accounts are included in the policy). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
To use this parameter, OneDrive sites need to be included in the policy (the OneDriveLocation parameter value is All, which is the default value).
@@ -705,6 +653,7 @@ You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDri
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -714,9 +663,6 @@ Accept wildcard characters: False
```
### -OneDriveSharedByMemberOf
-
-> Applicable: Security & Compliance
-
The OneDriveSharedByMemberOf parameter specifies the distribution groups or mail-enabled security groups to include in the DLP policy (the OneDrive sites of group members are included in the policy). You identify the groups by email address.
To use this parameter, OneDrive sites need to be included in the policy (the OneDriveLocation parameter value is All, which is the default value).
@@ -731,6 +677,7 @@ You can't use this parameter to specify Microsoft 365 Groups.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -740,9 +687,6 @@ Accept wildcard characters: False
```
### -OnPremisesScannerDlpLocation
-
-> Applicable: Security & Compliance
-
The OnPremisesScannerDlpLocation parameter specifies the on-premises file shares and SharePoint document libraries and folders to include in the DLP policy. You can use the value All to include all on-premises file shares and SharePoint document libraries and folders.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -753,6 +697,7 @@ For more information about the DLP on-premises scanner, see [Learn about the dat
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -762,9 +707,6 @@ Accept wildcard characters: False
```
### -OnPremisesScannerDlpLocationException
-
-> Applicable: Security & Compliance
-
The OnPremisesScannerDlpLocationException parameter specifies the on-premises file shares and SharePoint document libraries and folders to exclude from the DLP policy if you use the value All for the OnPremisesScannerDlpLocation parameter.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -775,6 +717,7 @@ For more information about the DLP on-premises scanner, see [Learn about the dat
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -784,9 +727,6 @@ Accept wildcard characters: False
```
### -PolicyRBACScopes
-
-> Applicable: Security & Compliance
-
The PolicyRBACScopes parameter specifies the administrative units to assign to the policy. A valid value is the Microsoft Entra ObjectID (GUID value) of the administrative unit. You can specify multiple values separated by commas.
Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell.
@@ -795,6 +735,7 @@ Administrative units are available only in Microsoft Entra ID P1 or P2. You crea
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -804,9 +745,6 @@ Accept wildcard characters: False
```
### -PolicyTemplateInfo
-
-> Applicable: Security & Compliance
-
The PolicyTemplateInfo specifies the built-in or custom DLP policy templates to use in the DLP policy.
For more information about DLP policy templates, see [What the DLP policy templates include](https://learn.microsoft.com/purview/what-the-dlp-policy-templates-include).
@@ -815,6 +753,7 @@ For more information about DLP policy templates, see [What the DLP policy templa
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -824,9 +763,6 @@ Accept wildcard characters: False
```
### -PowerBIDlpLocation
-
-> Applicable: Security & Compliance
-
The PowerBIDlpLocation parameter specifies the Power BI workspace IDs to include in the DLP policy. Only workspaces hosted in Premium Gen2 capacities are permitted. You can use the value All to include all supported workspaces.
You can find the workspace ID using any of the following procedures:
@@ -843,6 +779,7 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance
-
The PowerBIDlpLocationException parameter specifies the Power BI workspace IDs to exclude from the DLP policy when you use the value All for the PowerBIDlpLocation parameter. Only workspaces hosted in Premium Gen2 capacities are permitted.
You can find the workspace ID using any of the following procedures:
@@ -869,6 +803,7 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance
-
The Priority parameter specifies a priority value for the policy that determines the order of policy processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and policies can't have the same priority value.
Valid values and the default value depend on the number of existing policies. For example, if there are 5 existing policies:
@@ -895,6 +827,7 @@ If you modify the priority value of a policy, the position of the policy in the
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -904,15 +837,13 @@ Accept wildcard characters: False
```
### -SharePointAdaptiveScopes
-
-> Applicable: Security & Compliance
-
{{ Fill SharePointAdaptiveScopes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -922,15 +853,13 @@ Accept wildcard characters: False
```
### -SharePointAdaptiveScopesException
-
-> Applicable: Security & Compliance
-
{{ Fill SharePointAdaptiveScopesException Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -940,9 +869,6 @@ Accept wildcard characters: False
```
### -SharePointLocation
-
-> Applicable: Security & Compliance
-
The SharePointLocation parameter specifies the SharePoint sites to include in the DLP policy. You identify the site by its URL value, or you can use the value All to include all sites.
You can't add SharePoint sites to the policy until they have been indexed.
@@ -953,6 +879,7 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance
-
The SharePointLocationException parameter specifies the SharePoint sites to exclude when you use the value All for the SharePointLocation parameter. You identify the site by its URL value.
You can't add SharePoint sites to the policy until they have been indexed.
@@ -975,6 +899,7 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance
-
{{ Fill TeamsAdaptiveScopes Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1002,15 +925,13 @@ Accept wildcard characters: False
```
### -TeamsAdaptiveScopesException
-
-> Applicable: Security & Compliance
-
{{ Fill TeamsAdaptiveScopesException Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1020,9 +941,6 @@ Accept wildcard characters: False
```
### -TeamsLocation
-
-> Applicable: Security & Compliance
-
The TeamsLocation parameter specifies the Teams chat and channel messages to include in the DLP policy. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group. You can use the value All to include all accounts, distribution groups, and mail-enabled security groups.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -1031,6 +949,7 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance
-
The TeamsLocation parameter specifies the Teams chat and channel messages to exclude from the DLP policy when you use the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
To enter multiple values, use the following syntax: `,,...`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"","",...""`.
@@ -1051,6 +967,7 @@ To enter multiple values, use the following syntax: `,,... Applicable: Security & Compliance
-
**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
The ThirdPartyAppDlpLocation parameter specifies the non-Microsoft cloud apps to include in the DLP policy. You can use the value All to include all connected apps.
@@ -1075,6 +989,7 @@ For more information about DLP for non-Microsoft cloud apps, see [Use data loss
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1084,9 +999,6 @@ Accept wildcard characters: False
```
### -ThirdPartyAppDlpLocationException
-
-> Applicable: Security & Compliance
-
**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
The ThirdPartyAppDlpLocationException parameter specifies the non-Microsoft cloud apps to exclude from the DLP policy when you use the value All for the ThirdPartyAppDlpLocation parameter.
@@ -1099,6 +1011,7 @@ For more information about DLP for non-Microsoft cloud apps, see [Use data loss
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1108,15 +1021,13 @@ Accept wildcard characters: False
```
### -ValidatePolicy
-
-> Applicable: Security & Compliance
-
{{ Fill ValidatePolicy Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1126,15 +1037,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md b/exchange/exchange-ps/exchange/New-DlpComplianceRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md
rename to exchange/exchange-ps/exchange/New-DlpComplianceRule.md
index eceadf5ef2..177d38fa19 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md
+++ b/exchange/exchange-ps/exchange/New-DlpComplianceRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpcompliancerule
applicable: Security & Compliance
+title: New-DlpComplianceRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpcompliancerule
-schema: 2.0.0
-title: New-DlpComplianceRule
+ms.reviewer:
---
# New-DlpComplianceRule
@@ -327,15 +326,13 @@ This is an example of applying a CCSI-based DLP rule that should be handled by a
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies the unique name of the new DLP rule. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -345,9 +342,6 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter specifies the existing DLP policy that will contain the new DLP rule. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -359,6 +353,7 @@ The Policy parameter specifies the existing DLP policy that will contain the new
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -368,9 +363,6 @@ Accept wildcard characters: False
```
### -AccessScope
-
-> Applicable: Security & Compliance
-
The AccessScope parameter specifies a condition for the DLP rule that's based on the access scope of the content. The rule is applied to content that matches the specified access scope. Valid values are:
- InOrganization: The rule is applied to content that's accessible or delivered to a recipient inside the organization.
@@ -381,6 +373,7 @@ The AccessScope parameter specifies a condition for the DLP rule that's based on
Type: Microsoft.Office.CompliancePolicy.Tasks.AccessScope
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -390,15 +383,13 @@ Accept wildcard characters: False
```
### -ActivationDate
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -408,9 +399,6 @@ Accept wildcard characters: False
```
### -AddRecipients
-
-> Applicable: Security & Compliance
-
The AddRecipients parameter specifies an action for the DLP rule that adds the specified recipients to email messages. This parameter uses the following syntax:
- `@{ = "emailaddress"}`. For example, `@{AddToRecipients = "laura@contoso.com"}` or `@{BlindCopyTo = "julia@contoso.com"}`.
@@ -422,6 +410,7 @@ You can use this action in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -431,9 +420,6 @@ Accept wildcard characters: False
```
### -AdvancedRule
-
-> Applicable: Security & Compliance
-
The AdvancedRule parameter uses complex rule syntax that supports multiple AND, OR, and NOT operators and nested groups.
This parameter uses JSON syntax that's similar to the traditional advanced syntax in Example 2, but read from a file that contains additional operators and combinations that aren't traditionally supported.
@@ -444,6 +430,7 @@ For syntax details, see Example 3.
Type: String
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -453,15 +440,13 @@ Accept wildcard characters: False
```
### -AlertProperties
-
-> Applicable: Security & Compliance
-
{{ Fill AlertProperties Description }}
```yaml
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -471,9 +456,6 @@ Accept wildcard characters: False
```
### -AnyOfRecipientAddressContainsWords
-
-> Applicable: Security & Compliance
-
The AnyOfRecipientAddressContainsWords parameter specifies a condition for the DLP rule that looks for words or phrases in recipient email addresses. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -488,6 +470,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -497,9 +480,6 @@ Accept wildcard characters: False
```
### -AnyOfRecipientAddressMatchesPatterns
-
-> Applicable: Security & Compliance
-
The AnyOfRecipientAddressMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in recipient email addresses by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 300.
@@ -510,6 +490,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -519,9 +500,6 @@ Accept wildcard characters: False
```
### -ApplyBrandingTemplate
-
-> Applicable: Security & Compliance
-
The ApplyBrandingTemplate parameter specifies an action for the DLP rule that applies a custom branding template for messages encrypted by Microsoft Purview Message Encryption. You identify the custom branding template by name. If the name contains spaces, enclose the name in quotation marks (").
Use the EnforcePortalAccess parameter to control whether external users are required to use the encrypted message portal to view encrypted messages.
@@ -530,6 +508,7 @@ Use the EnforcePortalAccess parameter to control whether external users are requ
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -539,9 +518,6 @@ Accept wildcard characters: False
```
### -ApplyHtmlDisclaimer
-
-> Applicable: Security & Compliance
-
The ApplyHtmlDisclaimer parameter specifies an action for the rule that adds disclaimer text to messages.This parameter uses the syntax: `@{Text = "Disclaimer text"; Location = ; FallbackAction = }`.
- Text: Specifies the disclaimer text to add. Disclaimer text can include HTML tags and inline cascading style sheet (CSS) tags. You can add images using the IMG tag.
@@ -554,6 +530,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -563,15 +540,13 @@ Accept wildcard characters: False
```
### -AttachmentIsNotLabeled
-
-> Applicable: Security & Compliance
-
{{ Fill AttachmentIsNotLabeled Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -581,9 +556,6 @@ Accept wildcard characters: False
```
### -BlockAccess
-
-> Applicable: Security & Compliance
-
The BlockAccess parameter specifies an action for the DLP rule that blocks access to the source item when the conditions of the rule are met. Valid values are:
- $true: Blocks further access to the source item that matched the rule. The owner, author, and site owner can still access the item.
@@ -593,6 +565,7 @@ The BlockAccess parameter specifies an action for the DLP rule that blocks acces
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -602,9 +575,6 @@ Accept wildcard characters: False
```
### -BlockAccessScope
-
-> Applicable: Security & Compliance
-
The BlockAccessScope parameter specifies the scope of the block access action. Valid values are:
- All: Blocks access to everyone except the owner and the last modifier.
@@ -615,6 +585,7 @@ The BlockAccessScope parameter specifies the scope of the block access action. V
Type: Microsoft.Office.CompliancePolicy.Tasks.BlockAccessScope
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -624,15 +595,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -642,9 +611,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -654,6 +620,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -663,9 +630,6 @@ Accept wildcard characters: False
```
### -ContentCharacterSetContainsWords
-
-> Applicable: Security & Compliance
-
The ContentCharacterSetContainsWords parameter specifies a condition for the rule that looks for character set names in messages. You can specify multiple values separated by commas.
Supported character sets are `big5, din_66003, euc-jp, euc-kr, gb18030, gb2312, hz-gb-2312, iso-2022-jp, iso-2022-kr, iso-8859-1, iso-8859-13, iso-8859-15, iso-8859-2, iso-8859-3, iso-8859-4, iso-8859-5, iso-8859-6, iso-8859-7, iso-8859-8, iso-8859-9, koi8-r, koi8-u, ks_c_5601-1987, ns_4551-1, sen_850200_b, shift_jis, utf-7, utf-8, windows-1250, windows-1251, windows-1252, windows-1253, windows-1254, windows-1255, windows-1256, windows-1257, windows-1258, windows-874`.
@@ -674,6 +638,7 @@ Supported character sets are `big5, din_66003, euc-jp, euc-kr, gb18030, gb2312,
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -683,9 +648,6 @@ Accept wildcard characters: False
```
### -ContentContainsSensitiveInformation
-
-> Applicable: Security & Compliance
-
The ContentContainsSensitiveInformation parameter specifies a condition for the rule that's based on a sensitive information type match in content. The rule is applied to content that contains the specified sensitive information type. In addition to sensitive information type, the parameter can also be applied to files that contain sensitivity labels.
This parameter uses the basic syntax `@(@{Name="SensitiveInformationType1";[minCount="Value"],@{Name="SensitiveInformationType2";[minCount="Value"],...)`. For example, `@(@{Name="U.S. Social Security Number (SSN)"; minCount="2"},@{Name="Credit Card Number"})`. Example for sensitivity label: `@(@{operator = "And"; groups = @(@{operator="Or";name="Default";labels=@(@{name="Confidential";type="Sensitivity"})})})`.
@@ -698,6 +660,7 @@ For an example of advanced syntax, see Example 2 in this topic.
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -707,15 +670,13 @@ Accept wildcard characters: False
```
### -ContentExtensionMatchesWords
-
-> Applicable: Security & Compliance
-
The ContentExtensionMatchesWords parameter specifies a condition for the DLP rule that looks for words in file extensions. You can specify multiple words separated by commas. Irrespective of the original file type, this predicate matches based on the extension that is present in the name of the file.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -725,15 +686,13 @@ Accept wildcard characters: False
```
### -ContentFileTypeMatches
-
-> Applicable: Security & Compliance
-
{{ Fill ContentFileTypeMatches Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -743,9 +702,6 @@ Accept wildcard characters: False
```
### -ContentIsNotLabeled
-
-> Applicable: Security & Compliance
-
The ContentIsNotLabeled parameter specifies a condition for the DLP rule that looks for attachments or documents that aren't labeled. Valid values are:
- $true: Look for attachments or documents that aren't labeled.
@@ -757,6 +713,7 @@ In Exchange, this condition is matched only if both the attachment and the messa
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -766,9 +723,6 @@ Accept wildcard characters: False
```
### -ContentIsShared
-
-> Applicable: Security & Compliance
-
The ContentIsNotLabeled parameter specifies a condition for the DLP rule that looks for attachments or documents that aren't labeled. Valid values are:
- $true: Look for attachments or documents that aren't labeled.
@@ -780,6 +734,7 @@ In Exchange, this condition is matched only if both the attachment and the messa
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -789,9 +744,6 @@ Accept wildcard characters: False
```
### -ContentPropertyContainsWords
-
-> Applicable: Security & Compliance
-
The ContentPropertyContainsWords parameter specifies a condition for the DLP rule that's based on a property match in content. The rule is applied to content that contains the specified property.
This parameter accepts values in the format: `"Property1:Value1,Value2","Property2:Value3,Value4",..."PropertyN:ValueN,ValueN"`.
@@ -800,6 +752,7 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -809,9 +762,6 @@ Accept wildcard characters: False
```
### -Disabled
-
-> Applicable: Security & Compliance
-
The Disabled parameter specifies whether the DLP rule is disabled. Valid values are:
- $true: The rule is disabled.
@@ -821,6 +771,7 @@ The Disabled parameter specifies whether the DLP rule is disabled. Valid values
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -830,9 +781,6 @@ Accept wildcard characters: False
```
### -DocumentContainsWords
-
-> Applicable: Security & Compliance
-
The DocumentContainsWords parameter specifies a condition for the DLP rule that looks for words in message attachments. Only supported attachment types are checked.
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -843,6 +791,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -852,9 +801,6 @@ Accept wildcard characters: False
```
### -DocumentCreatedBy
-
-> Applicable: Security & Compliance
-
The DocumentCreatedBy parameter specifies a condition for the DLP rule that looks for documents that are created by the specificed identity. You can specify multiple values separated by commas.
This parameter applies to Sharepoint and Onedrive workloads.
@@ -863,6 +809,7 @@ This parameter applies to Sharepoint and Onedrive workloads.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -872,9 +819,6 @@ Accept wildcard characters: False
```
### -DocumentCreatedByMemberOf
-
-> Applicable: Security & Compliance
-
The DocumentCreatedByMemberOf parameter specifies a condition for the DLP rule that looks for documents that are created by a member of the specificed group. You can specify multiple values separated by commas.
This parameter applies to Sharepoint and Onedrive workloads.
@@ -883,6 +827,7 @@ This parameter applies to Sharepoint and Onedrive workloads.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -892,9 +837,6 @@ Accept wildcard characters: False
```
### -DocumentIsPasswordProtected
-
-> Applicable: Security & Compliance
-
The DocumentIsPasswordProtected parameter specifies a condition for the DLP rule that looks for password protected files (because the contents of the file can't be inspected). Password detection works for Office documents, compressed files (.zip, .7z, .rar, .tar, etc.), and .pdf files. Valid values are:
- $true: Look for password protected files.
@@ -904,6 +846,7 @@ The DocumentIsPasswordProtected parameter specifies a condition for the DLP rule
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -913,9 +856,6 @@ Accept wildcard characters: False
```
### -DocumentIsUnsupported
-
-> Applicable: Security & Compliance
-
The DocumentIsUnsupported parameter specifies a condition for the DLP rule that looks for files that can't be scanned. Valid values are:
- $true: Look for unsupported files that can't be scanned.
@@ -925,6 +865,7 @@ The DocumentIsUnsupported parameter specifies a condition for the DLP rule that
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -934,9 +875,6 @@ Accept wildcard characters: False
```
### -DocumentMatchesPatterns
-
-> Applicable: Security & Compliance
-
The DocumentMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in the content of message attachments by using regular expressions. Only supported attachment types are checked.
You can specify multiple text patterns by using the following syntax: `"Regular expression1","Regular expression2",..."Regular expressionN"`.
@@ -947,6 +885,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -956,9 +895,6 @@ Accept wildcard characters: False
```
### -DocumentNameMatchesPatterns
-
-> Applicable: Security & Compliance
-
The DocumentNameMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in the name of message attachments by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 300.
@@ -967,6 +903,7 @@ The maximum individual regular expression length is 128 characters. The maximum
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -976,9 +913,6 @@ Accept wildcard characters: False
```
### -DocumentNameMatchesWords
-
-> Applicable: Security & Compliance
-
The DocumentNameMatchesWords parameter specifies a condition for the DLP rule that looks for words or phrases in the name of message attachments. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -991,6 +925,7 @@ The maximum individual word or phrase length is 128 characters. The maximum numb
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1000,9 +935,6 @@ Accept wildcard characters: False
```
### -DocumentSizeOver
-
-> Applicable: Security & Compliance
-
The DocumentSizeOver parameter specifies a condition for the DLP rule that looks for messages where any attachment is greater than the specified size.
When you enter a value, qualify the value with one of the following units:
@@ -1021,6 +953,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: Microsoft.Exchange.Data.ByteQuantifiedSize
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1029,9 +962,6 @@ Accept pipeline input: False
Accept wildcard characters: False
```
### -DomainCountOver
-
-> Applicable: Security & Compliance
-
The DomainCountOver parameter specifies a condition for the DLP rule that looks for messages where the number of recipient domains is greater than the specified value.
You can use this condition in DLP policies that are scoped only to Exchange. In PowerShell, you can use this parameter only inside an Advanced Rule.
@@ -1040,6 +970,7 @@ You can use this condition in DLP policies that are scoped only to Exchange. In
Type: UInt32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1048,9 +979,6 @@ Accept pipeline input: False
Accept wildcard characters: False
```
### -EncryptRMSTemplate
-
-> Applicable: Security & Compliance
-
The EncryptRMSTemplate parameter specifies an action for the DLP rule that applies rights management service (RMS) templates to files. You identify the RMS template by name. If the name contains spaces, enclose the name in quotation marks (").
Use the Get-RMSTemplate cmdlet to see the RMS templates that are available.
@@ -1059,6 +987,7 @@ Use the Get-RMSTemplate cmdlet to see the RMS templates that are available.
Type: RmsTemplateIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1068,15 +997,13 @@ Accept wildcard characters: False
```
### -EndpointDlpBrowserRestrictions
-
-> Applicable: Security & Compliance
-
{{ Fill EndpointDlpBrowserRestrictions Description }}
```yaml
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1086,9 +1013,6 @@ Accept wildcard characters: False
```
### -EndpointDlpRestrictions
-
-> Applicable: Security & Compliance
-
**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
The EndpointDlpRestrictions parameter specifies the restricted endpoints for Endpoint DLP. This parameter uses the following syntax: `@(@{"Setting"=""; "Value"="}",@{"Setting"=""; "Value"=""},...)`.
@@ -1117,6 +1041,7 @@ For more information about Endpoint DLP, see [Learn about Endpoint data loss pre
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1126,9 +1051,6 @@ Accept wildcard characters: False
```
### -EnforcePortalAccess
-
-> Applicable: Security & Compliance
-
The EnforcePortalAccess parameter specifies whether external recipients are required to view encrypted mail using the encrypted message portal when the ApplyBrandingTemplate action is also specified. Valid values are:
- $true: External recipients are required to use the encrypted message portal to view encrypted messages.
@@ -1138,6 +1060,7 @@ The EnforcePortalAccess parameter specifies whether external recipients are requ
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1147,9 +1070,6 @@ Accept wildcard characters: False
```
### -EvaluateRulePerComponent
-
-> Applicable: Security & Compliance
-
The EvaluateRulePerComponent parameter specifies whether a match for conditions and exceptions in the rule is contained within the same message component. Valid values are:
- $true: A DLP rule match for conditions and exceptions must be in the same message component (for example, in the message body or in a single attachment).
@@ -1168,6 +1088,7 @@ This parameter works with the following conditions or exceptions only:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1177,9 +1098,6 @@ Accept wildcard characters: False
```
### -ExceptIfAccessScope
-
-> Applicable: Security & Compliance
-
The ExceptIfAccessScopeAccessScope parameter specifies an exception for the DLP rule that's based on the access scope of the content. The rule isn't applied to content that matches the specified access scope. Valid values are:
- InOrganization: The rule isn't applied to content that's accessible or delivered to a recipient inside the organization.
@@ -1190,6 +1108,7 @@ The ExceptIfAccessScopeAccessScope parameter specifies an exception for the DLP
Type: Microsoft.Office.CompliancePolicy.Tasks.AccessScope
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1199,9 +1118,6 @@ Accept wildcard characters: False
```
### -ExceptIfAnyOfRecipientAddressContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfAnyOfRecipientAddressContainsWords parameter specifies an exception for the DLP rule that looks for words or phrases in recipient email addresses. You can specify multiple words separated by commas.
- Single word: `"no_reply"`
@@ -1216,6 +1132,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1225,9 +1142,6 @@ Accept wildcard characters: False
```
### -ExceptIfAnyOfRecipientAddressMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfAnyOfRecipientAddressMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in recipient email addresses by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 300.
@@ -1238,6 +1152,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1247,9 +1162,6 @@ Accept wildcard characters: False
```
### -ExceptIfContentCharacterSetContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfContentCharacterSetContainsWords parameter specifies an exception for the rule that looks for character set names in messages.
To specify multiple words, this parameter uses the syntax: `Word1,word2,...wordN`. Don't use leading or trailing spaces.
@@ -1260,6 +1172,7 @@ Supported character sets are `big5, din_66003, euc-jp, euc-kr, gb18030, gb2312,
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1269,9 +1182,6 @@ Accept wildcard characters: False
```
### -ExceptIfContentContainsSensitiveInformation
-
-> Applicable: Security & Compliance
-
The ExceptIfContentContainsSensitiveInformation parameter specifies an exception for the rule that's based on a sensitive information type match in content. The rule isn't applied to content that contains the specified sensitive information type. In addition to sensitive information type, the parameter can also be applied to files that contain sensitivity labels.
This parameter uses the basic syntax `@(@{Name="SensitiveInformationType1";[minCount="Value"],@{Name="SensitiveInformationType2";[minCount="Value"],...)`. For example, `@(@{Name="U.S. Social Security Number (SSN)"; minCount="2"},@{Name="Credit Card Number"})`. Example for sensitivity label: `@(@{operator = "And"; groups = @(@{operator="Or";name="Default";labels=@(@{name="Confidential";type="Sensitivity"})})})`.
@@ -1282,6 +1192,7 @@ Use the Get-DLPSensitiveInformationType cmdlet to list the sensitive information
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1291,15 +1202,13 @@ Accept wildcard characters: False
```
### -ExceptIfContentExtensionMatchesWords
-
-> Applicable: Security & Compliance
-
The ExceptIfContentExtensionMatchesWords parameter specifies an exception for the DLP rule that looks for words in file extensions. You can specify multiple words separated by commas. Irrespective of what the original file type is, this predicate matches based on the extension that is present in the name of the file.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1309,15 +1218,13 @@ Accept wildcard characters: False
```
### -ExceptIfContentFileTypeMatches
-
-> Applicable: Security & Compliance
-
{{ Fill ExceptIfContentFileTypeMatches Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1327,9 +1234,6 @@ Accept wildcard characters: False
```
### -ExceptIfContentIsShared
-
-> Applicable: Security & Compliance
-
The ContentIsNotLabeled parameter specifies an exception for the DLP rule that looks for attachments or documents that aren't labeled. Valid values are:
- $true: Look for attachments or documents that aren't labeled.
@@ -1341,6 +1245,7 @@ In Exchange, this condition is matched only if both the attachment and the messa
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1350,9 +1255,6 @@ Accept wildcard characters: False
```
### -ExceptIfContentPropertyContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfContentPropertyContainsWords parameter specifies an exception for the DLP rule that's based on a property match in content. The rule is not applied to content that contains the specified property.
This parameter accepts values in the format: `"Property1:Value1,Value2","Property2:Value3,Value4",..."PropertyN:ValueN,ValueN"`.
@@ -1361,6 +1263,7 @@ This parameter accepts values in the format: `"Property1:Value1,Value2","Propert
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1370,9 +1273,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentContainsWords parameter specifies an exception for the DLP rule that looks for words in message attachments. Only supported attachment types are checked.
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -1383,6 +1283,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1392,9 +1293,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentCreatedBy
-
-> Applicable: Security & Compliance
-
The DocumentCreatedBy parameter specifies an exception for the DLP rule that looks for documents that are created by the specificed identity. You can specify multiple values separated by commas.
This parameter applies to Sharepoint and Onedrive workloads.
@@ -1403,6 +1301,7 @@ This parameter applies to Sharepoint and Onedrive workloads.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1412,9 +1311,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentCreatedByMemberOf
-
-> Applicable: Security & Compliance
-
The DocumentCreatedByMemberOf parameter specifies an exception for the DLP rule that looks for documents that are created by a member of the specificed group. You can specify multiple values separated by commas.
This parameter applies to Sharepoint and Onedrive workloads.
@@ -1423,6 +1319,7 @@ This parameter applies to Sharepoint and Onedrive workloads.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1432,9 +1329,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentIsPasswordProtected
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentIsPasswordProtected parameter specifies an exception for the DLP rule that looks for password protected files (because the contents of the file can't be inspected). Password detection works for Office documents, compressed files (.zip, .7z, .rar, .tar, etc.), and .pdf files. Valid values are:
- $true: Look for password protected files.
@@ -1444,6 +1338,7 @@ The ExceptIfDocumentIsPasswordProtected parameter specifies an exception for the
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1453,9 +1348,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentIsUnsupported
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentIsUnsupported parameter specifies an exception for the DLP rule that looks for files that can't be scanned. Valid values are:
- $true: Look for unsupported files that can't be scanned.
@@ -1465,6 +1357,7 @@ The ExceptIfDocumentIsUnsupported parameter specifies an exception for the DLP r
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1474,9 +1367,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentNameMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentNameMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in the name of message attachments by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 300.
@@ -1485,6 +1375,7 @@ The maximum individual regular expression length is 128 characters. The maximum
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1494,9 +1385,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in the content of message attachments by using regular expressions. Only supported attachment types are checked.
You can specify multiple text patterns by using the following syntax: `"Regular expression1","Regular expression2",..."Regular expressionN"`.
@@ -1507,6 +1395,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1516,9 +1405,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentNameMatchesWords
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentNameMatchesWords parameter specifies an exception for the DLP rule that looks for words or phrases in the name of message attachments. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -1531,6 +1417,7 @@ The maximum individual word or phrase length is 128 characters. The maximum numb
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1540,9 +1427,6 @@ Accept wildcard characters: False
```
### -ExceptIfDocumentSizeOver
-
-> Applicable: Security & Compliance
-
The ExceptIfDocumentSizeOver parameter specifies an exception for the DLP rule that looks for messages where any attachment is greater than the specified size.
When you enter a value, qualify the value with one of the following units:
@@ -1561,6 +1445,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: Microsoft.Exchange.Data.ByteQuantifiedSize
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1570,9 +1455,6 @@ Accept wildcard characters: False
```
### -ExceptIfFrom
-
-> Applicable: Security & Compliance
-
The ExceptIfFrom parameter specifies an exception for the DLP rule that looks for messages from specific senders. You identify the senders by email address. You can specify multiple values separated by commas.
You can use this exception in DLP policies that are scoped only to Exchange.
@@ -1581,6 +1463,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1590,9 +1473,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromAddressContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfFromAddressContainsWords parameter specifies an exception for the DLP rule that looks for words or phrases in the sender's email address. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -1607,6 +1487,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1616,9 +1497,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromAddressMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfFromAddressMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in the sender's email address by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 300.
@@ -1629,6 +1507,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1638,9 +1517,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromMemberOf
-
-> Applicable: Security & Compliance
-
The FromMemberOf parameter specifies an exception for the DLP rule that looks for messages sent by group members. You identify the group by its email address.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -1649,6 +1525,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1658,9 +1535,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromScope
-
-> Applicable: Security & Compliance
-
The ExceptIfFromScope parameter specifies an exception for the rule that looks for the location of message senders. Valid values are:
- InOrganization: The sender is a mailbox, mail user, group, or mail-enabled public folder in your organization or The sender's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain.
@@ -1672,6 +1546,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.FromScope
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1681,9 +1556,6 @@ Accept wildcard characters: False
```
### -ExceptIfHasSenderOverride
-
-> Applicable: Security & Compliance
-
The ExceptIfHasSenderOverride parameter specifies an exception for the rule that looks for messages where the sender chose to override a DLP policy. Valid values are:
- $true: Look for messages where the sender took action to override a DLP policy.
@@ -1695,6 +1567,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1704,9 +1577,6 @@ Accept wildcard characters: False
```
### -ExceptIfHeaderContainsWords
-
-> Applicable: Security & Compliance
-
The HeaderContainsWords parameter specifies an exception for the DLP rule that looks for words in a header field.
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -1717,6 +1587,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1726,9 +1597,6 @@ Accept wildcard characters: False
```
### -ExceptIfHeaderMatchesPatterns
-
-> Applicable: Security & Compliance
-
The HeaderMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in a header field by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1","regular expression2",..."regular expressionN"`.
You can use this exception in DLP policies that are scoped only to Exchange.
@@ -1737,6 +1605,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1746,9 +1615,6 @@ Accept wildcard characters: False
```
### -ExceptIfMessageSizeOver
-
-> Applicable: Security & Compliance
-
The ExceptIfMessageSizeOver parameter specifies an exception for the DLP rule that looks for messages larger than the specified size. The size include the message and all attachments.
When you enter a value, qualify the value with one of the following units:
@@ -1767,6 +1633,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: Microsoft.Exchange.Data.ByteQuantifiedSize
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1776,9 +1643,6 @@ Accept wildcard characters: False
```
### -ExceptIfMessageTypeMatches
-
-> Applicable: Security & Compliance
-
The ExceptIfMessageTypeMatches parameter specifies an exception for the rule that looks for messages of the specified type. Valid values are:
- ApprovalRequest: Moderation request messages sent to moderators.
@@ -1796,6 +1660,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.MessageTypes
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1805,9 +1670,6 @@ Accept wildcard characters: False
```
### -ExceptIfProcessingLimitExceeded
-
-> Applicable: Security & Compliance
-
The ExceptIfProcessingLimitExceeded parameter specifies an exception for the DLP rule that looks for files where scanning couldn't complete. Valid values are:
- $true: Look for files where scanning couldn't complete.
@@ -1817,6 +1679,7 @@ The ExceptIfProcessingLimitExceeded parameter specifies an exception for the DLP
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1826,9 +1689,6 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientADAttributeContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfRecipientADAttributeContainsWords parameter specifies an exception for the DLP rule that looks for words in Active Directory attributes of message recipients. You can use any of the following Active Directory attributes:
- City
@@ -1869,6 +1729,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1878,9 +1739,6 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientADAttributeMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfRecipientADAttributeMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in Active Directory attributes of message recipients by using regular expressions. You can use any of the following Active Directory attributes:
- City
@@ -1921,6 +1779,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1930,15 +1789,13 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientDomainIs
-
-> Applicable: Security & Compliance
-
The ExceptIfRecipientDomainIs parameter specifies an exception for the DLP rule that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -1948,9 +1805,6 @@ Accept wildcard characters: False
```
### -ExceptIfSenderADAttributeContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfSenderADAttributeContainsWords parameter specifies an exception for the DLP rule that looks for words in Active Directory attributes of message senders. You can use any of the following Active Directory attributes:
- City
@@ -1991,6 +1845,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2000,9 +1855,6 @@ Accept wildcard characters: False
```
### -ExceptIfSenderADAttributeMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfSenderADAttributeMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in Active Directory attributes of message senders by using regular expressions. You can use any of the following Active Directory attributes:
- City
@@ -2043,6 +1895,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2052,9 +1905,6 @@ Accept wildcard characters: False
```
### -ExceptIfSenderDomainIs
-
-> Applicable: Security & Compliance
-
The ExceptIfSenderDomainIs parameter specifies an exception for the DLP rule that looks for messages from senders with email address in the specified domains. You can specify multiple values separated by commas.
You can use this exception in DLP policies that are scoped only to Exchange.
@@ -2063,6 +1913,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2072,9 +1923,6 @@ Accept wildcard characters: False
```
### -ExceptIfSenderIPRanges
-
-> Applicable: Security & Compliance
-
The ExceptIfSenderIpRanges parameter specifies an exception for the DLP rule that looks for senders whose IP addresses matches the specified value, or fall within the specified ranges. Valid values are:
- Single IP address: For example, 192.168.1.1.
@@ -2087,6 +1935,7 @@ You can specify values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2096,9 +1945,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentTo
-
-> Applicable: Security & Compliance
-
The ExceptIfSentTo parameter specifies an exception for the DLP rule that looks for recipients in messages. You identify the recipients by email address. You can specify multiple values separated by commas.
You can use this exception in DLP policies that are scoped only to Exchange.
@@ -2107,6 +1953,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2116,9 +1963,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentToMemberOf
-
-> Applicable: Security & Compliance
-
The ExceptIfSentToMemberOf parameter specifies an exception for the DLP rule that looks for messages sent to members of distribution groups, dynamic distribution groups, or mail-enabled security groups. You identify the groups by email address. You can specify multiple values separated by commas.
You can use this exception in DLP policies that are scoped only to Exchange.
@@ -2127,6 +1971,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2136,9 +1981,6 @@ Accept wildcard characters: False
```
### -ExceptIfSubjectContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfSubjectContainsWords parameter specifies an exception for the DLP rule that looks for words or phrases in the Subject field of messages. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -2153,6 +1995,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2162,9 +2005,6 @@ Accept wildcard characters: False
```
### -ExceptIfSubjectMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfSubjectMatchesPatterns parameter specifies an exception for the DLP rule that looks for text patterns in the Subject field of messages by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 300.
@@ -2175,6 +2015,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2184,9 +2025,6 @@ Accept wildcard characters: False
```
### -ExceptIfSubjectOrBodyContainsWords
-
-> Applicable: Security & Compliance
-
The ExceptIfSubjectOrBodyContainsWords parameter specifies an exception for the rule that looks for words in the Subject field or body of messages.
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -2197,6 +2035,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type:
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2206,9 +2045,6 @@ Accept wildcard characters: False
```
### -ExceptIfSubjectOrBodyMatchesPatterns
-
-> Applicable: Security & Compliance
-
The ExceptIfSubjectOrBodyMatchesPatterns parameter specifies an exception for the rule that looks for text patterns in the Subject field or body of messages. You can specify multiple text patterns by using the following syntax: `"regular expression1","regular expression2",..."regular expressionN"`.
You can use this exception in DLP policies that are scoped only to Exchange.
@@ -2217,6 +2053,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type:
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2226,9 +2063,6 @@ Accept wildcard characters: False
```
### -ExceptIfUnscannableDocumentExtensionIs
-
-> Applicable: Security & Compliance
-
The ExceptIfUnscannableDocumentExtensionIs parameter specifies an exception for the rule that looks for the specified true file extension when the files aren't scannable. Irrespective of what the original file type is, this predicate matches based on the extension that is present in the name of the file.
You can specify multiple values separated by commas.
@@ -2237,6 +2071,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2246,9 +2081,6 @@ Accept wildcard characters: False
```
### -ExceptIfWithImportance
-
-> Applicable: Security & Compliance
-
The ExceptIfWithImportance parameter specifies an exception for the rule that looks for messages with the specified importance level. Valid values are:
- Low
@@ -2261,6 +2093,7 @@ You can use this exception in DLP policies that are scoped only to Exchange.
Type: Microsoft.Office.CompliancePolicy.Tasks.WithImportance
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2270,15 +2103,13 @@ Accept wildcard characters: False
```
### -ExpiryDate
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: System.DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2288,9 +2119,6 @@ Accept wildcard characters: False
```
### -From
-
-> Applicable: Security & Compliance
-
The From parameter specifies a condition for the DLP rule that looks for messages from specific senders. You identify the senders by email address. You can specify multiple values separated by commas.
You can use this condition in DLP policies that are scoped only to Exchange.
@@ -2299,6 +2127,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2308,9 +2137,6 @@ Accept wildcard characters: False
```
### -FromAddressContainsWords
-
-> Applicable: Security & Compliance
-
The FromAddressContainsWords parameter specifies a condition for the DLP rule that looks for words or phrases in the sender's email address. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -2325,6 +2151,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2334,9 +2161,6 @@ Accept wildcard characters: False
```
### -FromAddressMatchesPatterns
-
-> Applicable: Security & Compliance
-
The FromAddressMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in the sender's email address by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 300.
@@ -2347,6 +2171,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2356,9 +2181,6 @@ Accept wildcard characters: False
```
### -FromMemberOf
-
-> Applicable: Security & Compliance
-
The FromMemberOf parameter specifies a condition for the DLP rule that looks for messages sent by group members. You identify the group by its email address.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -2367,6 +2189,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: SmtpAddress[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2376,9 +2199,6 @@ Accept wildcard characters: False
```
### -FromScope
-
-> Applicable: Security & Compliance
-
The FromScope parameter specifies a condition for the rule that looks for the location of message senders. Valid values are:
- InOrganization: The sender is a mailbox, mail user, group, or mail-enabled public folder in your organization or The sender's email address is in an accepted domain that's configured as an authoritative domain or an internal relay domain.
@@ -2390,6 +2210,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.FromScope
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2399,9 +2220,6 @@ Accept wildcard characters: False
```
### -GenerateAlert
-
-> Applicable: Security & Compliance
-
The GenerateAlert parameter specifies an action for the DLP rule that notifies the specified users when the conditions of the rule are met. Valid values are:
- An email address.
@@ -2415,6 +2233,7 @@ The email message that's generated by this action contains a link to detailed in
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2424,9 +2243,6 @@ Accept wildcard characters: False
```
### -GenerateIncidentReport
-
-> Applicable: Security & Compliance
-
The GenerateIncidentReport parameter specifies an action for the DLP rule that sends an incident report to the specified users when the conditions of the rule are met. Valid values are:
- An email address.
@@ -2438,6 +2254,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2447,9 +2264,6 @@ Accept wildcard characters: False
```
### -HasSenderOverride
-
-> Applicable: Security & Compliance
-
The SenderOverride parameter specifies a condition for the rule that looks for messages where the sender chose to override a DLP policy. Valid values are:
- $true: Look for messages where the sender took action to override a DLP policy.
@@ -2461,6 +2275,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2470,9 +2285,6 @@ Accept wildcard characters: False
```
### -HeaderContainsWords
-
-> Applicable: Security & Compliance
-
The HeaderContainsWords parameter specifies a condition for the DLP rule that looks for words in a header field.
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -2483,6 +2295,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2492,9 +2305,6 @@ Accept wildcard characters: False
```
### -HeaderMatchesPatterns
-
-> Applicable: Security & Compliance
-
The HeaderMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in a header field by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1","regular expression2",..."regular expressionN"`.
You can use this condition in DLP policies that are scoped only to Exchange.
@@ -2503,6 +2313,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2512,15 +2323,13 @@ Accept wildcard characters: False
```
### -ImmutableId
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: System.Guid
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2530,9 +2339,6 @@ Accept wildcard characters: False
```
### -IncidentReportContent
-
-> Applicable: Security & Compliance
-
The IncidentReportContent parameter specifies the content to include in the report when you use the GenerateIncidentReport parameter. Valid values are:
- All
@@ -2562,6 +2368,7 @@ Therefore, any additional values that you use with the value "Default" are ignor
Type: ReportContentOption[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2571,15 +2378,13 @@ Accept wildcard characters: False
```
### -MessageIsNotLabeled
-
-> Applicable: Security & Compliance
-
{{ Fill MessageIsNotLabeled Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2589,9 +2394,6 @@ Accept wildcard characters: False
```
### -MessageSizeOver
-
-> Applicable: Security & Compliance
-
The MessageSizeOver parameter specifies a condition for the DLP rule that looks for messages larger than the specified size. The size include the message and all attachments.
When you enter a value, qualify the value with one of the following units:
@@ -2610,6 +2412,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: Microsoft.Exchange.Data.ByteQuantifiedSize
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2619,9 +2422,6 @@ Accept wildcard characters: False
```
### -MessageTypeMatches
-
-> Applicable: Security & Compliance
-
The MessageTypeMatches parameter specifies a condition for the rule that looks for messages of the specified type. Valid values are:
- ApprovalRequest: Moderation request messages sent to moderators.
@@ -2639,6 +2439,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MessageTypes
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2648,15 +2449,13 @@ Accept wildcard characters: False
```
### -MipRestrictAccess
-
-> Applicable: Security & Compliance
-
{{ Fill MipRestrictAccess Description }}
```yaml
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2666,9 +2465,6 @@ Accept wildcard characters: False
```
### -Moderate
-
-> Applicable: Security & Compliance
-
The Moderate parameter specifies an action for the DLP rule that sends the email message to a moderator. This parameter uses the syntax: `@{ModerateMessageByManager = <$true | $false>; ModerateMessageByUser = "emailaddress1,emailaddress2,...emailaddressN"}`.
You can use this action in DLP policies that are scoped only to Exchange.
@@ -2677,6 +2473,7 @@ You can use this action in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2686,9 +2483,6 @@ Accept wildcard characters: False
```
### -ModifySubject
-
-> Applicable: Security & Compliance
-
The ModifySubject parameter uses regular expressions to find text patterns in the subject of the email message, and then modifies the subject with the text that you specify. This parameter uses the syntax: `@{Patterns="RegEx1","RegEx2",..."RegEx10}"; SubjectText="Replacement Text"; ReplaceStrategy="Value"}`.
The `ReplaceStrategy=` property uses one of the following values:
@@ -2703,6 +2497,7 @@ The maximum individual regular expression length is 128 characters. The maximum
Type: PswsHashtable
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2712,9 +2507,6 @@ Accept wildcard characters: False
```
### -NonBifurcatingAccessScope
-
-> Applicable: Security & Compliance
-
The NonBifurcatingAccessScope parameter specifies a condition for the DLP rule that looks for recipients in the specified access scope. The rule is applied to all copies of the message. Valid values are:
- HasInternal: At least one recipient is inside the organization.
@@ -2727,6 +2519,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: Microsoft.Office.CompliancePolicy.Tasks.NonBifurcatingAccessScope
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2736,9 +2529,6 @@ Accept wildcard characters: False
```
### -NotifyAllowOverride
-
-> Applicable: Security & Compliance
-
The NotifyAllowOverride parameter specifies the notification override options when the conditions of the rule are met. Valid values are:
- FalsePositive: Allows overrides in the case of false positives.
@@ -2752,6 +2542,7 @@ You can specify multiple values separated by commas. The values WithoutJustifica
Type: OverrideOption[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2761,15 +2552,13 @@ Accept wildcard characters: False
```
### -NotifyEmailCustomSenderDisplayName
-
-> Applicable: Security & Compliance
-
{{ Fill NotifyEmailCustomSenderDisplayName Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2779,15 +2568,13 @@ Accept wildcard characters: False
```
### -NotifyEmailCustomSubject
-
-> Applicable: Security & Compliance
-
The NotifyEmailCustomSubject parameter specifies the custom text in the subject line of email notification message that's sent to recipients when the conditions of the rule are met.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2797,9 +2584,6 @@ Accept wildcard characters: False
```
### -NotifyEmailCustomText
-
-> Applicable: Security & Compliance
-
The NotifyEmailCustomText parameter specifies the custom text in the email notification message that's sent to recipients when the conditions of the rule are met.
This parameter has a 5000 character limit, and supports plain text, HTML tags, and the following tokens (variables):
@@ -2813,6 +2597,7 @@ This parameter has a 5000 character limit, and supports plain text, HTML tags, a
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2822,15 +2607,13 @@ Accept wildcard characters: False
```
### -NotifyEmailExchangeIncludeAttachment
-
-> Applicable: Security & Compliance
-
{{ Fill NotifyEmailExchangeIncludeAttachment Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2840,15 +2623,13 @@ Accept wildcard characters: False
```
### -NotifyEmailOnedriveRemediationActions
-
-> Applicable: Security & Compliance
-
{{ Fill NotifyEmailOnedriveRemediationActions Description }}
```yaml
Type: NotifyEmailRemediationActions
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2858,9 +2639,6 @@ Accept wildcard characters: False
```
### -NotifyEndpointUser
-
-> Applicable: Security & Compliance
-
**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
{{ Fill NotifyEndpointUser Description }}
@@ -2871,6 +2649,7 @@ For more information about Endpoint DLP, see [Learn about Endpoint data loss pre
Type: PswsHashtable
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2880,15 +2659,13 @@ Accept wildcard characters: False
```
### -NotifyOverrideRequirements
-
-> Applicable: Security & Compliance
-
{{ Fill NotifyOverrideRequirements Description }}
```yaml
Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyOverrideRequirements
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2898,15 +2675,13 @@ Accept wildcard characters: False
```
### -NotifyPolicyTipCustomDialog
-
-> Applicable: Security & Compliance
-
{{ Fill NotifyPolicyTipCustomDialog Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2916,15 +2691,13 @@ Accept wildcard characters: False
```
### -NotifyPolicyTipCustomText
-
-> Applicable: Security & Compliance
-
The NotifyPolicyTipCustomText parameter specifies the custom text in the Policy Tip notification message that's shown to recipients when the conditions of the rule are met. The maximum length is 256 characters. HTML tags and tokens (variables) aren't supported.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2934,9 +2707,6 @@ Accept wildcard characters: False
```
### -NotifyPolicyTipCustomTextTranslations
-
-> Applicable: Security & Compliance
-
The NotifyPolicyTipCustomTextTranslations parameter specifies the localized policy tip text that's shown when the conditions of the rule are met, based on the client settings. This parameter uses the syntax `CultureCode:Text`.
Valid culture codes are supported values from the Microsoft .NET Framework CultureInfo class. For example, da-DK for Danish or ja-JP for Japanese. For more information, see [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo).
@@ -2947,6 +2717,7 @@ To enter multiple values, use the following syntax: `"Value1","Value2",..."Value
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2956,9 +2727,6 @@ Accept wildcard characters: False
```
### -NotifyPolicyTipDisplayOption
-
-> Applicable: Security & Compliance
-
The NotifyPolicyTipDialogOption parameter specifies a display option for the policy tip. Valid values are:
- Tip: Displays policy tip at the top of the mail. This is the default value.
@@ -2968,6 +2736,7 @@ The NotifyPolicyTipDialogOption parameter specifies a display option for the pol
Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyTipDisplayOption
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2977,15 +2746,13 @@ Accept wildcard characters: False
```
### -NotifyPolicyTipUrl
-
-> Applicable: Security & Compliance
-
The NotifyPolicyTipUrl parameter specifies the URL in the popup dialog for Exchange workloads. This URL value has priority over the global: `Set-PolicyConfig -ComplianceUrl`.
```yaml
Type: String
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -2995,9 +2762,6 @@ Accept wildcard characters: False
```
### -NotifyUser
-
-> Applicable: Security & Compliance
-
The NotifyUser parameter specifies an action for the DLP rule that notifies the specified users when the conditions of the rule are met. Valid values are:
- An email address.
@@ -3011,6 +2775,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3020,9 +2785,6 @@ Accept wildcard characters: False
```
### -NotifyUserType
-
-> Applicable: Security & Compliance
-
The NotifyUserType parameter specifies the type of notification that's used for the rule. Valid values are:
- NotSet
@@ -3034,6 +2796,7 @@ The NotifyUserType parameter specifies the type of notification that's used for
Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.NotifyUserType
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3043,15 +2806,13 @@ Accept wildcard characters: False
```
### -OnPremisesScannerDlpRestrictions
-
-> Applicable: Security & Compliance
-
{{ Fill OnPremisesScannerDlpRestrictions Description }}
```yaml
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3061,9 +2822,6 @@ Accept wildcard characters: False
```
### -PrependSubject
-
-> Applicable: Security & Compliance
-
The PrependSubject parameter specifies an action for the rule that adds text to add to the beginning of the Subject field of messages. The value for this parameter is text that you specify. If the text contains spaces, enclose the value in quotation marks (").
Consider ending the value for this parameter with a colon (:) and a space, or at least a space, to separate it from the original subject.
@@ -3074,6 +2832,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3083,9 +2842,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Security & Compliance
-
The Priority parameter specifies a priority value for the rule that determines the order of rule processing within the policy. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
Valid values and the default value for this parameter depend on the number of existing rules in the policy. For example, if there are 8 existing rules:
@@ -3100,6 +2856,7 @@ If you modify the priority value of a rule, the position of the rule in the list
Type: System.Int32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3109,9 +2866,6 @@ Accept wildcard characters: False
```
### -ProcessingLimitExceeded
-
-> Applicable: Security & Compliance
-
The ProcessingLimitExceeded parameter specifies a condition for the DLP rule that looks for files where scanning couldn't complete. You can use this condition to create rules that work together to identify and process messages where the content couldn't be fully scanned. Valid values are:
- $true: Look for files where scanning couldn't complete.
@@ -3121,6 +2875,7 @@ The ProcessingLimitExceeded parameter specifies a condition for the DLP rule tha
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3130,9 +2885,6 @@ Accept wildcard characters: False
```
### -Quarantine
-
-> Applicable: Security & Compliance
-
This parameter specifies an action or part of an action for the rule.
The Quarantine parameter specifies an action that quarantines messages. Valid values are:
@@ -3144,6 +2896,7 @@ The Quarantine parameter specifies an action that quarantines messages. Valid va
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3153,9 +2906,6 @@ Accept wildcard characters: False
```
### -RecipientADAttributeContainsWords
-
-> Applicable: Security & Compliance
-
The RecipientADAttributeContainsWords parameter specifies a condition for the DLP rule that looks for words in Active Directory attributes of message recipients. You can use any of the following Active Directory attributes:
- City
@@ -3196,6 +2946,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3205,9 +2956,6 @@ Accept wildcard characters: False
```
### -RecipientADAttributeMatchesPatterns
-
-> Applicable: Security & Compliance
-
The RecipientADAttributeMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in Active Directory attributes of message recipients by using regular expressions. You can use any of the following Active Directory attributes:
- City
@@ -3248,6 +2996,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3257,9 +3006,6 @@ Accept wildcard characters: False
```
### -RecipientCountOver
-
-> Applicable: Security & Compliance
-
The RecipientCountOver parameter specifies a condition for the DLP rule that looks for messages where the number of recipients is greater than the specified value. Groups are counted as one recipient.
You can use this condition in DLP policies that are scoped only to Exchange. In PowerShell, you can use this parameter only inside an Advanced Rule.
@@ -3268,6 +3014,7 @@ You can use this condition in DLP policies that are scoped only to Exchange. In
Type: UInt32
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3277,15 +3024,13 @@ Accept wildcard characters: False
```
### -RecipientDomainIs
-
-> Applicable: Security & Compliance
-
The RecipientDomainIs parameter specifies a condition for the DLP rule that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3295,9 +3040,6 @@ Accept wildcard characters: False
```
### -RedirectMessageTo
-
-> Applicable: Security & Compliance
-
The RedirectMessageTo parameter specifies an action for the DLP rule that redirects the message to the specified email address. You can specify multiple values separated by commas.
You can use this action in DLP policies that are scoped only to Exchange.
@@ -3306,6 +3048,7 @@ You can use this action in DLP policies that are scoped only to Exchange.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3315,9 +3058,6 @@ Accept wildcard characters: False
```
### -RemoveHeader
-
-> Applicable: Security & Compliance
-
The RemoveHeader parameter specifies an action for the DLP rule that removes a header field from the message header. This parameter uses the syntax `HeaderName` or `"HeaderName:HeaderValue"`.You can specify multiple header names or header name and value pairs separated by commas: `HeaderName1,"HeaderName2:HeaderValue2",HeaderName3,..."HeaderNameN:HeaderValueN"`.
The maximum header name length is 64 characters, and header names can't contains spaces or colons ( : ). The maximum header value length is 128 characters.
@@ -3328,6 +3068,7 @@ You can use this action in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3337,9 +3078,6 @@ Accept wildcard characters: False
```
### -RemoveRMSTemplate
-
-> Applicable: Security & Compliance
-
The RemoveRMSTemplate parameter specifies an action for the DLP rule that removes Microsoft Purview Message Encryption from messages and their attachments. Valid values are:
- $true: The message and attachments are decrypted.
@@ -3351,6 +3089,7 @@ You can use this action in DLP policies that are scoped only to Exchange.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3360,9 +3099,6 @@ Accept wildcard characters: False
```
### -ReportSeverityLevel
-
-> Applicable: Security & Compliance
-
The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are:
- None: You can't select this value if the rule has no actions configured.
@@ -3374,6 +3110,7 @@ The ReportSeverityLevel parameter specifies the severity level of the incident r
Type: RuleSeverity
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3383,15 +3120,13 @@ Accept wildcard characters: False
```
### -RestrictAccess
-
-> Applicable: Security & Compliance
-
{{ Fill RestrictAccess Description }}
```yaml
Type: System.Collections.Hashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3401,15 +3136,13 @@ Accept wildcard characters: False
```
### -RestrictBrowserAccess
-
-> Applicable: Security & Compliance
-
{{ Fill RestrictBrowserAccess Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3419,9 +3152,6 @@ Accept wildcard characters: False
```
### -RuleErrorAction
-
-> Applicable: Security & Compliance
-
The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are:
- Ignore
@@ -3432,6 +3162,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du
Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyRuleErrorAction
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3441,9 +3172,6 @@ Accept wildcard characters: False
```
### -SenderADAttributeContainsWords
-
-> Applicable: Security & Compliance
-
The SenderADAttributeContainsWords parameter specifies a condition for the DLP rule that looks for words in Active Directory attributes of message senders. You can use any of the following Active Directory attributes:
- City
@@ -3484,6 +3212,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3493,9 +3222,6 @@ Accept wildcard characters: False
```
### -SenderADAttributeMatchesPatterns
-
-> Applicable: Security & Compliance
-
The SenderADAttributeMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in Active Directory attributes of message senders by using regular expressions. You can use any of the following Active Directory attributes:
- City
@@ -3536,6 +3262,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3545,9 +3272,6 @@ Accept wildcard characters: False
```
### -SenderAddressLocation
-
-> Applicable: Security & Compliance
-
The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value.
@@ -3566,6 +3290,7 @@ Note that message envelope searching is available only for the following conditi
Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicySenderAddressLocation
Parameter Sets: Default
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3575,9 +3300,6 @@ Accept wildcard characters: False
```
### -SenderDomainIs
-
-> Applicable: Security & Compliance
-
The SenderDomainIs parameter specifies a condition for the DLP rule that looks for messages from senders with email address in the specified domains. You can specify multiple values separated by commas.
You can use this condition in DLP policies that are scoped only to Exchange.
@@ -3586,6 +3308,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3595,9 +3318,6 @@ Accept wildcard characters: False
```
### -SenderIPRanges
-
-> Applicable: Security & Compliance
-
The SenderIpRanges parameter specifies a condition for the DLP rule that looks for senders whose IP addresses matches the specified value or fall within the specified ranges. Valid values are:
- Single IP address: For example, 192.168.1.1.
@@ -3610,6 +3330,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3619,9 +3340,6 @@ Accept wildcard characters: False
```
### -SentTo
-
-> Applicable: Security & Compliance
-
The SentTo parameter specifies a condition for the DLP rule that looks for recipients in messages. You identify the recipients by email address. You can specify multiple values separated by commas.
You can use this condition in DLP policies that are scoped only to Exchange.
@@ -3630,6 +3348,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3639,9 +3358,6 @@ Accept wildcard characters: False
```
### -SentToMemberOf
-
-> Applicable: Security & Compliance
-
The SentToMemberOf parameter specifies a condition for the DLP rule that looks for messages sent to members of distribution groups, dynamic distribution groups, or mail-enabled security groups. You identify the groups by email address. You can specify multiple values separated by commas.
You can use this condition in DLP policies that are scoped only to Exchange.
@@ -3650,6 +3366,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3659,9 +3376,6 @@ Accept wildcard characters: False
```
### -SetHeader
-
-> Applicable: Security & Compliance
-
The SetHeader parameter specifies an action for the DLP rule that adds or modifies a header field and value in the message header. This parameter uses the syntax `"HeaderName:HeaderValue"`. You can specify multiple header name and value pairs separated by commas: `"HeaderName1:HeaderValue1",HeaderName2:HeaderValue2",..."HeaderNameN:HeaderValueN"`.
The maximum header name length is 64 characters, and header names can't contains spaces or colons ( : ). The maximum header value length is 128 characters.
@@ -3672,6 +3386,7 @@ You can use this action in DLP policies that are scoped only to Exchange.
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3681,9 +3396,6 @@ Accept wildcard characters: False
```
### -SharedByIRMUserRisk
-
-> Applicable: Security & Compliance
-
The SharedByIRMUserRisk parameter specifies the risk category of the user performing the violating action. Valid values are:
- FCB9FA93-6269-4ACF-A756-832E79B36A2A (Elevated Risk Level)
@@ -3696,6 +3408,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3705,9 +3418,6 @@ Accept wildcard characters: False
```
### -StopPolicyProcessing
-
-> Applicable: Security & Compliance
-
The StopPolicyProcessing parameter specifies an action that stops processing more DLP policy rules. Valid values are:
- $true: Stop processing more rules.
@@ -3717,6 +3427,7 @@ The StopPolicyProcessing parameter specifies an action that stops processing mor
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3726,9 +3437,6 @@ Accept wildcard characters: False
```
### -SubjectContainsWords
-
-> Applicable: Security & Compliance
-
The SubjectContainsWords parameter specifies a condition for the DLP rule that looks for words or phrases in the Subject field of messages. You can specify multiple words or phrases separated by commas.
- Single word: `"no_reply"`
@@ -3743,6 +3451,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3752,9 +3461,6 @@ Accept wildcard characters: False
```
### -SubjectMatchesPatterns
-
-> Applicable: Security & Compliance
-
The SubjectMatchesPatterns parameter specifies a condition for the DLP rule that looks for text patterns in the Subject field of messages by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`.
The maximum individual regular expression length is 128 characters. The maximum number of regular expressions is 300.
@@ -3765,6 +3471,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3774,9 +3481,6 @@ Accept wildcard characters: False
```
### -SubjectOrBodyContainsWords
-
-> Applicable: Security & Compliance
-
The SubjectOrBodyContainsWords parameter specifies a condition for the rule that looks for words in the Subject field or body of messages.
To specify multiple words or phrases, this parameter uses the syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -3787,6 +3491,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type:
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3796,9 +3501,6 @@ Accept wildcard characters: False
```
### -SubjectOrBodyMatchesPatterns
-
-> Applicable: Security & Compliance
-
The SubjectOrBodyMatchesPatterns parameter specifies a condition for the rule that looks for text patterns in the Subject field or body of messages. You can specify multiple text patterns by using the following syntax: `"regular expression1","regular expression2",..."regular expressionN"`.
You can use this condition in DLP policies that are scoped only to Exchange.
@@ -3807,6 +3509,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type:
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3816,15 +3519,13 @@ Accept wildcard characters: False
```
### -ThirdPartyAppDlpRestrictions
-
-> Applicable: Security & Compliance
-
{{ Fill ThirdPartyAppDlpRestrictions Description }}
```yaml
Type: PswsHashtable[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3834,15 +3535,13 @@ Accept wildcard characters: False
```
### -TriggerPowerAutomateFlow
-
-> Applicable: Security & Compliance
-
{{ Fill TriggerPowerAutomateFlow Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3852,9 +3551,6 @@ Accept wildcard characters: False
```
### -UnscannableDocumentExtensionIs
-
-> Applicable: Security & Compliance
-
The UnscannableDocumentExtensionIs parameter specifies a condition for the rule that looks for the specified true file extension when the files aren't scannable. Irrespective of the original file type, this predicate matches based on the extension that is present in the name of the file.
You can specify multiple values separated by commas.
@@ -3863,6 +3559,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3872,15 +3569,13 @@ Accept wildcard characters: False
```
### -ValidateRule
-
-> Applicable: Security & Compliance
-
{{ Fill ValidateRule Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3890,15 +3585,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -3908,9 +3601,6 @@ Accept wildcard characters: False
```
### -WithImportance
-
-> Applicable: Security & Compliance
-
The WithImportance parameter specifies a condition for the rule that looks for messages with the specified importance level. Valid values are:
- Low
@@ -3923,6 +3613,7 @@ You can use this condition in DLP policies that are scoped only to Exchange.
Type: Microsoft.Office.CompliancePolicy.Tasks.WithImportance
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpEdmSchema.md b/exchange/exchange-ps/exchange/New-DlpEdmSchema.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-DlpEdmSchema.md
rename to exchange/exchange-ps/exchange/New-DlpEdmSchema.md
index a4d2cedc0c..27c440830a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpEdmSchema.md
+++ b/exchange/exchange-ps/exchange/New-DlpEdmSchema.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpedmschema
applicable: Security & Compliance
+title: New-DlpEdmSchema
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpedmschema
-schema: 2.0.0
-title: New-DlpEdmSchema
+ms.reviewer:
---
# New-DlpEdmSchema
@@ -45,9 +44,6 @@ This example creates a new DLP EDM schema using the file named edm.xml in the fo
## PARAMETERS
### -FileData
-
-> Applicable: Security & Compliance
-
The FileData parameter specifies the DLP EDM schema that you want to import.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -56,6 +52,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -65,9 +62,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -77,6 +71,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -86,15 +81,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpFingerprint.md b/exchange/exchange-ps/exchange/New-DlpFingerprint.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DlpFingerprint.md
rename to exchange/exchange-ps/exchange/New-DlpFingerprint.md
index 3acf20af84..cbd457cd29 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpFingerprint.md
+++ b/exchange/exchange-ps/exchange/New-DlpFingerprint.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpfingerprint
applicable: Security & Compliance
+title: New-DlpFingerprint
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpfingerprint
-schema: 2.0.0
-title: New-DlpFingerprint
+ms.reviewer:
---
# New-DlpFingerprint
@@ -49,9 +48,6 @@ This example creates a new document fingerprint based on the file C:\\My Documen
## PARAMETERS
### -FileData
-
-> Applicable: Security & Compliance
-
The FileData parameter specifies the file to use as a document fingerprint.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -60,6 +56,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Security & Compliance
-
The Description parameter specifies a description for the document fingerprint.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -87,9 +82,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -99,6 +91,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -108,15 +101,13 @@ Accept wildcard characters: False
```
### -IsExact
-
-> Applicable: Security & Compliance
-
{{ Fill IsExact Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -126,15 +117,13 @@ Accept wildcard characters: False
```
### -ThresholdConfig
-
-> Applicable: Security & Compliance
-
{{ Fill ThresholdConfig Description }}
```yaml
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -144,15 +133,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md b/exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md
rename to exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md
index 143373bf26..10ac021e60 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md
+++ b/exchange/exchange-ps/exchange/New-DlpKeywordDictionary.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpkeyworddictionary
applicable: Security & Compliance
+title: New-DlpKeywordDictionary
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpkeyworddictionary
-schema: 2.0.0
-title: New-DlpKeywordDictionary
+ms.reviewer:
---
# New-DlpKeywordDictionary
@@ -64,15 +63,13 @@ This example creates a DLP keyword dictionary named Inappropriate Language from
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the DLP keyword dictionary. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -94,6 +88,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -103,15 +98,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Security & Compliance
-
The Description parameter specifies descriptive text for the DLP keyword dictionary. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -121,15 +114,13 @@ Accept wildcard characters: False
```
### -DoNotPersistKeywords
-
-> Applicable: Security & Compliance
-
{{ Fill DoNotPersistKeywords Description }}
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -139,15 +130,13 @@ Accept wildcard characters: False
```
### -FileData
-
-> Applicable: Security & Compliance
-
The FileData parameter specifies the terms that are used in the DLP keyword dictionary. This parameter requires a comma-separated list of values that's binary encoded in UTF-16. For more information, see the examples in this topic.
```yaml
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -157,15 +146,13 @@ Accept wildcard characters: False
```
### -Organization
-
-> Applicable: Security & Compliance
-
{{ Fill Organization Description }}
```yaml
Type: OrganizationIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -175,15 +162,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md b/exchange/exchange-ps/exchange/New-DlpPolicy.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md
rename to exchange/exchange-ps/exchange/New-DlpPolicy.md
index 6f345ee2f5..705a5e5e46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md
+++ b/exchange/exchange-ps/exchange/New-DlpPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dlppolicy
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-DlpPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlppolicy
-schema: 2.0.0
-title: New-DlpPolicy
+ms.reviewer:
---
# New-DlpPolicy
@@ -55,15 +54,13 @@ This example creates a new DLP policy named Contoso PII with the following value
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies a descriptive name for the DLP policy.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -85,6 +79,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -94,15 +89,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Description parameter specifies an optional description for the DLP policy.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -112,15 +105,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,9 +121,6 @@ Accept wildcard characters: False
```
### -Mode
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mode parameter specifies the action and notification level of the DLP policy. Valid values for this parameter are:
- Audit: The actions specified by the DLP policy aren't enforced when a message matches the conditions specified by the policy, and the Policy Tip isn't displayed to the user.
@@ -145,6 +133,7 @@ By default, the value of this parameter is set to Audit when you create a new DL
Type: RuleMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -154,9 +143,6 @@ Accept wildcard characters: False
```
### -Parameters
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Parameters parameter specifies the parameter values that are required by the DLP policy template that you specify using the Template or TemplateData parameters. DLP policy templates may contain parameters that need to be populated with values from your organization. For example, a DLP policy template may include an exception group that defines users who are exempt from the DLP policy.
This parameter uses the syntax: `@{Parameter1="Value1";Parameter2="Value2"...}`.
@@ -165,6 +151,7 @@ This parameter uses the syntax: `@{Parameter1="Value1";Parameter2="Value2"...}`.
Type: Hashtable
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -174,15 +161,13 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The State parameter enables or disables the DLP policy. Valid input for this parameter is Enabled or Disabled. By default, a new DLP policy that you create is enabled. If you want to create a disabled DLP policy, specify the value Disabled for this parameter.
```yaml
Type: RuleState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -192,15 +177,13 @@ Accept wildcard characters: False
```
### -Template
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Template parameter specifies the existing DLP policy template from which you can create a new DLP policy. You can't use the Template and TemplateData parameters in the same command.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -210,9 +193,6 @@ Accept wildcard characters: False
```
### -TemplateData
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The TemplateData parameter specifies an external DLP policy template file from which you can create a new DLP policy. You can't use the TemplateData and Template parameters in the same command.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -221,6 +201,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -230,15 +211,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationType.md b/exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationType.md
rename to exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md
index ce313eca7d..961c0d2e48 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationType.md
+++ b/exchange/exchange-ps/exchange/New-DlpSensitiveInformationType.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpsensitiveinformationtype
applicable: Security & Compliance
+title: New-DlpSensitiveInformationType
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype
-schema: 2.0.0
-title: New-DlpSensitiveInformationType
+ms.reviewer:
---
# New-DlpSensitiveInformationType
@@ -59,9 +58,6 @@ This example creates a new sensitive information type rule named "Contoso Employ
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a name for the sensitive information type rule. The value must be less than 256 characters.
The value of this parameter is used in the Policy Tip that's presented to users in Outlook on the web.
@@ -70,6 +66,7 @@ The value of this parameter is used in the Policy Tip that's presented to users
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -79,15 +76,13 @@ Accept wildcard characters: False
```
### -Fingerprints
-
-> Applicable: Security & Compliance
-
-The Fingerprints parameter specifies the byte-encoded files to use as document fingerprints. You can use multiple document fingerprints separated by commas. For instructions on how to import documents to use as templates for fingerprints, see [New-Fingerprint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-fingerprint) or the Examples section.
+The Fingerprints parameter specifies the byte-encoded files to use as document fingerprints. You can use multiple document fingerprints separated by commas. For instructions on how to import documents to use as templates for fingerprints, see [New-Fingerprint](https://learn.microsoft.com/powershell/module/exchange/new-fingerprint) or the Examples section.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Security & Compliance
-
The Description parameter specifies a description for the sensitive information type rule.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -115,15 +108,13 @@ Accept wildcard characters: False
```
### -FileData
-
-> Applicable: Security & Compliance
-
{{ Fill FileData Description }}
```yaml
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -133,9 +124,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -145,6 +133,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -154,15 +143,13 @@ Accept wildcard characters: False
```
### -IsExact
-
-> Applicable: Security & Compliance
-
{{ Fill IsExact Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -172,9 +159,6 @@ Accept wildcard characters: False
```
### -Locale
-
-> Applicable: Security & Compliance
-
The Locale parameter specifies the language that's associated with the sensitive information type rule.
Valid input for this parameter is a supported culture code value from the Microsoft .NET Framework CultureInfo class. For example, da-DK for Danish or ja-JP for Japanese. For more information, see [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo).
@@ -185,6 +169,7 @@ You can add additional language translations to the sensitive information type r
Type: CultureInfo
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -194,15 +179,13 @@ Accept wildcard characters: False
```
### -ThresholdConfig
-
-> Applicable: Security & Compliance
-
{{ Fill ThresholdConfig Description }}
```yaml
Type: PswsHashtable
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -212,15 +195,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationTypeRulePackage.md
rename to exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md
index caee5727d4..ff65bcc045 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpSensitiveInformationTypeRulePackage.md
+++ b/exchange/exchange-ps/exchange/New-DlpSensitiveInformationTypeRulePackage.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dlpsensitiveinformationtyperulepackage
applicable: Security & Compliance
+title: New-DlpSensitiveInformationTypeRulePackage
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtyperulepackage
-schema: 2.0.0
-title: New-DlpSensitiveInformationTypeRulePackage
+ms.reviewer:
---
# New-DlpSensitiveInformationTypeRulePackage
@@ -46,9 +45,6 @@ This example imports the sensitive information type rule package C:\\My Document
## PARAMETERS
### -FileData
-
-> Applicable: Security & Compliance
-
The FileData parameter specifies the sensitive information type rule package that you want to import.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -57,6 +53,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -66,9 +63,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -78,6 +72,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -87,15 +82,13 @@ Accept wildcard characters: False
```
### -MigrationId
-
-> Applicable: Security & Compliance
-
{{ Fill MigrationId Description }}
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -105,15 +98,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md
rename to exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md
index fa1137e12b..548bcc5965 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/exchange/New-DynamicDistributionGroup.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-dynamicdistributiongroup
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+title: New-DynamicDistributionGroup
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-dynamicdistributiongroup
-schema: 2.0.0
-title: New-DynamicDistributionGroup
+ms.reviewer:
---
# New-DynamicDistributionGroup
@@ -107,9 +106,6 @@ This example creates a dynamic distribution group named Washington Management Te
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Name parameter specifies the unique name of the dynamic distribution group. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
This value is also used for the DisplayName property if you don't use the DisplayName parameter.
@@ -118,6 +114,7 @@ This value is also used for the DisplayName property if you don't use the Displa
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -127,9 +124,6 @@ Accept wildcard characters: False
```
### -IncludedRecipients
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
- AllRecipients: This value can be used only by itself.
@@ -147,6 +141,7 @@ You need to use this parameter when you use any Conditional parameters as part o
Type: WellKnownRecipientType
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -156,9 +151,6 @@ Accept wildcard characters: False
```
### -RecipientFilter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -178,6 +170,7 @@ The maximum length for the RecipientFilter property is 2048 characters, includin
Type: String
Parameter Sets: CustomFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -187,9 +180,6 @@ Accept wildcard characters: False
```
### -Alias
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
The Alias value can contain letters, numbers and the following characters:
@@ -214,6 +204,7 @@ The Alias parameter never generates or updates the primary email address of a ma
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -223,9 +214,6 @@ Accept wildcard characters: False
```
### -ArbitrationMailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ArbitrationMailbox parameter specifies the arbitration mailbox that's used to manage the moderation process for this recipient. You can use any value that uniquely identifies the arbitration mailbox. For example:
@@ -245,6 +233,7 @@ The ArbitrationMailbox parameter specifies the arbitration mailbox that's used t
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -254,9 +243,6 @@ Accept wildcard characters: False
```
### -ConditionalCompany
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -267,6 +253,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -276,9 +263,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute1
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -289,6 +273,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -298,9 +283,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute10
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -311,6 +293,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -320,9 +303,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute11
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -333,6 +313,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -342,9 +323,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute12
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -355,6 +333,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -364,9 +343,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute13
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -377,6 +353,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -386,9 +363,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute14
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -399,6 +373,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -408,9 +383,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute15
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -421,6 +393,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -430,9 +403,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute2
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -443,6 +413,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -452,9 +423,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute3
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -465,6 +433,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -474,9 +443,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute4
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -487,6 +453,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -496,9 +463,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute5
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -509,6 +473,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -518,9 +483,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute6
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -531,6 +493,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -540,9 +503,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute7
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -553,6 +513,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -562,9 +523,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute8
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -575,6 +533,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -584,9 +543,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute9
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -597,6 +553,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -606,9 +563,6 @@ Accept wildcard characters: False
```
### -ConditionalDepartment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -619,6 +573,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -628,9 +583,6 @@ Accept wildcard characters: False
```
### -ConditionalStateOrProvince
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -641,6 +593,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -650,9 +603,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -662,6 +612,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -671,9 +622,6 @@ Accept wildcard characters: False
```
### -DirectMembershipOnly
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is available only in the cloud-based service.
This parameter is reserved for internal Microsoft use.
@@ -682,6 +630,7 @@ This parameter is reserved for internal Microsoft use.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -691,9 +640,6 @@ Accept wildcard characters: False
```
### -DisplayName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The DisplayName parameter specifies the display name of the dynamic distribution group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
If you don't use the DisplayName parameter, the value of the Name parameter is used for the display name.
@@ -702,6 +648,7 @@ If you don't use the DisplayName parameter, the value of the Name parameter is u
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -711,9 +658,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -722,6 +666,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -731,9 +676,6 @@ Accept wildcard characters: False
```
### -ModeratedBy
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
- Name
@@ -751,6 +693,7 @@ You use this parameter to specify at least one moderator when you set the Modera
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -760,9 +703,6 @@ Accept wildcard characters: False
```
### -ModerationEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
- $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
@@ -774,6 +714,7 @@ You use the ModeratedBy parameter to specify the moderators.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -783,9 +724,6 @@ Accept wildcard characters: False
```
### -OrganizationalUnit
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The OrganizationalUnit parameter specifies the organizational unit (OU) where the dynamic distribution group is created.
Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
@@ -805,6 +743,7 @@ If you don't use the RecipientContainer parameter, the location of the dynamic d
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -814,15 +753,13 @@ Accept wildcard characters: False
```
### -PrimarySmtpAddress
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
```yaml
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -832,9 +769,6 @@ Accept wildcard characters: False
```
### -RecipientContainer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The RecipientContainer parameter specifies a filter that's based on the recipient's location in Active Directory. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
- Name
@@ -852,6 +786,7 @@ Note that the RecipientContainer property can't be blank. The group is always li
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -861,9 +796,6 @@ Accept wildcard characters: False
```
### -SendModerationNotifications
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
- Always: Notify all senders when their messages aren't approved. This is the default value.
@@ -876,6 +808,7 @@ This parameter is only meaningful when moderation is enabled (the ModerationEnab
Type: TransportModerationNotificationFlags
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -885,15 +818,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md b/exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md
rename to exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md
index 93ddfc0f15..f070348810 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/exchange/New-EOPProtectionPolicyRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-eopprotectionpolicyrule
applicable: Exchange Online, Exchange Online Protection
+title: New-EOPProtectionPolicyRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-eopprotectionpolicyrule
-schema: 2.0.0
-title: New-EOPProtectionPolicyRule
+ms.reviewer:
---
# New-EOPProtectionPolicyRule
@@ -58,9 +57,6 @@ This example creates the rule for the Standard preset security policy. No restri
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Name parameter specifies a unique name for the rule. The maximum length is 64 characters.
By default, the rules are named Standard Preset Security Policy or Strict Preset Security Policy. Since you don't need to create rules other than those used by the Standard preset security policy or the Strict preset security policy, we highly recommend that you use the default rule names for clarity and consistency.
@@ -69,6 +65,7 @@ By default, the rules are named Standard Preset Security Policy or Strict Preset
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -78,9 +75,6 @@ Accept wildcard characters: False
```
### -AntiPhishPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AntiPhishPolicy parameter specifies the existing anti-phishing policy that's associated with the preset security policy.
If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-phishing policy will be one of the following values:
@@ -94,6 +88,7 @@ You can find the anti-phishing policy that's used by the Standard or Strict pres
Type: AntiPhishPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -103,9 +98,6 @@ Accept wildcard characters: False
```
### -HostedContentFilterPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HostedContentFilterPolicy parameter specifies the existing anti-spam policy that's associated with the preset security policy.
If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-spam policy will be one of the following values:
@@ -119,6 +111,7 @@ You can find the anti-spam policy that's used by the Standard or Strict preset s
Type: HostedContentFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -128,9 +121,6 @@ Accept wildcard characters: False
```
### -MalwareFilterPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HostedContentFilterPolicy parameter specifies the existing anti-malware policy that's associated with the preset security policy.
If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-malware policy will be one of the following values:
@@ -144,6 +134,7 @@ You can find the anti-malware policy that's used by the Standard or Strict prese
Type: MalwareFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -153,15 +144,13 @@ Accept wildcard characters: False
```
### -Comments
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Comments parameter specifies informative comments for the rule, such as what the rule is used for or how it has changed over time. The length of the comment can't exceed 1024 characters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -171,9 +160,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -183,6 +169,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -192,9 +179,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Enabled parameter specifies whether the rule is enabled. Valid values are:
- $true: The rule is enabled. The State value of the rule is Enabled. This is the default value.
@@ -209,6 +193,7 @@ After you create the rule, you turn on or turn off the preset security policy us
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -218,15 +203,13 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientDomainIs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -236,9 +219,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentTo
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -254,6 +234,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -263,9 +244,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentToMemberOf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfSentToMemberOf parameter specifies an exception that looks for messages sent to members of groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -283,6 +261,7 @@ If you remove the group after you create the rule, no exception is made for mess
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -292,9 +271,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
The default value for the rule that's associated with the Strict preset security policy is 0, and the default value for the rule that's associated with the Standard preset security policy is 1.
@@ -305,6 +281,7 @@ When you create the policy, you must use the default value.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -314,15 +291,13 @@ Accept wildcard characters: False
```
### -RecipientDomainIs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientDomainIs parameter specifies a condition that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -332,9 +307,6 @@ Accept wildcard characters: False
```
### -SentTo
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SentTo parameter specifies a condition that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -350,6 +322,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -359,9 +332,6 @@ Accept wildcard characters: False
```
### -SentToMemberOf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SentToMemberOf parameter specifies a condition that looks for messages sent to members of distribution groups, dynamic distribution groups, or mail-enabled security groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -379,6 +349,7 @@ If you remove the group after you create the rule, no action is taken on message
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -388,15 +359,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md b/exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md
rename to exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md
index 99729e8485..d888a64122 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/exchange/New-EcpVirtualDirectory.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-ecpvirtualdirectory
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-EcpVirtualDirectory
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-ecpvirtualdirectory
-schema: 2.0.0
-title: New-EcpVirtualDirectory
+ms.reviewer:
---
# New-EcpVirtualDirectory
@@ -55,15 +54,13 @@ This example creates the ECP virtual directory on the Exchange server named Serv
## PARAMETERS
### -AppPoolId
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AppPoolId parameter sets the IIS application pool where the ECP virtual directory runs. We recommend that you leave this parameter at its default setting.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -85,6 +79,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -94,15 +89,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -112,9 +105,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionFlags
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
- None: This is the default setting.
@@ -127,6 +117,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -136,9 +127,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionSPNList
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
- $null: This is the default value.
@@ -148,6 +136,7 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -157,9 +146,6 @@ Accept wildcard characters: False
```
### -ExtendedProtectionTokenChecking
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
@@ -172,6 +158,7 @@ The ExtendedProtectionTokenChecking parameter defines how you want to use Extend
Type: ExtendedProtectionTokenCheckingMode
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -181,9 +168,6 @@ Accept wildcard characters: False
```
### -ExternalUrl
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
This setting is important when Secure Sockets Layer (SSL) is used. You need to set this parameter to allow the Autodiscover service to return the URL for the ECP virtual directory.
@@ -192,6 +176,7 @@ This setting is important when Secure Sockets Layer (SSL) is used. You need to s
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -201,9 +186,6 @@ Accept wildcard characters: False
```
### -InternalUrl
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
This setting is important when SSL is used. You need to set this parameter to allow the Autodiscover service to return the URL for the ECP virtual directory.
@@ -212,6 +194,7 @@ This setting is important when SSL is used. You need to set this parameter to al
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -221,15 +204,13 @@ Accept wildcard characters: False
```
### -Path
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Path parameter sets the file system path of the ECP virtual directory. This parameter should be used with care and only when you must use a different file system path than the default.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -239,9 +220,6 @@ Accept wildcard characters: False
```
### -Role
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Role parameter species the configuration for the virtual directory. Valid values are:
- ClientAccess: Configure the virtual directory for the Client Access (frontend) services on the Mailbox server.
@@ -253,6 +231,7 @@ Client connections are proxied from the Client Access services to the backend se
Type: VirtualDirectoryRole
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -262,9 +241,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
- Name
@@ -278,6 +254,7 @@ You can't create an ECP virtual directory remotely. You can only create an ECP v
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -287,15 +264,13 @@ Accept wildcard characters: False
```
### -WebSiteName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WebSiteName parameter specifies the name of the IIS website where the ECP virtual directory is created.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -305,15 +280,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md b/exchange/exchange-ps/exchange/New-EdgeSubscription.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md
rename to exchange/exchange-ps/exchange/New-EdgeSubscription.md
index 9df879d76c..e7c67b1d70 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md
+++ b/exchange/exchange-ps/exchange/New-EdgeSubscription.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-edgesubscription
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-EdgeSubscription
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-edgesubscription
-schema: 2.0.0
-title: New-EdgeSubscription
+ms.reviewer:
---
# New-EdgeSubscription
@@ -70,9 +69,6 @@ This example also imports the Edge Subscription file generated in Example 1 to t
## PARAMETERS
### -AccountExpiryDuration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AccountExpiryDuration parameter specifies how soon the EdgeSync bootstrap replication account (ESBRA) created by this command will expire.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -83,6 +79,7 @@ The value for this parameter must be a minimum of 00:02:00 or 2 minutes. The def
Type: TimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -92,9 +89,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -104,6 +98,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -113,15 +108,13 @@ Accept wildcard characters: False
```
### -CreateInboundSendConnector
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The CreateInboundSendConnector parameter specifies whether to create the Send connector to connect the Edge Transport server and the Hub Transport servers. The default value is $true. The Send connector address space is set to "--", the smart hosts are set to "--", the Edge Transport server is set as the source server and Domain Name System (DNS) routing is disabled. This parameter is only used when you run the command on the Hub Transport server.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -131,15 +124,13 @@ Accept wildcard characters: False
```
### -CreateInternetSendConnector
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The CreateInternetSendConnector parameter specifies whether to create the Send connector to connect to the Internet. The default value is $true. The Send connector address space is set to all domains (\*), the Edge Transport server is set as the source server, and DNS routing is enabled. This parameter is only used when you run the command on the Hub Transport server.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -149,9 +140,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -160,6 +148,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -169,9 +158,6 @@ Accept wildcard characters: False
```
### -FileData
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The FileData parameter specifies the byte-encoded data object that contains the Edge Subscription file information.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -182,6 +168,7 @@ You can only use this parameter when you're running the command on a Mailbox ser
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -191,9 +178,6 @@ Accept wildcard characters: False
```
### -FileName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The FileName parameter specifies the full path of the Edge Subscription file.
You can only use this parameter when you're running this command on an Edge Transport server.
@@ -202,6 +186,7 @@ You can only use this parameter when you're running this command on an Edge Tran
Type: LongPath
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -211,9 +196,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
This switch is useful in the following scenarios:
@@ -225,6 +207,7 @@ This switch is useful in the following scenarios:
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -234,15 +217,13 @@ Accept wildcard characters: False
```
### -Site
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Site parameter specifies the name of the Active Directory site that contains the Mailbox servers with which the Edge Transport servers are associated. This parameter is used and required only when you run the command on a Mailbox server.
```yaml
Type: AdSiteIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -252,15 +233,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md b/exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md
rename to exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md
index a8168f3519..f961f43a6f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/exchange/New-EdgeSyncServiceConfig.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-edgesyncserviceconfig
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-EdgeSyncServiceConfig
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-edgesyncserviceconfig
-schema: 2.0.0
-title: New-EdgeSyncServiceConfig
+ms.reviewer:
---
# New-EdgeSyncServiceConfig
@@ -62,9 +61,6 @@ This example creates EdgeSync service settings with the following configuration:
## PARAMETERS
### -ConfigurationSyncInterval
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ConfigurationSyncInterval parameter specifies how frequently the EdgeSync service synchronizes configuration data. The default value is 3 minutes.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -73,6 +69,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -82,9 +79,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -94,6 +88,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -103,9 +98,6 @@ Accept wildcard characters: False
```
### -CookieValidDuration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The CookieValidDuration parameter specifies how long a cookie record is valid. The default value is 21 days.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -114,6 +106,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -123,15 +116,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -141,9 +132,6 @@ Accept wildcard characters: False
```
### -FailoverDCInterval
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The FailoverDCInterval parameter specifies how long EdgeSync waits before failing over to another domain controller if it can't read configuration data from Active Directory. The default value is 5 minutes.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -152,6 +140,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -161,9 +150,6 @@ Accept wildcard characters: False
```
### -LockDuration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LockDuration parameter specifies how long an instance of the EdgeSync service can maintain an exclusive lock on the synchronization rights. While an EdgeSync service maintains an exclusive lock on synchronization rights, no other EdgeSync service can take over synchronization. The default value is 6 minutes.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -172,6 +158,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -181,9 +168,6 @@ Accept wildcard characters: False
```
### -LockRenewalDuration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LockRenewalDuration parameter specifies how long before the expiry of an exclusive lock an EdgeSync service can renew the lock. The default value is 4 minutes.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -192,6 +176,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -201,15 +186,13 @@ Accept wildcard characters: False
```
### -LogEnabled
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LogEnabled parameter enables or disables the EdgeSync log. Valid input for this parameter is $true or $false. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -219,9 +202,6 @@ Accept wildcard characters: False
```
### -LogLevel
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LogLevel parameter specifies the EdgeSync logging level. Valid values are:
- None (This is the default value)
@@ -233,6 +213,7 @@ The LogLevel parameter specifies the EdgeSync logging level. Valid values are:
Type: EdgeSyncLoggingLevel
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -242,9 +223,6 @@ Accept wildcard characters: False
```
### -LogMaxAge
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LogMaxAge parameter specifies the maximum duration in days to keep the EdgeSyncLog files. Log files older than the specified value can be overwritten. The default value is 30 days.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -253,6 +231,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -262,9 +241,6 @@ Accept wildcard characters: False
```
### -LogMaxDirectorySize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LogMaxDirectorySize parameter specifies the maximum amount of disk space the EdgeSyncLog directory can use. The default value is 250 MB.
When you enter a value, qualify the value with one of the following units:
@@ -283,6 +259,7 @@ The value of the LogMaxFileSize parameter must be less than or equal to the valu
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -292,9 +269,6 @@ Accept wildcard characters: False
```
### -LogMaxFileSize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LogMaxFileSize parameter specifies the maximum log file size for the EdgeSyncLog files. The default value is 10 MB.
When you enter a value, qualify the value with one of the following units:
@@ -313,6 +287,7 @@ The value of the LogMaxFileSize parameter must be less than or equal to the valu
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -322,15 +297,13 @@ Accept wildcard characters: False
```
### -LogPath
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The LogPath parameter specifies the default location for the EdgeSyncLog files. The default value is TransportRoles\\Logs\\EdgeSync\\.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -340,9 +313,6 @@ Accept wildcard characters: False
```
### -OptionDuration
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OptionDuration parameter specifies how long an instance of the EdgeSync service can maintain an optional lock on synchronization rights. While an EdgeSync service maintains an optional lock on synchronization rights, another EdgeSync service can take over synchronization after the optional lock has expired if it's initiated using the Start-EdgeSynchronization command. The default value is 30 minutes.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -351,6 +321,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -360,9 +331,6 @@ Accept wildcard characters: False
```
### -RecipientSyncInterval
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The RecipientSyncInterval parameter specifies how frequently the EdgeSync service synchronizes recipient data from the global catalog. The default value is 5 minutes.
To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
@@ -371,6 +339,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
Type: EnhancedTimeSpan
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -380,15 +349,13 @@ Accept wildcard characters: False
```
### -Site
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Site parameter specifies the Active Directory site that EdgeSync connects to for synchronizing configuration and recipient data.
```yaml
Type: AdSiteIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -398,15 +365,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md b/exchange/exchange-ps/exchange/New-EmailAddressPolicy.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md
rename to exchange/exchange-ps/exchange/New-EmailAddressPolicy.md
index 6b5b760e67..966babe33d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/exchange/New-EmailAddressPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-emailaddresspolicy
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-EmailAddressPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-emailaddresspolicy
-schema: 2.0.0
-title: New-EmailAddressPolicy
+ms.reviewer:
---
# New-EmailAddressPolicy
@@ -174,15 +173,13 @@ This example creates an email address policy in an on-premises Exchange organiza
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies the unique name of the email address policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -192,9 +189,6 @@ Accept wildcard characters: False
```
### -EnabledEmailAddressTemplates
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The EnabledEmailAddressTemplates parameter specifies the rules in the email address policy that are used to generate email addresses for recipients.
Valid syntax for this parameter is `Type:AddressFormat`:
@@ -214,6 +208,7 @@ In Exchange Online PowerShell, you can't use variables in the email address temp
Type: ProxyAddressTemplateCollection
Parameter Sets: AllTemplatesWithPrecannedFilter, AllTemplatesWithCustomFilter, AllTemplatesForUnifiedGroupRecipientsFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -223,9 +218,6 @@ Accept wildcard characters: False
```
### -EnabledPrimarySMTPAddressTemplate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The EnabledPrimarySMTPAddressTemplate parameter specifies the rule in the email address policy that's used to generate the primary SMTP email addresses for recipients. You can use this parameter instead of the EnabledEmailAddressTemplates if the policy only applies the primary email address and no additional proxy addresses.
Valid syntax for this parameter is a domain or subdomain that's configured as an authoritative accepted domain, and valid variables and ASCII text characters as described in the "Address format" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: alias@contoso.com requires the value `%m@contoso.com`, and firstname.lastname@contoso.com requires the value `%g.%s@contoso.com`.
@@ -238,6 +230,7 @@ In Exchange Online PowerShell, you can't use variables in the email address temp
Type: String
Parameter Sets: SMTPTemplateWithPrecannedFilter, SMTPTemplateWithCustomFilter, SMTPTemplateForUnifiedGroupRecipientsFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -247,9 +240,6 @@ Accept wildcard characters: False
```
### -IncludedRecipients
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
@@ -269,6 +259,7 @@ You need to use this parameter when you use any Conditional parameters as part o
Type: WellKnownRecipientType
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -278,9 +269,6 @@ Accept wildcard characters: False
```
### -IncludeUnifiedGroupRecipients
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The IncludeUnifiedGroupRecipients switch specifies that the email address policy applies only to Microsoft 365 Groups. You don't need to specify a value with this switch.
@@ -291,6 +279,7 @@ In Exchange Online PowerShell, you always need to use this switch, because email
Type: SwitchParameter
Parameter Sets: AllTemplatesForUnifiedGroupRecipientsFilter, SMTPTemplateForUnifiedGroupRecipientsFilter
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -300,9 +289,6 @@ Accept wildcard characters: False
```
### -RecipientFilter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
@@ -322,6 +308,7 @@ You can't use this parameter in combination with the IncludedRecipients paramete
Type: String
Parameter Sets: AllTemplatesWithCustomFilter, SMTPTemplateWithCustomFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -331,9 +318,6 @@ Accept wildcard characters: False
```
### -ConditionalCompany
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property. You can specify multiple values separated by commas.
@@ -346,6 +330,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -355,9 +340,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute1
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
@@ -370,6 +352,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -379,9 +362,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute10
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
@@ -394,6 +374,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -403,9 +384,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute11
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
@@ -418,6 +396,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -427,9 +406,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute12
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
@@ -442,6 +418,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -451,9 +428,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute13
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
@@ -466,6 +440,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -475,9 +450,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute14
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
@@ -490,6 +462,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -499,9 +472,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute15
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
@@ -514,6 +484,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -523,9 +494,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute2
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
@@ -538,6 +506,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -547,9 +516,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute3
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
@@ -562,6 +528,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -571,9 +538,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute4
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
@@ -586,6 +550,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -595,9 +560,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute5
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
@@ -610,6 +572,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -619,9 +582,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute6
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
@@ -634,6 +594,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -643,9 +604,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute7
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
@@ -658,6 +616,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -667,9 +626,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute8
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
@@ -682,6 +638,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -691,9 +648,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute9
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
@@ -706,6 +660,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -715,9 +670,6 @@ Accept wildcard characters: False
```
### -ConditionalDepartment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
@@ -730,6 +682,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -739,9 +692,6 @@ Accept wildcard characters: False
```
### -ConditionalStateOrProvince
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
@@ -754,6 +704,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: AllTemplatesWithPrecannedFilter, SMTPTemplateWithPrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -763,9 +714,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -775,6 +723,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -784,9 +733,6 @@ Accept wildcard characters: False
```
### -DisabledEmailAddressTemplates
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DisabledEmailAddressTemplates parameter specifies the proxy email addresses templates that are included in an email address policy, but aren't used to configure the email addresses of recipients.
@@ -802,6 +748,7 @@ You can specify multiple disabled email address templates separated by commas: `
Type: ProxyAddressTemplateCollection
Parameter Sets: AllTemplatesWithPrecannedFilter, AllTemplatesWithCustomFilter, AllTemplatesForUnifiedGroupRecipientsFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -811,9 +758,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -822,6 +766,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -831,9 +776,6 @@ Accept wildcard characters: False
```
### -ManagedByFilter
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The ManagedByFilter parameter specifies the email address policies to apply to Microsoft 365 Groups based on the properties of the users who create the Microsoft 365 Groups.
@@ -856,6 +798,7 @@ You can only use this parameter in Exchange Online PowerShell with the IncludeUn
Type: String
Parameter Sets: AllTemplatesForUnifiedGroupRecipientsFilter, SMTPTemplateForUnifiedGroupRecipientsFilter
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -865,9 +808,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Priority parameter specifies the order that the email address policies are evaluated. By default, every time that you add a new email address policy, the policy is assigned a priority of N+1, where N is the number of email address policies that you've created.
If you set this parameter to a value that's the same as another email address policy, the priority of the policy that you added first is incremented by 1.
@@ -878,6 +818,7 @@ If you set this parameter to a value that's the same as another email address po
Type: EmailAddressPolicyPriority
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -887,9 +828,6 @@ Accept wildcard characters: False
```
### -RecipientContainer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RecipientContainer parameter specifies a filter that's based on the recipient's location in Active Directory. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
@@ -905,6 +843,7 @@ If you don't use this parameter, the default value is the OU where the object wa
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -914,15 +853,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md b/exchange/exchange-ps/exchange/New-ExchangeCertificate.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md
rename to exchange/exchange-ps/exchange/New-ExchangeCertificate.md
index 365938a134..5d957d9ce7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md
+++ b/exchange/exchange-ps/exchange/New-ExchangeCertificate.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-exchangecertificate
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-ExchangeCertificate
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-exchangecertificate
-schema: 2.0.0
-title: New-ExchangeCertificate
+ms.reviewer:
---
# New-ExchangeCertificate
@@ -181,9 +180,6 @@ This example creates a new DER encoded (binary) certificate renewal request file
## PARAMETERS
### -BinaryEncoded
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The BinaryEncoded switch specifies whether to encode the new certificate request by using Distinguished Encoding Rules (DER). You don't need to specify a value with this switch.
If you don't use this switch, the request is Base64 encoded.
@@ -196,6 +192,7 @@ For Base64 encoded requests, you send the contents of the file to the certificat
Type: SwitchParameter
Parameter Sets: Request
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -205,9 +202,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -217,6 +211,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -226,9 +221,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -237,6 +229,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -246,9 +239,6 @@ Accept wildcard characters: False
```
### -DomainName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainName parameter specifies one or more FQDNs or server names for theSubject Alternative Name field (also known as the Subject Alt Name or SAN field) of the certificate request or self-signed certificate.
If the value in the certificate's Subject field doesn't match the destination server name or FQDN, the requestor looks for a match in the Subject Alternative Name field.
@@ -264,6 +254,7 @@ The default value includes the name and FQDN of the Exchange server when both of
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -273,9 +264,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
By default, when you create a self-signed certificate that's enabled for SMTP (no Services parameter, or the Services parameter contains the value SMTP), you're prompted to replace the existing default SMTP certificate with the new one that you're creating. If you use the Force switch, the new SMTP certificate automatically replaces the existing SMTP certificate without asking.
@@ -284,6 +272,7 @@ By default, when you create a self-signed certificate that's enabled for SMTP (n
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -293,9 +282,6 @@ Accept wildcard characters: False
```
### -FriendlyName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The FriendlyName parameter specifies a friendly name for the certificate request or self-signed certificate. The value must be less than 64 characters.
The default value is Microsoft Exchange. The friendly name value is descriptive text, and doesn't affect the functionality of the certificate.
@@ -304,6 +290,7 @@ The default value is Microsoft Exchange. The friendly name value is descriptive
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -313,9 +300,6 @@ Accept wildcard characters: False
```
### -GenerateRequest
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The GenerateRequest switch specifies that you're creating a certificate request for a certification authority (CA). You don't need to specify a value with this switch.
Using this switch and exporting the output to a file generates a PKCS #10 certificate request that you send to the CA. How you send the information depends on the CA, but typically, for Base64 encoded requests, you paste the contents in an email message or in the request form on the CA's web site.
@@ -328,6 +312,7 @@ If you don't use this switch, the command creates a new self-signed certificate
Type: SwitchParameter
Parameter Sets: Request
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -337,9 +322,6 @@ Accept wildcard characters: False
```
### -IncludeAcceptedDomains
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeAcceptedDomains switch specifies that all accepted domains in the Exchange organization are included in the Subject Alternative Name field of the certificate request or self-signed certificate. You don't need to specify a value with this switch.
When you use this switch:
@@ -351,6 +333,7 @@ When you use this switch:
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -360,9 +343,6 @@ Accept wildcard characters: False
```
### -IncludeAutoDiscover
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeAutoDiscover switch specifies whether to add a Subject Alternative Namevalue with the prefix autodiscover for each accepted domain in the Exchange organization. You don't need to specify a value with this switch.
For example, if the organization has the accepted domains woodgrovebank.com and woodgrovebank.co.uk, using this switch results in the addition of the following values in the Subject Alternative Name field:
@@ -379,6 +359,7 @@ When you use this switch:
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -388,9 +369,6 @@ Accept wildcard characters: False
```
### -IncludeServerFQDN
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeServerFQDN switch specifies that the FQDN of the Exchange server is included in the Subject Alternative Name field of the new certificate request or self-signed certificate. You don't need to specify a value with this switch.
When you use this switch, and you've already included the server's FQDN in the DomainName parameter, the value isn't duplicated in the Subject Alternative Name field.
@@ -399,6 +377,7 @@ When you use this switch, and you've already included the server's FQDN in the D
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -408,9 +387,6 @@ Accept wildcard characters: False
```
### -IncludeServerNetBIOSName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IncludeServerNetBIOSName switch specifies that the NetBIOS name of the Exchange server is included in the Subject Alternative Name field of the new certificate request or self-signed certificate. You don't need to specify a value with this switch
When you use this switch, and you've already included the server's NetBIOS name in the DomainName parameter, the value isn't duplicated in the Subject Alternative Name field.
@@ -419,6 +395,7 @@ When you use this switch, and you've already included the server's NetBIOS name
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -428,15 +405,13 @@ Accept wildcard characters: False
```
### -Instance
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter has been deprecated and is no longer used.
```yaml
Type: X509Certificate2
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -446,9 +421,6 @@ Accept wildcard characters: False
```
### -KeySize
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The KeySize parameter specifies the size (in bits) of the RSA public key that's associated with the new certificate request or self-signed certificate. Valid values are:
- 1024
@@ -459,6 +431,7 @@ The KeySize parameter specifies the size (in bits) of the RSA public key that's
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -468,9 +441,6 @@ Accept wildcard characters: False
```
### -PrivateKeyExportable
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key, and controls whether you can export the certificate from the server (and import the certificate on other servers). Valid values are:
- $true: The private key is exportable, so you can export the certificate from the server.
@@ -480,6 +450,7 @@ The PrivateKeyExportable parameter specifies whether the certificate has an expo
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -489,9 +460,6 @@ Accept wildcard characters: False
```
### -RequestFile
-
-> Applicable: Exchange Server 2013
-
**Note**: This parameter was removed from Exchange 2016 and Exchange 2019 by the [2022 H1 Cumulative Updates](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-2022-h1-cumulative-updates-for-exchange-server/ba-p/3285026) because it accepts UNC path values. To export the certificate request to a file without using the RequestFile parameter, see Example 4 and Example 5 (new) or Example 7 and Example 8 (renew).
This parameter is available only in Exchange 2013.
@@ -506,6 +474,7 @@ You can use this parameter only when you use the GenerateRequest switch.
Type: String
Parameter Sets: Request
Aliases:
+Applicable: Exchange Server 2013
Required: False
Position: Named
@@ -515,9 +484,6 @@ Accept wildcard characters: False
```
### -Server
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
- Name
@@ -531,6 +497,7 @@ If you don't use this parameter, the command is run on the local server.
Type: ServerIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -540,9 +507,6 @@ Accept wildcard characters: False
```
### -Services
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Services parameter specifies the Exchange services that the new self-signed certificate is enabled for. Valid values are:
- None: You can enable the certificate for Exchange services later by using the Enable-ExchangeCertificate cmdlet.
@@ -564,6 +528,7 @@ Once you enable a certificate for a service, you can't remove the service from t
Type: AllowedServices
Parameter Sets: Certificate
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -573,15 +538,13 @@ Accept wildcard characters: False
```
### -SubjectKeyIdentifier
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SubjectKeyIdentifier parameter specifies the unique subject key identifier for a newself-signed certificate. For example, run the command: $ski = [System.Guid]::NewGuid().ToString("N"), and use the value $ski for this parameter.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -591,9 +554,6 @@ Accept wildcard characters: False
```
### -SubjectName
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SubjectName parameter specifies the Subject field of the certificate request or self-signed certificate.
Every certificate requires a value for the Subject field, and only one value is allowed. The requestor attempts to match the destination server name or FQDN with the common name (CN) value of subject.
@@ -616,6 +576,7 @@ For a wildcard certificate, use a SubjectName value that contains the wildcard c
Type: X500DistinguishedName
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -625,15 +586,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md b/exchange/exchange-ps/exchange/New-ExchangeSettings.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md
rename to exchange/exchange-ps/exchange/New-ExchangeSettings.md
index a39cde59db..abedc962ae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md
+++ b/exchange/exchange-ps/exchange/New-ExchangeSettings.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.ServerStatus-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-exchangesettings
applicable: Exchange Server 2016, Exchange Server 2019
+title: New-ExchangeSettings
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.ServerStatus-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-exchangesettings
-schema: 2.0.0
-title: New-ExchangeSettings
+ms.reviewer:
---
# New-ExchangeSettings
@@ -45,9 +44,6 @@ This example creates a new Exchange settings object for the Audit configuration
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies the name of a valid Exchange configuration schema that you want to create an Exchange settings object for. Valid values are
- ADDriver
@@ -64,6 +60,7 @@ The Name parameter specifies the name of a valid Exchange configuration schema t
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -73,9 +70,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -85,6 +79,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -94,15 +89,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -112,9 +105,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -123,6 +113,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -132,15 +123,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md
rename to exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md
index 1c3e6a1a8f..c126bc6fbf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md
+++ b/exchange/exchange-ps/exchange/New-ExoPhishSimOverrideRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-exophishsimoverriderule
applicable: Exchange Online
+title: New-ExoPhishSimOverrideRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-exophishsimoverriderule
-schema: 2.0.0
-title: New-ExoPhishSimOverrideRule
+ms.reviewer:
---
# New-ExoPhishSimOverrideRule
@@ -48,9 +47,6 @@ This example creates a new phishing simulation override rule with the specified
## PARAMETERS
### -Policy
-
-> Applicable: Exchange Online
-
The Policy parameter specifies the phishing simulation override policy that's associated with the rule. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -62,6 +58,7 @@ The Policy parameter specifies the phishing simulation override policy that's as
Type: PolicyIdParameter
Parameter Sets: Default, PublishComplianceTag, ComplianceTag, SetRawXml
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -71,9 +68,6 @@ Accept wildcard characters: False
```
### -SenderIpRanges
-
-> Applicable: Exchange Online
-
The SenderIpRanges parameter specifies the source IP address that's used by the non-Microsoft phishing simulation. Valid values are:
- Single IP address: For example, 192.168.1.1.
@@ -88,6 +82,7 @@ A phishing simulation entry requires at least one IP address in this parameter a
Type: MultiValuedProperty
Parameter Sets: Default
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -97,15 +92,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Exchange Online
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: Default
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -115,9 +108,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -127,6 +117,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -136,15 +127,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -154,9 +143,6 @@ Accept wildcard characters: False
```
### -Domains
-
-> Applicable: Exchange Online
-
The Domains parameter specifies the email domain that's used by the non-Microsoft phishing simulation. You can use either of the following values:
- The `5321.MailFrom` address (also known as the MAIL FROM address, P1 sender, or envelope sender).
@@ -170,6 +156,7 @@ A phishing simulation requires at least one domain from this parameter and at le
Type: MultiValuedProperty
Parameter Sets: Default
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -179,15 +166,13 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Online
-
The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:PhishSimOverr:` \[sic\] where \ is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329).
```yaml
Type: String
Parameter Sets: Default
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -197,15 +182,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md
rename to exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md
index 919af1904f..e962547317 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md
+++ b/exchange/exchange-ps/exchange/New-ExoSecOpsOverrideRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-exosecopsoverriderule
applicable: Exchange Online
+title: New-ExoSecOpsOverrideRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-exosecopsoverriderule
-schema: 2.0.0
-title: New-ExoSecOpsOverrideRule
+ms.reviewer:
---
# New-ExoSecOpsOverrideRule
@@ -47,9 +46,6 @@ This example creates the SecOps mailbox override rule with the specified setting
## PARAMETERS
### -Policy
-
-> Applicable: Exchange Online
-
The Policy parameter specifies the phishing simulation override policy that's associated with the rule. You can use any value that uniquely identifies the policy. For example:
- Name
@@ -61,6 +57,7 @@ The Policy parameter specifies the phishing simulation override policy that's as
Type: PolicyIdParameter
Parameter Sets: Default, PublishComplianceTag, ComplianceTag, SetRawXml
Aliases:
+Applicable: Exchange Online
Required: True
Position: Named
@@ -70,15 +67,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Exchange Online
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: Default
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -88,15 +83,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online
Required: False
Position: Named
@@ -106,15 +99,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -124,15 +115,13 @@ Accept wildcard characters: False
```
### -Name
-
-> Applicable: Exchange Online
-
The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:SecOpsOverrid:` \[sic\] where \ is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977ef).
```yaml
Type: String
Parameter Sets: Default
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -142,15 +131,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FeatureConfiguration.md b/exchange/exchange-ps/exchange/New-FeatureConfiguration.md
similarity index 95%
rename from exchange/exchange-ps/ExchangePowerShell/New-FeatureConfiguration.md
rename to exchange/exchange-ps/exchange/New-FeatureConfiguration.md
index bb04d6b1e3..2f093ab5f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FeatureConfiguration.md
+++ b/exchange/exchange-ps/exchange/New-FeatureConfiguration.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-featureconfiguration
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/new-featureconfiguration
+applicable: Security & Compliance
title: New-FeatureConfiguration
+schema: 2.0.0
---
# New-FeatureConfiguration
@@ -73,15 +71,13 @@ This example creates a disabled collection policy named "Scoped collection polic
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies the unique name for the feature configuration. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -91,9 +87,6 @@ Accept wildcard characters: False
```
### -FeatureScenario
-
-> Applicable: Security & Compliance
-
The FeatureScenario parameter specifies the scenario for the feature configuration. Currently, the only valid values are:
- `KnowYourData` for collection policies
- `TrustContainer` for Endpoint DLP trust container
@@ -102,6 +95,7 @@ The FeatureScenario parameter specifies the scenario for the feature configurati
Type: PolicyScenario
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -111,9 +105,6 @@ Accept wildcard characters: False
```
### -Mode
-
-> Applicable: Security & Compliance
-
The Mode parameter specifies feature configuration mode. Valid values are:
- Enable: The feature configuration is enabled.
@@ -123,6 +114,7 @@ The Mode parameter specifies feature configuration mode. Valid values are:
Type: PolicyMode
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -132,15 +124,13 @@ Accept wildcard characters: False
```
### -ScenarioConfig
-
-> Applicable: Security & Compliance
-
The ScenarioConfig parameter specifies additional information about the feature configuration.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -150,15 +140,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -168,9 +156,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -180,6 +165,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -189,15 +175,13 @@ Accept wildcard characters: False
```
### -Locations
-
-> Applicable: Security & Compliance
-
The locations parameter specifies where the feature configuration applies.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -207,15 +191,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md b/exchange/exchange-ps/exchange/New-FederationTrust.md
similarity index 88%
rename from exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md
rename to exchange/exchange-ps/exchange/New-FederationTrust.md
index 1ef2e0094b..b1f50c5c62 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md
+++ b/exchange/exchange-ps/exchange/New-FederationTrust.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-federationtrust
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-FederationTrust
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-federationtrust
-schema: 2.0.0
-title: New-FederationTrust
+ms.reviewer:
---
# New-FederationTrust
@@ -65,15 +64,13 @@ This example creates the federation trust Microsoft Federation Gateway with a ce
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies a friendly name for the federation trust.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -83,9 +80,6 @@ Accept wildcard characters: False
```
### -ApplicationUri
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ApplicationUri parameter specifies the primary domain used for the federated organization identifier.
If you specify the ApplicationUri parameter, you must use the SkipNamespaceProviderProvisioning switch and also specify the AdministratorProvisioningId and ApplicationIdentifier parameters.
@@ -94,6 +88,7 @@ If you specify the ApplicationUri parameter, you must use the SkipNamespaceProvi
Type: String
Parameter Sets: SkipNamespaceProviderProvisioning
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -103,9 +98,6 @@ Accept wildcard characters: False
```
### -SkipNamespaceProviderProvisioning
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SkipNamespaceProviderProvisioning switch specifies that the trust and federated organization identifier are provisioned externally without using federation functionality in Microsoft Exchange. You don't need to specify a value with this switch.
If you use this switch, you must specify the ApplicationIdentifier, ApplicationUri and AdministratorProvisioningId parameters.
@@ -114,6 +106,7 @@ If you use this switch, you must specify the ApplicationIdentifier, ApplicationU
Type: SwitchParameter
Parameter Sets: SkipNamespaceProviderProvisioning
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -123,15 +116,13 @@ Accept wildcard characters: False
```
### -Thumbprint
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Thumbprint parameter specifies the thumbprint of a certificate issued by a public certification authority (CA) trusted by the Microsoft Federation Gateway. For more details, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help).
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -141,9 +132,6 @@ Accept wildcard characters: False
```
### -AdministratorProvisioningId
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AdministratorProvisioningId parameter specifies the provisioning key returned by the Microsoft Federation Gateway when an organization has already registered a SiteID or ApplicationID.
If you specify the AdministratorProvisioningId parameter, you must use the SkipNamespaceProviderProvisioning switch and also specify the ApplicationIdentifier and ApplicationUri parameters.
@@ -152,6 +140,7 @@ If you specify the AdministratorProvisioningId parameter, you must use the SkipN
Type: String
Parameter Sets: SkipNamespaceProviderProvisioning
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -161,9 +150,6 @@ Accept wildcard characters: False
```
### -ApplicationIdentifier
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ApplicationIdentifier parameter specifies the SiteID or ApplicationID when an organization has already registered a SiteID or ApplicationID.
If you specify the ApplicationIdentifier parameter, you must use the SkipNamespaceProviderProvisioning switch and also specify the AdministratorProvisioningId and ApplicationUri parameters.
@@ -172,6 +158,7 @@ If you specify the ApplicationIdentifier parameter, you must use the SkipNamespa
Type: String
Parameter Sets: SkipNamespaceProviderProvisioning
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -181,9 +168,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -193,6 +177,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -202,15 +187,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -220,15 +203,13 @@ Accept wildcard characters: False
```
### -MetadataUrl
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The MetadataUrl parameter specifies the URL where WS-FederationMetadata is published by the Microsoft Federation Gateway.
```yaml
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -238,9 +219,6 @@ Accept wildcard characters: False
```
### -SuppressDnsWarning
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The SuppressDNSWarning switch specifies whether to display the DNS warning message for creating TXT records in your public DNS when running the New-FederationTrust cmdlet. You don't need to specify a value with this switch.
@@ -251,6 +229,7 @@ This switch is used automatically by the Hybrid Configuration wizard. We don't r
Type: SwitchParameter
Parameter Sets: FederationTrust
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -260,9 +239,6 @@ Accept wildcard characters: False
```
### -UseLegacyProvisioningService
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The UseLegacyProvisioningService switch specifies that the legacy interface on the Microsoft Federation Gateway is used for managing the federation trust, including federated domains, certificates, and federation metadata. You don't need to specify a value with this switch.
When using a self-signed certificate for configuring a federation trust with the Microsoft Federation Gateway, the trust needs to be created using this switch. After the federation trust is created, this behavior can't be changed and requires the deletion and re-creation of the federation trust.
@@ -271,6 +247,7 @@ When using a self-signed certificate for configuring a federation trust with the
Type: SwitchParameter
Parameter Sets: FederationTrust
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -280,15 +257,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyAuthority.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyAuthority.md
rename to exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md
index 08dece03d0..4d11d7b876 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyAuthority.md
+++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyAuthority.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-fileplanpropertyauthority
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertyauthority
+applicable: Security & Compliance
title: New-FilePlanPropertyAuthority
+schema: 2.0.0
---
# New-FilePlanPropertyAuthority
@@ -41,15 +39,13 @@ This example creates a new file plan property authority named Contoso Authority.
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the file plan property authority. The maximum length is 64 characters. If the value includes spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -59,9 +55,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -71,6 +64,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -80,15 +74,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCategory.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCategory.md
rename to exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md
index 4f7f68b402..acdefd1244 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCategory.md
+++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyCategory.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-fileplanpropertycategor
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertycategor
+applicable: Security & Compliance
title: New-FilePlanPropertyCategory
+schema: 2.0.0
---
# New-FilePlanPropertyCategory
@@ -41,15 +39,13 @@ This example creates a new file plan property category named Contoso Category.
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the file plan property category. The maximum length is 64 characters. If the value includes spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -59,9 +55,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -71,6 +64,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -80,15 +74,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCitation.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCitation.md
rename to exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md
index aa14c036c8..80625e0af9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyCitation.md
+++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyCitation.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-fileplanpropertycitation
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertycitation
+applicable: Security & Compliance
title: New-FilePlanPropertyCitation
+schema: 2.0.0
---
# New-FilePlanPropertyCitation
@@ -41,15 +39,13 @@ This example creates a new file plan property citation named Contoso-0001.
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the file plan property citation. The maximum length is 64 characters. If the value includes spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -59,15 +55,13 @@ Accept wildcard characters: False
```
### -CitationUrl
-
-> Applicable: Security & Compliance
-
The CitationJurisdiction parameter specifies the jurisdiction for the file plan property citation. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 1
@@ -77,15 +71,13 @@ Accept wildcard characters: False
```
### -CitationJurisdiction
-
-> Applicable: Security & Compliance
-
The CitationJurisdiction parameter specifies the URL for the file plan property citation.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: 2
@@ -95,9 +87,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -107,6 +96,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -116,15 +106,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyDepartment.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyDepartment.md
rename to exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md
index 99d970af33..8d084f8c09 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyDepartment.md
+++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyDepartment.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-fileplanpropertydepartment
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertydepartment
+applicable: Security & Compliance
title: New-FilePlanPropertyDepartment
+schema: 2.0.0
---
# New-FilePlanPropertyDepartment
@@ -41,15 +39,13 @@ This example creates a new file plan property department named Contoso HR.
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the file plan property department. The maximum length is 64 characters. If the value includes spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -59,9 +55,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -71,6 +64,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -80,15 +74,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyReferenceId.md
rename to exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md
index 81702c562c..f32d9f3ac4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertyReferenceId.md
+++ b/exchange/exchange-ps/exchange/New-FilePlanPropertyReferenceId.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-fileplanpropertyreferenceid
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertyreferenceid
+applicable: Security & Compliance
title: New-FilePlanPropertyReferenceId
+schema: 2.0.0
---
# New-FilePlanPropertyReferenceId
@@ -41,15 +39,13 @@ This example creates a new file plan property reference ID named Contoso-0001.
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the file plan property reference ID. The maximum length is 64 characters. If the value includes spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -59,9 +55,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -71,6 +64,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -80,15 +74,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertySubCategory.md b/exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertySubCategory.md
rename to exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md
index 2488a54aa6..ceff1b7f3e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FilePlanPropertySubCategory.md
+++ b/exchange/exchange-ps/exchange/New-FilePlanPropertySubCategory.md
@@ -1,11 +1,9 @@
---
-applicable: Security & Compliance
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-fileplanpropertysubcategory
-schema: 2.0.0
+online version: https://learn.microsoft.com/powershell/module/exchange/new-fileplanpropertysubcategory
+applicable: Security & Compliance
title: New-FilePlanPropertySubCategory
+schema: 2.0.0
---
# New-FilePlanPropertySubCategory
@@ -41,15 +39,13 @@ This example creates a new file plan property subcategory named US Tax that's a
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the file plan property subcategory. The maximum length is 64 characters. If the value includes spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -59,9 +55,6 @@ Accept wildcard characters: False
```
### -ParentId
-
-> Applicable: Security & Compliance
-
The ParentId parameter specifies parent file plan property category for this subcategory. You can use any value that uniquely identifies the parent category. For example:
- Name
@@ -72,6 +65,7 @@ The ParentId parameter specifies parent file plan property category for this sub
Type: ComplianceRuleIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -81,9 +75,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
@@ -93,6 +84,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -102,15 +94,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md b/exchange/exchange-ps/exchange/New-Fingerprint.md
similarity index 90%
rename from exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md
rename to exchange/exchange-ps/exchange/New-Fingerprint.md
index f72b4bc2e4..b2d1f80558 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md
+++ b/exchange/exchange-ps/exchange/New-Fingerprint.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-fingerprint
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-Fingerprint
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-fingerprint
-schema: 2.0.0
-title: New-Fingerprint
+ms.reviewer:
---
# New-Fingerprint
@@ -15,7 +14,7 @@ title: New-Fingerprint
## SYNOPSIS
This cmdlet is functional only in on-premises Exchange.
-**Note**: In Exchange Online, this cmdlet has been replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell.
+**Note**: In Exchange Online, this cmdlet has been replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchange/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell.
Use the New-Fingerprint cmdlet to create document fingerprints that are used with data classification rules. Because the results of New-Fingerprint are not stored outside of the data classification rule, you always run New-Fingerprint and New-DataClassification or Set-DataClassification in the same PowerShell session.
@@ -49,9 +48,6 @@ This example creates a new document fingerprint based on the file C:\\My Documen
## PARAMETERS
### -FileData
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FileData parameter specifies the file to use as a document fingerprint.
A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('\'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('\')`) and use the variable as the parameter value (`$data`).
@@ -60,6 +56,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded
Type: Byte[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: 1
@@ -69,15 +66,13 @@ Accept wildcard characters: False
```
### -Description
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Description parameter specifies a description for the document fingerprint.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -87,9 +82,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -99,6 +91,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -108,15 +101,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md b/exchange/exchange-ps/exchange/New-ForeignConnector.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md
rename to exchange/exchange-ps/exchange/New-ForeignConnector.md
index 38a27b3040..354a0c1d76 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md
+++ b/exchange/exchange-ps/exchange/New-ForeignConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RemoteConnections-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-foreignconnector
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-ForeignConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RemoteConnections-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-foreignconnector
-schema: 2.0.0
-title: New-ForeignConnector
+ms.reviewer:
---
# New-ForeignConnector
@@ -54,15 +53,13 @@ This example creates a Foreign connector with the following properties:
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Name parameter specifies the name for the Foreign connector.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: 1
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -AddressSpaces
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
- AddressSpaceType: The address space type may be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed.
@@ -94,6 +88,7 @@ You may specify multiple address spaces by separating the address spaces with co
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: True
Position: Named
@@ -103,9 +98,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -115,6 +107,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -124,9 +117,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data.
@@ -135,6 +125,7 @@ The DomainController parameter isn't supported on Edge Transport servers. An Edg
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -144,15 +135,13 @@ Accept wildcard characters: False
```
### -IsScopedConnector
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The IsScopedConnector parameter specifies the availability of the connector to other Mailbox servers. When the value of this parameter is $false, the connector can be used by all Mailbox servers in the Exchange organization. When the value of this parameter is $true, the connector can be used only by Mailbox servers in the same Active Directory site. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -162,9 +151,6 @@ Accept wildcard characters: False
```
### -SourceTransportServers
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SourceTransportServers parameter specifies the names of the Mailbox servers that use this Foreign connector. Having a single Foreign connector homed on multiple servers provides fault tolerance and high availability if one of the Mailbox servers fails. The default value of this parameter is the name of the server on which this Foreign connector is first installed.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -173,6 +159,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -182,15 +169,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md b/exchange/exchange-ps/exchange/New-GlobalAddressList.md
similarity index 89%
rename from exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md
rename to exchange/exchange-ps/exchange/New-GlobalAddressList.md
index a51e891a50..990ae4ba24 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md
+++ b/exchange/exchange-ps/exchange/New-GlobalAddressList.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-globaladdresslist
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-GlobalAddressList
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-globaladdresslist
-schema: 2.0.0
-title: New-GlobalAddressList
+ms.reviewer:
---
# New-GlobalAddressList
@@ -91,15 +90,13 @@ This example creates the GAL named GAL\_AgencyB by using the RecipientFilter par
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies a unique name for the global address list. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -109,9 +106,6 @@ Accept wildcard characters: False
```
### -IncludedRecipients
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
- AllRecipients: This value can be used only by itself.
@@ -129,6 +123,7 @@ You need to use this parameter when you use any Conditional parameters as part o
Type: WellKnownRecipientType
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -138,9 +133,6 @@ Accept wildcard characters: False
```
### -RecipientFilter
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
@@ -158,6 +150,7 @@ You can't use this parameter in combination with the IncludedRecipients paramete
Type: String
Parameter Sets: CustomFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -167,9 +160,6 @@ Accept wildcard characters: False
```
### -ConditionalCompany
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -180,6 +170,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -189,9 +180,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute1
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -202,6 +190,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -211,9 +200,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute10
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -224,6 +210,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -233,9 +220,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute11
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -246,6 +230,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -255,9 +240,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute12
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -268,6 +250,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -277,9 +260,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute13
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -290,6 +270,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -299,9 +280,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute14
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -312,6 +290,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -321,9 +300,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute15
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -334,6 +310,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -343,9 +320,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute2
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -356,6 +330,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -365,9 +340,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute3
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -378,6 +350,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -387,9 +360,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute4
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -400,6 +370,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -409,9 +380,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute5
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -422,6 +390,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -431,9 +400,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute6
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -444,6 +410,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -453,9 +420,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute7
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -466,6 +430,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -475,9 +440,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute8
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -488,6 +450,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -497,9 +460,6 @@ Accept wildcard characters: False
```
### -ConditionalCustomAttribute9
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -510,6 +470,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -519,9 +480,6 @@ Accept wildcard characters: False
```
### -ConditionalDepartment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -532,6 +490,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -541,9 +500,6 @@ Accept wildcard characters: False
```
### -ConditionalStateOrProvince
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
When you use multiple values for this parameter, the OR Boolean operator is applied. For more information about how Conditional parameters work, see the Detailed Description section of this topic.
@@ -554,6 +510,7 @@ You use this parameter in combination with the IncludedRecipients parameter as p
Type: MultiValuedProperty
Parameter Sets: PrecannedFilter
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -563,9 +520,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -575,6 +529,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -584,9 +539,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -595,6 +547,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -604,9 +557,6 @@ Accept wildcard characters: False
```
### -RecipientContainer
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The RecipientContainer parameter specifies a filter that's based on the recipient's location in Active Directory. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
@@ -622,6 +572,7 @@ If you don't use this parameter, the default value is the OU where the object wa
Type: OrganizationalUnitIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -631,15 +582,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md b/exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md
rename to exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md
index f791c26aab..68a8cdeb6a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md
+++ b/exchange/exchange-ps/exchange/New-HoldCompliancePolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-holdcompliancepolicy
applicable: Security & Compliance
+title: New-HoldCompliancePolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-holdcompliancepolicy
-schema: 2.0.0
-title: New-HoldCompliancePolicy
+ms.reviewer:
---
# New-HoldCompliancePolicy
@@ -53,15 +52,13 @@ This example creates a preservation policy named "Regulation 123 Compliance" for
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies the unique name of the preservation policy. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -71,15 +68,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -89,9 +84,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -101,6 +93,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -110,9 +103,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Security & Compliance
-
The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are:
- $true: The policy is enabled. This is the default value.
@@ -122,6 +112,7 @@ The Enabled parameter specifies whether the policy is enabled or disabled. Valid
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -131,9 +122,6 @@ Accept wildcard characters: False
```
### -ExchangeLocation
-
-> Applicable: Security & Compliance
-
The ExchangeLocation parameter specifies the mailboxes to include in the policy. Valid values are:
- A mailbox
@@ -154,6 +142,7 @@ If no mailboxes are specified, then no mailboxes are placed on hold.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -163,9 +152,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -174,6 +160,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -183,15 +170,13 @@ Accept wildcard characters: False
```
### -PublicFolderLocation
-
-> Applicable: Security & Compliance
-
The PublicFolderLocation parameter specifies that you want to include all public folders in the preservation policy. You use the value All for this parameter.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -201,9 +186,6 @@ Accept wildcard characters: False
```
### -SharePointLocation
-
-> Applicable: Security & Compliance
-
The SharePointLocation parameter specifies the SharePoint sites to include. You identify the site by its URL value, or you can use the value All to include all sites.
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -214,6 +196,7 @@ SharePoint sites can't be added to the policy until they have been indexed. If n
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -223,15 +206,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md b/exchange/exchange-ps/exchange/New-HoldComplianceRule.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md
rename to exchange/exchange-ps/exchange/New-HoldComplianceRule.md
index 59af4874f5..9ebebdb7c5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md
+++ b/exchange/exchange-ps/exchange/New-HoldComplianceRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-holdcompliancerule
applicable: Security & Compliance
+title: New-HoldComplianceRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-holdcompliancerule
-schema: 2.0.0
-title: New-HoldComplianceRule
+ms.reviewer:
---
# New-HoldComplianceRule
@@ -54,15 +53,13 @@ This example creates a new preservation rule named SeptOneYear and adds it to th
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the preservation rule. If the value contains spaces, enclose the value in quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 1
@@ -72,15 +69,13 @@ Accept wildcard characters: False
```
### -Policy
-
-> Applicable: Security & Compliance
-
The Policy parameter specifies the policy to contain the rule.
```yaml
Type: PolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -90,15 +85,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -108,9 +101,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -120,6 +110,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -129,9 +120,6 @@ Accept wildcard characters: False
```
### -ContentDateFrom
-
-> Applicable: Security & Compliance
-
The ContentDateFrom parameter specifies the start date of the date range for content to include.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -140,6 +128,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -149,9 +138,6 @@ Accept wildcard characters: False
```
### -ContentDateTo
-
-> Applicable: Security & Compliance
-
The ContentDateTo parameter specifies the end date of the date range for content to include.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -160,6 +146,7 @@ Use the short date format that's defined in the Regional Options settings on the
Type: DateTime
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -169,9 +156,6 @@ Accept wildcard characters: False
```
### -ContentMatchQuery
-
-> Applicable: Security & Compliance
-
The ContentMatchQuery parameter specifies a content search filter.
This parameter uses a text search string or a query that's formatted by using the Keyword Query Language (KQL). For more information, see [Keyword Query Language (KQL) syntax reference](https://learn.microsoft.com/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference) and [Keyword queries and search conditions for eDiscovery](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions).
@@ -180,6 +164,7 @@ This parameter uses a text search string or a query that's formatted by using th
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -189,15 +174,13 @@ Accept wildcard characters: False
```
### -Disabled
-
-> Applicable: Security & Compliance
-
The Disabled parameter specifies whether the preservation rule is enabled or disabled. Valid input for this parameter is $true or $false. The default value is $false.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -207,9 +190,6 @@ Accept wildcard characters: False
```
### -HoldContent
-
-> Applicable: Security & Compliance
-
The HoldContent parameter specifies the hold duration for the preservation rule. Valid values are:
- An integer: The hold duration in days.
@@ -219,6 +199,7 @@ The HoldContent parameter specifies the hold duration for the preservation rule.
Type: Unlimited
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -228,9 +209,6 @@ Accept wildcard characters: False
```
### -HoldDurationDisplayHint
-
-> Applicable: Security & Compliance
-
The HoldDurationDisplayHint parameter specifies the units that are used to display the preservation duration in the Microsoft Purview compliance portal. Valid values are:
- Days
@@ -243,6 +221,7 @@ For example, if this parameter is set to the value Years, and the HoldContent pa
Type: HoldDurationHint
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -252,15 +231,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md b/exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md
rename to exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md
index 8bb8f78675..c11691fd96 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md
+++ b/exchange/exchange-ps/exchange/New-HostedContentFilterPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-hostedcontentfilterpolicy
applicable: Exchange Online, Exchange Online Protection
+title: New-HostedContentFilterPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-hostedcontentfilterpolicy
-schema: 2.0.0
-title: New-HostedContentFilterPolicy
+ms.reviewer:
---
# New-HostedContentFilterPolicy
@@ -103,9 +102,6 @@ This example creates a spam filter policy named Contoso Executives with the foll
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Name parameter specifies a unique name for the spam filter policy. If the value contains spaces, enclose the value in quotation marks (").
Don't use the following characters in the name value: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`.
@@ -114,6 +110,7 @@ Don't use the following characters in the name value: `\ % & * + / = ? { } | < >
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -123,9 +120,6 @@ Accept wildcard characters: False
```
### -AddXHeaderValue
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AddXHeaderValue parameter specifies the X-header name (not value) to add to spam messages when a spam filtering verdict parameter is set to the value AddXHeader. The following spam filtering verdict parameters can use the AddXHeader action:
- BulkSpamAction
@@ -145,6 +139,7 @@ Note that this setting is independent of the AddXHeader value of the TestModeAct
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -154,15 +149,13 @@ Accept wildcard characters: False
```
### -AdminDisplayName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AdminDisplayName parameter specifies a description for the policy. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -172,9 +165,6 @@ Accept wildcard characters: False
```
### -AllowedSenderDomains
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AllowedSenderDomains parameter specifies trusted domains that aren't processed by the spam filter. Messages from senders in these domains are stamped with `SFV:SKA` in the `X-Forefront-Antispam-Report header` and receive a spam confidence level (SCL) of -1, so the messages are delivered to the recipient's inbox. Valid values are one or more SMTP domains.
**Caution**: Think very carefully before you add domains here. For more information, see [Create safe sender lists in EOP](https://learn.microsoft.com/defender-office-365/create-safe-sender-lists-in-office-365).
@@ -187,6 +177,7 @@ To add or remove one or more values without affecting any existing entries, use
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -196,9 +187,6 @@ Accept wildcard characters: False
```
### -AllowedSenders
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AllowedSenders parameter specifies a list of trusted senders that skip spam filtering. Messages from these senders are stamped with SFV:SKA in the X-Forefront-Antispam-Report header and receive an SCL of -1, so the messages are delivered to the recipient's inbox. Valid values are one or more SMTP email addresses.
**Caution**: Think very carefully before you add senders here. For more information, see [Create safe sender lists in EOP](https://learn.microsoft.com/defender-office-365/create-safe-sender-lists-in-office-365).
@@ -211,6 +199,7 @@ To add or remove one or more values without affecting any existing entries, use
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -220,9 +209,6 @@ Accept wildcard characters: False
```
### -BlockedSenderDomains
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The BlockedSenderDomains parameter specifies domains that are always marked as spam sources. Messages from senders in these domains are stamped with `SFV:SKB` value in the `X-Forefront-Antispam-Report` header and receive an SCL of 6 (spam). Valid values are one or more SMTP domains.
**Note**: Manually blocking domains isn't dangerous, but it can increase your administrative workload. For more information, see [Create block sender lists in EOP](https://learn.microsoft.com/defender-office-365/create-block-sender-lists-in-office-365).
@@ -235,6 +221,7 @@ To add or remove one or more values without affecting any existing entries, use
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -244,9 +231,6 @@ Accept wildcard characters: False
```
### -BlockedSenders
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The BlockedSenders parameter specifies senders that are always marked as spam sources. Messages from these senders are stamped with `SFV:SKB` in the `X-Forefront-Antispam-Report` header and receive an SCL of 6 (spam). Valid values are one or more SMTP email addresses.
**Note**: Manually blocking senders isn't dangerous, but it can increase your administrative workload. For more information, see [Create block sender lists in EOP](https://learn.microsoft.com/defender-office-365/create-block-sender-lists-in-office-365).
@@ -259,6 +243,7 @@ To add or remove one or more values without affecting any existing entries, use
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -268,9 +253,6 @@ Accept wildcard characters: False
```
### -BulkQuarantineTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The BulkQuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as bulk email (the BulkSpamAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
- Name
@@ -287,6 +269,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -296,9 +279,6 @@ Accept wildcard characters: False
```
### -BulkSpamAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The BulkSpamAction parameter specifies the action to take on messages that are marked as bulk email (also known as gray mail) based on the bulk complaint level (BCL) of the message, and the BCL threshold you configure in the BulkThreshold parameter. Valid values are:
- AddXHeader: Add the AddXHeaderValue parameter value to the message header and deliver the message.
@@ -313,6 +293,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m
Type: SpamFilteringAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -322,9 +303,6 @@ Accept wildcard characters: False
```
### -BulkThreshold
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages will trigger the action that's specified by the BulkSpamAction parameter.
A higher BCL indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk complaint level (BCL) in EOP](https://learn.microsoft.com/defender-office-365/anti-spam-bulk-complaint-level-bcl-about).
@@ -333,6 +311,7 @@ A higher BCL indicates the message is more likely to generate complaints (and is
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -342,9 +321,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -354,6 +330,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -363,15 +340,13 @@ Accept wildcard characters: False
```
### -DownloadLink
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -381,15 +356,13 @@ Accept wildcard characters: False
```
### -EnableEndUserSpamNotifications
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -399,9 +372,6 @@ Accept wildcard characters: False
```
### -EnableLanguageBlockList
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EnableLanguageBlockList parameter enables or disables marking messages that were written in specific languages as spam. Valid values are:
- $true: Mark messages hat were written in the languages specified by the LanguageBlockList parameter as spam.
@@ -411,6 +381,7 @@ The EnableLanguageBlockList parameter enables or disables marking messages that
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -420,9 +391,6 @@ Accept wildcard characters: False
```
### -EnableRegionBlockList
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EnableRegionBlockList parameter enables or disables marking messages that are sent from specific countries or regions as spam. Valid values are:
- $true: Mark messages from senders in the RegionBlockList parameter as spam.
@@ -432,6 +400,7 @@ The EnableRegionBlockList parameter enables or disables marking messages that ar
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -441,15 +410,13 @@ Accept wildcard characters: False
```
### -EndUserSpamNotificationCustomFromAddress
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
```yaml
Type: SmtpAddress
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -459,15 +426,13 @@ Accept wildcard characters: False
```
### -EndUserSpamNotificationCustomFromName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -477,15 +442,13 @@ Accept wildcard characters: False
```
### -EndUserSpamNotificationCustomSubject
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -495,15 +458,13 @@ Accept wildcard characters: False
```
### -EndUserSpamNotificationFrequency
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -513,15 +474,13 @@ Accept wildcard characters: False
```
### -EndUserSpamNotificationLanguage
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
```yaml
Type: EsnLanguage
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -531,15 +490,13 @@ Accept wildcard characters: False
```
### -EndUserSpamNotificationLimit
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
```yaml
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -549,9 +506,6 @@ Accept wildcard characters: False
```
### -HighConfidencePhishAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HighConfidencePhishAction parameter specifies the action to take on messages that are marked as high confidence phishing (not phishing). Phishing messages use fraudulent links or spoofed domains to get personal information. Valid values are:
- Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
@@ -561,6 +515,7 @@ The HighConfidencePhishAction parameter specifies the action to take on messages
Type: PhishFilteringAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -570,9 +525,6 @@ Accept wildcard characters: False
```
### -HighConfidencePhishQuarantineTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HighConfidencePhishQuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as high confidence phishing (the HighConfidencePhishAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
- Name
@@ -589,6 +541,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -598,9 +551,6 @@ Accept wildcard characters: False
```
### -HighConfidenceSpamAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HighConfidenceSpamAction parameter specifies the action to take on messages that are marked as high confidence spam (not spam, bulk email, phishing, or high confidence phishing). Valid values are:
- AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
@@ -614,6 +564,7 @@ The HighConfidenceSpamAction parameter specifies the action to take on messages
Type: SpamFilteringAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -623,9 +574,6 @@ Accept wildcard characters: False
```
### -HighConfidenceSpamQuarantineTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HighConfidenceSpamQuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as high confidence spam (the HighConfidenceSpamAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
- Name
@@ -642,6 +590,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -651,9 +600,6 @@ Accept wildcard characters: False
```
### -IncreaseScoreWithBizOrInfoUrls
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncreaseScoreWithBizOrInfoUrls parameter increases the spam score of messages that contain links to .biz or .info domains. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -664,6 +610,7 @@ The IncreaseScoreWithBizOrInfoUrls parameter increases the spam score of message
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -673,9 +620,6 @@ Accept wildcard characters: False
```
### -IncreaseScoreWithImageLinks
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncreaseScoreWithImageLinks parameter increases the spam score of messages that contain image links to remote websites. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -686,6 +630,7 @@ The IncreaseScoreWithImageLinks parameter increases the spam score of messages t
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -695,9 +640,6 @@ Accept wildcard characters: False
```
### -IncreaseScoreWithNumericIps
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncreaseScoreWithNumericIps parameter increases the spam score of messages that contain links to IP addresses. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -708,6 +650,7 @@ The IncreaseScoreWithNumericIps parameter increases the spam score of messages t
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -717,9 +660,6 @@ Accept wildcard characters: False
```
### -IncreaseScoreWithRedirectToOtherPort
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IncreaseScoreWithRedirectToOtherPort parameter increases the spam score of messages that contain links that redirect to TCP ports other than 80 (HTTP), 8080 (alternate HTTP), or 443 (HTTPS). Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -730,6 +670,7 @@ The IncreaseScoreWithRedirectToOtherPort parameter increases the spam score of m
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -739,9 +680,6 @@ Accept wildcard characters: False
```
### -InlineSafetyTipsEnabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The InlineSafetyTipsEnabled parameter specifies whether to enable or disable safety tips that are shown to recipients in messages. Valid values are:
- $true: Safety tips are enabled. This is the default value.
@@ -751,6 +689,7 @@ The InlineSafetyTipsEnabled parameter specifies whether to enable or disable saf
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -760,9 +699,6 @@ Accept wildcard characters: False
```
### -IntraOrgFilterState
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The IntraOrgFilterState parameter specifies whether to enable anti-spam filtering for messages sent between internal users (users in the same organization). The action that's configured in the policy for the specified spam filter verdicts is taken on messages sent between internal users. Valid values are:
- Default: This is the default value. Currently, this value is the same as HighConfidencePhish.
@@ -776,6 +712,7 @@ The IntraOrgFilterState parameter specifies whether to enable anti-spam filterin
Type: IntraOrgFilterState
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -785,9 +722,6 @@ Accept wildcard characters: False
```
### -LanguageBlockList
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The LanguageBlockList parameter specifies the email content languages that are marked as spam when the EnableLanguageBlockList parameter value is $true. A valid value is a supported uppercase ISO 639-1 two-letter language code:
AF, AR, AZ, BE, BG, BN, BR, BS, CA, CS, CY, DA, DE, EL, EN, EO, ES, ET, EU, FA, FI, FO, FR, FY, GA, GL, GU, HA, HE, HI, HR, HU, HY, ID, IS, IT, JA, KA, KK, KL, KN, KO, KU, KY, LA, LB, LT, LV, MI, MK, ML, MN, MR, MS, MT, NB, NL, NN, PA, PL, PS, PT, RM, RO, RU, SE, SK, SL, SQ, SR, SV, SW, TA, TE, TH, TL, TR, UK, UR, UZ, VI, WEN, YI, ZH-CN, ZH-TW, and ZU.
@@ -800,6 +734,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -809,9 +744,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamBulkMail
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamBulkMail parameter allows spam filtering to act on bulk email messages. Valid values are:
- Off: The message is stamped with the BCL, but no action is taken for a bulk email filtering verdict. In effect, the values of the BulkThreshold and BulkSpamAction parameters are irrelevant.
@@ -822,6 +754,7 @@ The MarkAsSpamBulkMail parameter allows spam filtering to act on bulk email mess
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -831,9 +764,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamEmbedTagsInHtml
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -844,6 +774,7 @@ The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -853,9 +784,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamEmptyMessages
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamEmptyMessages parameter marks a message as spam when the message contains no subject, no content in the message body, and no attachments. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -866,6 +794,7 @@ The MarkAsSpamEmptyMessages parameter marks a message as spam when the message c
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -875,9 +804,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamFormTagsInHtml
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -888,6 +814,7 @@ The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -897,9 +824,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamFramesInHtml
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamFramesInHtml parameter marks a message as spam when the message contains HTML \ or \ tags. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -910,6 +834,7 @@ The MarkAsSpamFramesInHtml parameter marks a message as spam when the message co
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -919,9 +844,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamFromAddressAuthFail
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamFromAddressAuthFail parameter marks a message as spam when Sender ID filtering encounters a hard fail. This setting combines an Sender Policy Framework (SPF) check with a Sender ID check to help protect against message headers that contain forged senders. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -931,6 +853,7 @@ The MarkAsSpamFromAddressAuthFail parameter marks a message as spam when Sender
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -940,9 +863,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamJavaScriptInHtml
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamJavaScriptInHtml parameter marks a message as spam when the message contains JavaScript or VBScript. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -953,6 +873,7 @@ The MarkAsSpamJavaScriptInHtml parameter marks a message as spam when the messag
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -962,9 +883,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamNdrBackscatter
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamNdrBackscatter parameter marks a message as spam when the message is a non-delivery report (also known as an NDR or bounce messages) sent to a forged sender (known as *backscatter*). Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -974,6 +892,7 @@ The MarkAsSpamNdrBackscatter parameter marks a message as spam when the message
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -983,9 +902,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamObjectTagsInHtml
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the message contains HTML \ tags. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -996,6 +912,7 @@ The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the messag
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1005,9 +922,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamSensitiveWordList
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamSensitiveWordList parameter marks a message as spam when the message contains words from the sensitive words list. Microsoft maintains a dynamic but non-editable list of words that are associated with potentially offensive messages. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -1018,6 +932,7 @@ The MarkAsSpamSensitiveWordList parameter marks a message as spam when the messa
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1027,9 +942,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamSpfRecordHardFail
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamSpfRecordHardFail parameter marks a message as spam when SPF record checking encounters a hard fail. Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -1039,6 +951,7 @@ The MarkAsSpamSpfRecordHardFail parameter marks a message as spam when SPF recor
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1048,9 +961,6 @@ Accept wildcard characters: False
```
### -MarkAsSpamWebBugsInHtml
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The MarkAsSpamWebBugsInHtml parameter marks a message as spam when the message contains web bugs (also known as web beacons). Valid values are:
- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
@@ -1061,6 +971,7 @@ The MarkAsSpamWebBugsInHtml parameter marks a message as spam when the message c
Type: SpamFilteringOption
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1070,9 +981,6 @@ Accept wildcard characters: False
```
### -ModifySubjectValue
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ModifySubjectValue parameter specifies the text to prepend to the existing subject of messages when a spam filtering verdict parameter is set to the value ModifySubject. The following spam filtering verdict parameters can use the ModifySubject action:
- BulkSpamAction
@@ -1086,6 +994,7 @@ If the value contains spaces, enclose the value in quotation marks (").
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1095,9 +1004,6 @@ Accept wildcard characters: False
```
### -PhishQuarantineTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PhishQuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as phishing (the PhishSpamAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
- Name
@@ -1114,6 +1020,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1123,9 +1030,6 @@ Accept wildcard characters: False
```
### -PhishSpamAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PhishSpamAction parameter specifies the action to take on messages that are marked as phishing (not high confidence phishing). Phishing messages use fraudulent links or spoofed domains to get personal information. Valid values are:
- AddXHeader: Add the AddXHeaderValue parameter value to the message header and deliver the message.
@@ -1140,6 +1044,7 @@ The PhishSpamAction parameter specifies the action to take on messages that are
Type: SpamFilteringAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1149,9 +1054,6 @@ Accept wildcard characters: False
```
### -PhishZapEnabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The PhishZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect phishing in already delivered messages in Exchange Online mailboxes. Valid values are:
- $true: ZAP for phishing messages is enabled. This is the default value. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
@@ -1163,6 +1065,7 @@ You configure ZAP for spam with the SpamZapEnabled parameter.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1172,9 +1075,6 @@ Accept wildcard characters: False
```
### -QuarantineRetentionPeriod
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The QuarantineRetentionPeriod parameter specifies the number of days that spam messages remain in quarantine when a spam filtering verdict parameter is set to the value Quarantine. All spam filtering verdict parameters can use the Quarantine action:
- BulkSpamAction
@@ -1191,6 +1091,7 @@ After the time period expires, the message is deleted.
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1200,15 +1101,13 @@ Accept wildcard characters: False
```
### -RecommendedPolicyType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecommendedPolicyType parameter is used for Standard and Strict policy creation as part of [Preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies). Don't use this parameter yourself.
```yaml
Type: RecommendedPolicyType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1218,9 +1117,6 @@ Accept wildcard characters: False
```
### -RedirectToRecipients
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RedirectToRecipients parameter specifies the email addresses of replacement recipients when a spam filtering verdict parameter is set to the value Redirect. The following spam filtering verdict parameters can use the Redirect action:
- BulkSpamAction
@@ -1234,6 +1130,7 @@ You can specify multiple email addresses separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1243,9 +1140,6 @@ Accept wildcard characters: False
```
### -RegionBlockList
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RegionBlockList parameter specifies the source countries or regions that are marked as spam when the EnableRegionBlockList parameter value is $true. A valid value is a supported ISO 3166-1 two-letter country code:
AD, AE, AF, AG, AI, AL, AM, AO, AQ, AR, AS, AT, AU, AW, AX, AZ, BA, BB, BD, BE, BF, BG, BH, BI, BJ, BL, BM, BN, BO, BQ, BR, BS, BT, BV, BW, BY, BZ, CA, CC, CD, CF, CG, CH, CI, CK, CL, CM, CN, CO, CR, CU, CV, CW, CX, CY, CZ, DE, DJ, DK, DM, DO, DZ, EC, EE, EG, ER, ES, ET, FI, FJ, FK, FM, FO, FR, GA, GB, GD, GE, GF, GG, GH, GI, GL, GM, GN, GP, GQ, GR, GS, GT, GU, GW, GY, HK, HM, HN, HR, HT, HU, ID, IE, IL, IM, IN, IO, IQ, IR, IS, IT, JE, JM, JO, JP, KE, KG, KH, KI, KM, KN, KP, KR, KW, KY, KZ, LA, LB, LC, LI, LK, LR, LS, LT, LU, LV, LY, MA, MC, MD, ME, MF, MG, MH, MK, ML, MM, MN, MO, MP, MQ, MR, MS, MT, MU, MV, MW, MX, MY, MZ, NA, NC, NE, NF, NG, NI, NL, NO, NP, NR, NU, NZ, OM, PA, PE, PF, PG, PH, PK, PL, PM, PN, PR, PS, PT, PW, PY, QA, RE, RO, RS, RU, RW, SA, SB, SC, SD, SE, SG, SH, SI, SJ, SK, SL, SM, SN, SO, SR, ST, SV, SX, SY, SZ, TC, TD, TF, TG, TH, TJ, TK, TL, TM, TN, TO, TR, TT, TV, TW, TZ, UA, UG, UM, US, UY, UZ, VA, VC, VE, VG, VI, VN, VU, WF, WS, XE, XJ, XS, YE, YT, ZA, ZM, and ZW.
@@ -1262,6 +1156,7 @@ To empty the list, use the value $null.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1271,9 +1166,6 @@ Accept wildcard characters: False
```
### -SpamAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SpamAction parameter specifies the action to take on messages that are marked as spam (not high confidence spam, bulk email, phishing, or high confidence phishing). Valid values are:
- AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
@@ -1287,6 +1179,7 @@ The SpamAction parameter specifies the action to take on messages that are marke
Type: SpamFilteringAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1296,9 +1189,6 @@ Accept wildcard characters: False
```
### -SpamQuarantineTag
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SpamQuarantineTag parameter specifies the quarantine policy that's used on messages that are quarantined as spam (the SpamAction parameter value is Quarantine). You can use any value that uniquely identifies the quarantine policy. For example:
- Name
@@ -1315,6 +1205,7 @@ To view the list of available quarantine policies, run the following command: `G
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1324,9 +1215,6 @@ Accept wildcard characters: False
```
### -SpamZapEnabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SpamZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect spam in already delivered messages in Exchange Online mailboxes. Valid values are:
- $true: ZAP for spam is enabled. This is the default value. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
@@ -1338,6 +1226,7 @@ You configure ZAP for phishing messages with the PhishZapEnabled parameter.
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1347,9 +1236,6 @@ Accept wildcard characters: False
```
### -TestModeAction
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The TestModeAction parameter specifies the additional action to take on messages when one or more IncreaseScoreWith\* or MarkAsSpam\* ASF parameters are set to the value Test. Valid values are:
- None: This is the default value, and we recommend that you don't change it.
@@ -1360,6 +1246,7 @@ The TestModeAction parameter specifies the additional action to take on messages
Type: SpamFilteringTestModeAction
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1370,8 +1257,6 @@ Accept wildcard characters: False
### -TestModeBccToRecipients
-> Applicable: Exchange Online, Exchange Online Protection
-
The TestModeBccToRecipients parameter specifies the blind carbon copy (Bcc) recipients to add to spam messages when the TestModeAction ASF parameter is set to the value BccMessage.
Valid input for this parameter is an email address. Separate multiple email addresses with commas.
@@ -1382,6 +1267,7 @@ This parameter is meaningful only when the value of the TestModeAction parameter
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -1391,15 +1277,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md b/exchange/exchange-ps/exchange/New-HostedContentFilterRule.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md
rename to exchange/exchange-ps/exchange/New-HostedContentFilterRule.md
index 7dc54be6f6..427202c583 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/exchange/New-HostedContentFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-hostedcontentfilterrule
applicable: Exchange Online, Exchange Online Protection
+title: New-HostedContentFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-hostedcontentfilterrule
-schema: 2.0.0
-title: New-HostedContentFilterRule
+ms.reviewer:
---
# New-HostedContentFilterRule
@@ -55,9 +54,6 @@ This example creates a new spam filter rule named Contoso Recipients with the fo
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Name parameter specifies a unique name for the spam filter rule. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
Don't use the following characters in the name value: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`.
@@ -66,6 +62,7 @@ Don't use the following characters in the name value: `\ % & * + / = ? { } | < >
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -HostedContentFilterPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HostedContentFilterPolicy parameter specifies the spam filter policy (content filter policy) that's associated with the rule.
You can use any value that uniquely identifies the policy. For example:
@@ -92,6 +86,7 @@ You can't specify the default spam filter policy, and you can't specify a spam f
Type: HostedContentFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -101,15 +96,13 @@ Accept wildcard characters: False
```
### -Comments
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Comments parameter specifies informative comments for the rule, such as what the rule is used for or how it has changed over time. The length of the comment can't exceed 1024 characters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -119,9 +112,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -131,6 +121,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -140,15 +131,13 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Enabled parameter enables or disables the rule. Valid input for this parameter is $true or $false. The default value is $true.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -158,15 +147,13 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientDomainIs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfRecipientDomainIs parameter specifies an exception for the rule that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -176,9 +163,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentTo
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfSentTo parameter specifies an exception for the rule that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -194,6 +178,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -203,9 +188,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentToMemberOf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfSentToMemberOf parameter specifies an exception for the rule that looks for messages sent to members of distribution groups, mail-enabled security groups, or sent to Microsoft 365 Groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -223,6 +205,7 @@ If you remove the group after you create the rule, no exception is made for mess
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -232,9 +215,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules:
@@ -249,6 +229,7 @@ If you modify the priority value of a rule, the position of the rule in the list
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -258,15 +239,13 @@ Accept wildcard characters: False
```
### -RecipientDomainIs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientDomainIs parameter specifies a condition for the rule that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -276,9 +255,6 @@ Accept wildcard characters: False
```
### -SentTo
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SentTo parameter specifies a condition for the rule that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -294,6 +270,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -303,9 +280,6 @@ Accept wildcard characters: False
```
### -SentToMemberOf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SentToMemberOf parameter specifies a condition that looks for messages sent to members of distribution groups, mail-enabled security groups, or sent to Microsoft 365 Groups. You can use any value that uniquely identifies the group. For example:
- Name
@@ -323,6 +297,7 @@ If you remove the group after you create the rule, no action is taken on message
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -332,15 +307,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md
similarity index 93%
rename from exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md
rename to exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md
index d838d30f5b..6f78d93176 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md
+++ b/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-hostedoutboundspamfilterpolicy
applicable: Exchange Online, Exchange Online Protection
+title: New-HostedOutboundSpamFilterPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-hostedoutboundspamfilterpolicy
-schema: 2.0.0
-title: New-HostedOutboundSpamFilterPolicy
+ms.reviewer:
---
# New-HostedOutboundSpamFilterPolicy
@@ -57,15 +56,13 @@ This example creates a new outbound spam filter policy named Contoso Executives
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Name parameter specifies a unique name for the outbound spam filter policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -75,9 +72,6 @@ Accept wildcard characters: False
```
### -ActionWhenThresholdReached
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ActionWhenThresholdReach parameter specifies the action to take when any of the limits specified in the policy are reached. Valid values are:
- Alert: No action, alert only.
@@ -89,6 +83,7 @@ Type: OutboundRecipientLimitsExceededAction
Parameter Sets: (All)
Aliases:
Accepted values: Alert, BlockUserForToday, BlockUser
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -AdminDisplayName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AdminDisplayName parameter specifies a description for the policy. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -AutoForwardingMode
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AutoForwardingMode specifies how the policy controls automatic email forwarding to external recipients. Valid values are:
- Automatic: This is the default value. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888).
@@ -132,6 +122,7 @@ Type: AutoForwardingMode
Parameter Sets: (All)
Aliases:
Accepted values: Automatic, Off, On
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -141,9 +132,6 @@ Accept wildcard characters: False
```
### -BccSuspiciousOutboundAdditionalRecipients
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The BccSuspiciousOutboundAdditionalRecipients parameter specifies an email address to add to the Bcc field of outgoing spam messages. You can specify multiple email addresses separated by commas.
The specified recipients are added to the Bcc field of outgoing spam messages when the value of the BccSuspiciousOutboundMail parameter is $true.
@@ -152,6 +140,7 @@ The specified recipients are added to the Bcc field of outgoing spam messages wh
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -161,9 +150,6 @@ Accept wildcard characters: False
```
### -BccSuspiciousOutboundMail
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The BccSuspiciousOutboundMail parameter specifies whether to add recipients to the Bcc field of outgoing spam messages. Valid values are:
- $true: The recipients specified by the BccSuspiciousOutboundAdditionalRecipients parameter are added to outgoing spam messages.
@@ -173,6 +159,7 @@ The BccSuspiciousOutboundMail parameter specifies whether to add recipients to t
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -182,9 +169,6 @@ Accept wildcard characters: False
```
### -NotifyOutboundSpam
-
-> Applicable: Exchange Online, Exchange Online Protection
-
**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
The NotifyOutboundSpam parameter specify whether to notify admins when outgoing spam is detected. Valid values are:
@@ -196,6 +180,7 @@ The NotifyOutboundSpam parameter specify whether to notify admins when outgoing
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -205,9 +190,6 @@ Accept wildcard characters: False
```
### -NotifyOutboundSpamRecipients
-
-> Applicable: Exchange Online, Exchange Online Protection
-
**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
The NotifyOutboundSpamRecipients parameter specifies the email addresses of admins to notify when an outgoing spam is detected. You can specify multiple email addresses separated by commas.
@@ -218,6 +200,7 @@ The specified recipients receive notifications when the value of the NotifyOutbo
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -227,15 +210,13 @@ Accept wildcard characters: False
```
### -RecipientLimitExternalPerHour
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientLimitExternalPerHour parameter specifies the maximum number of external recipients that a user can send to within an hour. A valid value is 0 to 10000. The default value is 0, which means the service defaults are used. For more information, see [Sending limits across Microsoft 365 options](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
```yaml
Type: UInt32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -245,15 +226,13 @@ Accept wildcard characters: False
```
### -RecipientLimitInternalPerHour
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientLimitInternalPerHour parameter specifies the maximum number of internal recipients that a user can send to within an hour. A valid value is 0 to 10000. The default value is 0, which means the service defaults are used. For more information, see [Sending limits across Microsoft 365 options](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-across-office-365-options).
```yaml
Type: UInt32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -263,15 +242,13 @@ Accept wildcard characters: False
```
### -RecipientLimitPerDay
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecipientLimitInternalPerHour parameter specifies the maximum number of recipients that a user can send to within a day. A valid value is 0 to 10000. The default value is 0, which means the service defaults are used. For more information, see [Sending limits across Microsoft 365 options](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-across-office-365-options).
```yaml
Type: UInt32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -281,15 +258,13 @@ Accept wildcard characters: False
```
### -RecommendedPolicyType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RecommendedPolicyType parameter is used for Standard and Strict policy creation as part of [Preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies). Don't use this parameter yourself.
```yaml
Type: RecommendedPolicyType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md
rename to exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md
index 1afdd51735..721a9bd38a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-hostedoutboundspamfilterrule
applicable: Exchange Online, Exchange Online Protection
+title: New-HostedOutboundSpamFilterRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-hostedoutboundspamfilterrule
-schema: 2.0.0
-title: New-HostedOutboundSpamFilterRule
+ms.reviewer:
---
# New-HostedOutboundSpamFilterRule
@@ -52,9 +51,6 @@ This example creates a new outbound spam filter rule named Contoso Executives th
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Name parameter specifies a unique name for the outbound spam filter rule. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
Don't use the following characters: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`.
@@ -63,6 +59,7 @@ Don't use the following characters: `\ % & * + / = ? { } | < > ( ) ; : [ ] , "`.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 0
@@ -72,9 +69,6 @@ Accept wildcard characters: False
```
### -HostedOutboundSpamFilterPolicy
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The HostedOutboundSpamFilterPolicy parameter specifies the outbound spam filter policy that's associated with the outbound spam filter rule.
You can use any value that uniquely identifies the policy. For example:
@@ -89,6 +83,7 @@ You can't specify the default outbound spam filter policy, and you can't specify
Type: HostedOutboundSpamFilterPolicyIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -98,15 +93,13 @@ Accept wildcard characters: False
```
### -Comments
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Comments parameter specifies informative comments for the rule, such as what the rule is used for or how it has changed over time. The length of the comment can't exceed 1024 characters.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -116,9 +109,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -128,6 +118,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -137,9 +128,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Enabled parameter specifies whether the rule is enabled. Valid values are:
- $true: The rule is enabled. This is the default value.
@@ -151,6 +139,7 @@ In the properties of the rule, the value of this parameter is visible in the Sta
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -160,9 +149,6 @@ Accept wildcard characters: False
```
### -ExceptIfFrom
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfFrom parameter specifies an exception that looks for messages from specific senders. You can use any value that uniquely identifies the sender. For example:
- Name
@@ -178,6 +164,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -187,9 +174,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromMemberOf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfFromMemberOf parameter specifies an exception that looks for messages sent by group members. You can use any value that uniquely identifies the group. For example:
- Name
@@ -205,6 +189,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -214,15 +199,13 @@ Accept wildcard characters: False
```
### -ExceptIfSenderDomainIs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ExceptIfSenderDomainIs parameter specifies an exception that looks for senders with email address in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -232,9 +215,6 @@ Accept wildcard characters: False
```
### -From
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The From parameter specifies a condition that looks for messages from specific senders. You can use any value that uniquely identifies the sender. For example:
- Name
@@ -250,6 +230,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -259,9 +240,6 @@ Accept wildcard characters: False
```
### -FromMemberOf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The FromMemberOf parameter specifies a condition that looks for messages sent by group members. You can use any value that uniquely identifies the group. For example:
- Name
@@ -277,6 +255,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -286,9 +265,6 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules:
@@ -303,6 +279,7 @@ If you modify the priority value of a rule, the position of the rule in the list
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -312,15 +289,13 @@ Accept wildcard characters: False
```
### -SenderDomainIs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SenderDomainIs parameter specifies a condition that looks for senders with email address in the specified domains. You can specify multiple domains separated by commas.
```yaml
Type: Word[]
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -330,15 +305,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md b/exchange/exchange-ps/exchange/New-HybridConfiguration.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md
rename to exchange/exchange-ps/exchange/New-HybridConfiguration.md
index eeb2dd5b03..a345872239 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md
+++ b/exchange/exchange-ps/exchange/New-HybridConfiguration.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-hybridconfiguration
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+title: New-HybridConfiguration
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-hybridconfiguration
-schema: 2.0.0
-title: New-HybridConfiguration
+ms.reviewer:
---
# New-HybridConfiguration
@@ -65,9 +64,6 @@ This example creates the hybrid configuration named Hybrid Configuration with th
## PARAMETERS
### -ClientAccessServers
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The ClientAccessServers parameter specifies the Hub Transport servers in Exchange Server 2010 SP2 or later that are configured to support hybrid deployment features. You need to specify at least one Client Access server that's accessible from the internet on TCP ports 80 and 443. The servers are configured to enable the following features:
@@ -82,6 +78,7 @@ You can specify multiple servers separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -91,9 +88,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -103,6 +97,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -112,15 +107,13 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
```yaml
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -130,9 +123,6 @@ Accept wildcard characters: False
```
### -Domains
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Domains parameter specifies the domain namespaces used in the hybrid deployment. These domains must be configured as accepted domains in either on-premises Exchange or Exchange Online. The domains are used in configuring the organization relationships and Send and Receive connectors used by the hybrid configuration.
You can specify multiple domains separated by commas.
@@ -141,6 +131,7 @@ You can specify multiple domains separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -150,9 +141,6 @@ Accept wildcard characters: False
```
### -EdgeTransportServers
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The EdgeTransportServers parameter specifies the Edge Transport servers that are configured to support the hybrid deployment features. The Edge Transport server must be accessible from the internet on port 25. Valid values are:
- The Edge Transport server FQDN (for example, edge.corp.contoso.com).
@@ -166,6 +154,7 @@ If you use this parameter, don't use the the ReceivingTransportServers and Sendi
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -175,9 +164,6 @@ Accept wildcard characters: False
```
### -ExternalIPAddresses
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ExternalIPAddresses parameter is a legacy parameter that specifies the publicly accessible inbound IP address of Microsoft Exchange Server 2010 Hub Transport servers.
You should use this parameter to change or clear legacy Exchange 2010 Hub Transport server IP address values only. IPv6 addresses aren't supported.
@@ -186,6 +172,7 @@ You should use this parameter to change or clear legacy Exchange 2010 Hub Transp
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -195,9 +182,6 @@ Accept wildcard characters: False
```
### -Features
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The Features parameter specifies the features that are enabled for the hybrid configuration. Valid values are:
- OnlineArchive: Enables the Exchange Online archive for on-premises Exchange and Exchange Online users.
@@ -215,6 +199,7 @@ You can specify multiple values separated by commas. When you use the Hybrid Con
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -224,15 +209,13 @@ Accept wildcard characters: False
```
### -OnPremisesSmartHost
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The OnPremisesSmartHost parameter specifies the FQDN of the on-premises Exchange Mailbox server used for secure mail transport between on-premises Exchange and Exchange Online.
```yaml
Type: SmtpDomain
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -242,9 +225,6 @@ Accept wildcard characters: False
```
### -ReceivingTransportServers
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The ReceivingTransportServers parameter specifies the Mailbox servers defined in the outbound connector configuration in Exchange Online. Valid values are:
- The Mailbox server FQDN (for example, mbx.corp.contoso.com).
@@ -260,6 +240,7 @@ Don't use this parameter with the EdgeTransportServers parameter. The value of t
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -269,9 +250,6 @@ Accept wildcard characters: False
```
### -SecureMailCertificateThumbprint
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to use as the certificate for hybrid deployment secure message transport. This certificate can't be self-signed, must be obtained from a trusted certification authority (CA), and must be installed on all Hub Transport servers specified in the TransportServers parameter.
@@ -280,6 +258,7 @@ The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -289,9 +268,6 @@ Accept wildcard characters: False
```
### -SendingTransportServers
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The SendingTransportServers parameter specifies the Mailbox servers defined in the inbound connector configuration in Exchange Online. Valid values are:
- The Mailbox server FQDN (for example, mbx.corp.contoso.com).
@@ -307,6 +283,7 @@ Don't use this parameter with the EdgeTransportServers parameter. The value of t
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -316,9 +293,6 @@ Accept wildcard characters: False
```
### -ServiceInstance
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is meaningful only in Office 365 operated by 21Vianet in China.
To manually configure a hybrid deployment with Office 365 operated by 21Vianet in China, set the value of this parameter to 1. Otherwise, the default value is 0.
@@ -329,6 +303,7 @@ All other Microsoft 365 organizations should use the Hybrid Configuration wizard
Type: Int32
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -338,9 +313,6 @@ Accept wildcard characters: False
```
### -TlsCertificateName
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. Valid syntax for this parameter is `"X.500IssuerX.500Subject"`:
- `X.500Issuer`: The value in the certificate's Issuer field.
@@ -354,6 +326,7 @@ Or, after you run Get-ExchangeCertificate to find the thumbprint value of the ce
Type: SmtpX509Identifier
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -363,9 +336,6 @@ Accept wildcard characters: False
```
### -TransportServers
-
-> Applicable: Exchange Server 2010
-
This parameter is available only in Exchange Server 2010.
The TransportServers parameter specifies the Hub Transport servers in Exchange Server 2010 SP2 or later that are configured to support hybrid deployment features.
@@ -378,6 +348,7 @@ You can specify multiple servers separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010
Required: False
Position: Named
@@ -387,15 +358,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md b/exchange/exchange-ps/exchange/New-InboundConnector.md
similarity index 92%
rename from exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md
rename to exchange/exchange-ps/exchange/New-InboundConnector.md
index bed3ce6485..ab3f7a8b2d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md
+++ b/exchange/exchange-ps/exchange/New-InboundConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-inboundconnector
applicable: Exchange Online, Exchange Online Protection
+title: New-InboundConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-inboundconnector
-schema: 2.0.0
-title: New-InboundConnector
+ms.reviewer:
---
# New-InboundConnector
@@ -77,15 +76,13 @@ This example creates the Inbound connector named Contoso Inbound Secure Connecto
## PARAMETERS
### -Name
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Name parameter specifies a descriptive name for the connector.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: 1
@@ -95,9 +92,6 @@ Accept wildcard characters: False
```
### -SenderDomains
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SenderDomains parameter specifies the source domains that a Partner type connector accepts messages for (limits the scope of a Partner type connector). A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, `*.contoso.com`). However, you can't embed the wildcard character (for example, `domain.*.contoso.com` isn't valid).
You can specify multiple domains separated by commas.
@@ -106,6 +100,7 @@ You can specify multiple domains separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: True
Position: Named
@@ -115,9 +110,6 @@ Accept wildcard characters: False
```
### -AssociatedAcceptedDomains
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The AssociatedAcceptedDomains parameter restricts the source domains that use the connector to the specified accepted domains. A valid value is an SMTP domain that's configured as an accepted domain in your Microsoft 365 organization.
You can specify multiple values separated by commas.
@@ -126,6 +118,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -135,15 +128,13 @@ Accept wildcard characters: False
```
### -ClientHostNames
-
-> Applicable: Exchange Online, Exchange Online Protection
-
{{ Fill ClientHostNames Description }}
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -153,9 +144,6 @@ Accept wildcard characters: False
```
### -CloudServicesMailEnabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
**Note**: We recommend that you don't use this parameter unless you are directed to do so by Microsoft Customer Service and Support, or by specific product documentation. Instead, use the Hybrid Configuration wizard to configure mail flow between your on-premises and cloud organizations. For more information, see [Hybrid Configuration wizard](https://learn.microsoft.com/exchange/hybrid-configuration-wizard).
The CloudServicesMailEnabled parameter specifies whether the connector is used for hybrid mail flow between an on-premises Exchange environment and Microsoft 365. Specifically, this parameter controls how certain internal X-MS-Exchange-Organization-\* message headers are handled in messages that are sent between accepted domains in the on-premises and cloud organizations. These headers are collectively known as cross-premises headers.
@@ -169,6 +157,7 @@ Valid values are:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -178,15 +167,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -196,9 +183,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -208,6 +192,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -217,9 +202,6 @@ Accept wildcard characters: False
```
### -ConnectorSource
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values:
- Default: The connector is manually created. This is the default value.
@@ -232,6 +214,7 @@ We recommended that you don't change this value.
Type: TenantConnectorSource
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -241,9 +224,6 @@ Accept wildcard characters: False
```
### -ConnectorType
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The ConnectorType parameter specifies the category for the source domains that the connector accepts messages for. Valid values are:
- Partner: External partners or services.
@@ -253,6 +233,7 @@ The ConnectorType parameter specifies the category for the source domains that t
Type: TenantConnectorType
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -262,9 +243,6 @@ Accept wildcard characters: False
```
### -EFSkipIPs
-
-> Applicable: Exchange Online, Exchange Online Protection
-
the EFSkipIPs parameter specifies the source IP addresses to skip in Enhanced Filtering for Connectors when the EFSkipLastIP parameter value is $false. Valid values are:
- Single IP address: For example, 192.168.1.1.
@@ -277,6 +255,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -286,9 +265,6 @@ Accept wildcard characters: False
```
### -EFSkipLastIP
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are:
- $true: Only the last message source is skipped.
@@ -298,6 +274,7 @@ The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connect
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -307,15 +284,13 @@ Accept wildcard characters: False
```
### -EFSkipMailGateway
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -325,15 +300,13 @@ Accept wildcard characters: False
```
### -EFTestMode
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -343,9 +316,6 @@ Accept wildcard characters: False
```
### -EFUsers
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The EFUsers parameter specifies the recipients that Enhanced Filtering for Connectors applies to. The default value is blank ($null), which means Enhanced Filtering for Connectors is applied to all recipients.
You can specify multiple recipient email addresses separated by commas.
@@ -354,6 +324,7 @@ You can specify multiple recipient email addresses separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -363,9 +334,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The Enabled parameter enables or disables the connector. Valid values are:
- $true: The connector is enabled. This is the default value.
@@ -375,6 +343,7 @@ The Enabled parameter enables or disables the connector. Valid values are:
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -384,9 +353,6 @@ Accept wildcard characters: False
```
### -RequireTls
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are:
- $true: Reject messages if they aren't sent over TLS. This is the default value
@@ -398,6 +364,7 @@ The RequireTLS parameter specifies whether to require TLS transmission for all m
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -407,9 +374,6 @@ Accept wildcard characters: False
```
### -RestrictDomainsToCertificate
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are:
- $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value.
@@ -421,6 +385,7 @@ The RestrictDomainsToCertificate parameter specifies whether the Subject value o
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -430,9 +395,6 @@ Accept wildcard characters: False
```
### -RestrictDomainsToIPAddresses
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are:
- $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter.
@@ -444,6 +406,7 @@ The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -453,15 +416,13 @@ Accept wildcard characters: False
```
### -ScanAndDropRecipients
-
-> Applicable: Exchange Online, Exchange Online Protection
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -471,9 +432,6 @@ Accept wildcard characters: False
```
### -SenderIPAddresses
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The SenderIPAddresses parameter specifies the source IPV4 IP addresses that the Partner type connector accepts messages from when the value of the RestrictDomainsToIPAddresses parameter is $true. Valid values are:
- Single IP address: For example, 192.168.1.1.
@@ -489,6 +447,7 @@ IPv6 addresses are not supported.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -498,15 +457,13 @@ Accept wildcard characters: False
```
### -TlsSenderCertificateName
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The TlsSenderCertificateName parameter specifies the TLS certificate that's used when the value of the RequireTls parameter is $true. A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, \*.contoso.com), but you can't embed the wildcard character (for example, domain.\*.contoso.com is not valid).
```yaml
Type: TlsCertificate
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -516,9 +473,6 @@ Accept wildcard characters: False
```
### -TreatMessagesAsInternal
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The TreatMessagesAsInternal parameter specifies an alternative method to identify messages sent from an on-premises organization as internal messages. You should only consider using this parameter when your on-premises organization doesn't use Exchange. Valid values are:
- $true: Messages are considered internal if the sender's domain matches a domain that's configured in Microsoft 365. This setting allows internal mail flow between Microsoft 365 and on-premises organizations that don't have Exchange Server 2010 or later installed. However, this setting has potential security risks (for example, internal messages bypass antispam filtering), so use caution when configuring this setting.
@@ -535,6 +489,7 @@ In hybrid environments, you don't need to use this parameter, because the Hybrid
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -544,9 +499,6 @@ Accept wildcard characters: False
```
### -TrustedOrganizations
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The TrustedOrganizations parameter specifies other Microsoft 365 organizations that are trusted mail sources (for example, after acquisitions and mergers). You can specify multiple Microsoft 365 organizations separated by commas.
This parameter works only for mail flow between two Microsoft 365 organizations, so no other parameters are used.
@@ -555,6 +507,7 @@ This parameter works only for mail flow between two Microsoft 365 organizations,
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
@@ -564,15 +517,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Online, Exchange Online Protection
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Online, Exchange Online Protection
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md b/exchange/exchange-ps/exchange/New-InboxRule.md
similarity index 85%
rename from exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md
rename to exchange/exchange-ps/exchange/New-InboxRule.md
index c9db1ab9c4..a3b0fe0e83 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md
+++ b/exchange/exchange-ps/exchange/New-InboxRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-inboxrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-InboxRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-inboxrule
-schema: 2.0.0
-title: New-InboxRule
+ms.reviewer:
---
# New-InboxRule
@@ -131,15 +130,13 @@ This example raises the message importance to High if the mailbox owner is in th
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies the name of the Inbox rule. The maximum length is 512 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -149,9 +146,6 @@ Accept wildcard characters: False
```
### -FromMessageId
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FromMessageId parameter specifies the message that's used to create the Inbox rule. The rule is based on the properties of the message. You identify the message by its Base64-encoded StoreObjectId property value. For example:
- MailboxId\\StoreObjectId
@@ -167,6 +161,7 @@ When you use this parameter to create an Inbox rule, the following message prope
Type: MailboxStoreObjectIdParameter
Parameter Sets: FromMessage
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -176,15 +171,13 @@ Accept wildcard characters: False
```
### -ValidateOnly
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. No changes are made when the ValidateOnly switch is used.
```yaml
Type: SwitchParameter
Parameter Sets: FromMessage
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -194,15 +187,13 @@ Accept wildcard characters: False
```
### -AlwaysDeleteOutlookRulesBlob
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -212,9 +203,6 @@ Accept wildcard characters: False
```
### -ApplyCategory
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ApplyCategory parameter specifies an action for the Inbox rule that applies the specified category to messages. A valid value is any text value that you want to define as a category. You can specify multiple categories separated by commas. If the value contains spaces, enclose the value in quotation marks (").
The categories that you specify for this parameter are defined in the mailbox (they aren't shared between mailboxes).
@@ -223,6 +211,7 @@ The categories that you specify for this parameter are defined in the mailbox (t
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -232,9 +221,6 @@ Accept wildcard characters: False
```
### -ApplySystemCategory
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ApplySystemCategory parameter specifies an action for the Inbox rule that applies the specified system category to messages. System categories are available to all mailboxes in the organization. Valid values are:
- NotDefined
@@ -268,6 +254,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -277,9 +264,6 @@ Accept wildcard characters: False
```
### -BodyContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The BodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the body of messages.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -292,6 +276,7 @@ The corresponding exception parameter to this condition is ExceptIfBodyContainsW
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -301,9 +286,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -313,6 +295,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -322,9 +305,6 @@ Accept wildcard characters: False
```
### -CopyToFolder
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The CopyToFolder parameter specifies an action for the Inbox rule that copies messages to the specified mailbox folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example:
@@ -346,6 +326,7 @@ Example values for this parameter are `john@contoso.com:\Marketing` or `John:\In
Type: MailboxFolderIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -355,9 +336,6 @@ Accept wildcard characters: False
```
### -DeleteMessage
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DeleteMessage parameter specifies an action for the Inbox rule that sends messages to the Deleted Items folder. Valid values are:
- $true: Messages that match the conditions of the rule are moved to the Deleted Items folder.
@@ -367,6 +345,7 @@ The DeleteMessage parameter specifies an action for the Inbox rule that sends me
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -376,9 +355,6 @@ Accept wildcard characters: False
```
### -DeleteSystemCategory
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DeleteSystemCategory parameter specifies an action for the Inbox rule that deletes the specified system category from messages. System categories are available to all mailboxes in the organization. Valid values are:
- NotDefined
@@ -412,6 +388,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -421,9 +398,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -432,6 +406,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -441,9 +416,6 @@ Accept wildcard characters: False
```
### -ExceptIfBodyContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the body of messages.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -456,6 +428,7 @@ The corresponding condition parameter to this exception is BodyContainsWords.
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -465,9 +438,6 @@ Accept wildcard characters: False
```
### -ExceptIfFlaggedForAction
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfFlaggedForAction parameter specifies an exception for the Inbox rule that looks messages with the specified message flag. Valid values are:
- Any
@@ -488,6 +458,7 @@ The corresponding condition parameter to this exception is FlaggedForAction.
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -497,9 +468,6 @@ Accept wildcard characters: False
```
### -ExceptIfFrom
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfFrom parameter specifies an exception for the Inbox rule that looks for the specified sender in messages. You can use any value that uniquely identifies the sender. For example:
- Name
@@ -517,6 +485,7 @@ The corresponding condition parameter to this exception is From.
Type: RecipientIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -526,9 +495,6 @@ Accept wildcard characters: False
```
### -ExceptIfFromAddressContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfFromAddressContainsWords parameter specifies an exception for the Inbox rule that looks for messages where the specified words are in the sender's email address.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -541,6 +507,7 @@ The corresponding condition parameter to this exception is FromAddressContainsWo
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -550,9 +517,6 @@ Accept wildcard characters: False
```
### -ExceptIfHasAttachment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfHasAttachment parameter specifies an exception for the Inbox rule that looks for messages with attachments. Valid values are:
- $true: The rule action isn't applied to messages that have attachments.
@@ -564,6 +528,7 @@ The corresponding condition parameter to this exception is HasAttachment.
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -573,9 +538,6 @@ Accept wildcard characters: False
```
### -ExceptIfHasClassification
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfHasClassification parameter specifies an exception for the Inbox rule that looks for messages with the specified message classification. You can find message classifications by using the Get-MessageClassification cmdlet. You can specify multiple message classifications separated by commas.
The corresponding condition parameter to this exception is HasClassification.
@@ -584,6 +546,7 @@ The corresponding condition parameter to this exception is HasClassification.
Type: MessageClassificationIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -593,9 +556,6 @@ Accept wildcard characters: False
```
### -ExceptIfHeaderContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The HeaderContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the header fields of messages.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -608,6 +568,7 @@ The corresponding condition parameter to this exception is HeaderContainsWords.
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -617,9 +578,6 @@ Accept wildcard characters: False
```
### -ExceptIfMessageTypeMatches
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfMessageTypeMatches parameter specifies an exception for the Inbox rule that looks for messages of the specified type. Valid values are:
- AutomaticReply
@@ -640,6 +598,7 @@ The corresponding condition parameter to this exception is MessageTypeMatches.
Type: InboxRuleMessageType
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -649,9 +608,6 @@ Accept wildcard characters: False
```
### -ExceptIfMyNameInCcBox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfMyNameInCcBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the Cc field. Valid values are:
- $true: The rule action isn't applied to messages where the mailbox owner is in the Cc field.
@@ -663,6 +619,7 @@ The corresponding condition parameter to this exception is MyNameInCcBox.
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -672,9 +629,6 @@ Accept wildcard characters: False
```
### -ExceptIfMyNameInToBox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfMyNameInToBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the To field. Valid values are:
- $true: The rule action isn't applied to messages where the mailbox owner is in the To field.
@@ -686,6 +640,7 @@ The corresponding condition parameter to this exception is MyNameInToBox.
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -695,9 +650,6 @@ Accept wildcard characters: False
```
### -ExceptIfMyNameInToOrCcBox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfMyNameInToOrCcBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the To or Cc fields Valid values are.
- $true: The rule action isn't applied to messages where the mailbox owner is in the To or Cc fields.
@@ -709,6 +661,7 @@ The corresponding condition parameter to this exception is MyNameInToOrCcBox.
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -718,9 +671,6 @@ Accept wildcard characters: False
```
### -ExceptIfMyNameNotInToBox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfMyNameNotInToBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner isn't in the To field. Valid values are:
- $true: The rule action isn't applied to messages where the mailbox owner isn't in the To field.
@@ -732,6 +682,7 @@ The corresponding condition parameter to this exception is MyNameNotInToBox.
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -741,9 +692,6 @@ Accept wildcard characters: False
```
### -ExceptIfReceivedAfterDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfReceivedAfterDate parameter specifies an exception for the Inbox rule that looks for messages received after the specified date.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -754,6 +702,7 @@ The corresponding condition parameter to this exception is ReceivedAfterDate.
Type: ExDateTime
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -763,9 +712,6 @@ Accept wildcard characters: False
```
### -ExceptIfReceivedBeforeDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfReceivedBeforeDate parameter specifies an exception for the Inbox rule that looks for messages received before the specified date.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -776,6 +722,7 @@ The corresponding condition parameter to this exception is ReceivedBeforeDate.
Type: ExDateTime
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -785,9 +732,6 @@ Accept wildcard characters: False
```
### -ExceptIfRecipientAddressContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfRecipientAddressContainsWords parameter specifies an exception for the Inbox rule that looks for messages where the specified words are in recipient email addresses.
You can specify multiple values separated by commas. The maximum length of this parameter is 255 characters.
@@ -798,6 +742,7 @@ The corresponding condition parameter to this exception is RecipientAddressConta
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -807,9 +752,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentOnlyToMe
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfSentOnlyToMe parameter specifies an exception for the Inbox rule that looks for messages where the only recipient is the mailbox owner. Valid values are:
- $true: The rule action isn't applied to messages where the mailbox owner is the only recipient.
@@ -821,6 +763,7 @@ The corresponding condition parameter to this exception is SentOnlyToMe.
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -830,9 +773,6 @@ Accept wildcard characters: False
```
### -ExceptIfSentTo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -850,6 +790,7 @@ The corresponding condition parameter to this exception is SentTo.
Type: RecipientIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -859,9 +800,6 @@ Accept wildcard characters: False
```
### -ExceptIfSubjectContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfSubjectContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field of messages.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -874,6 +812,7 @@ The corresponding condition parameter to this exception is SubjectContainsWords.
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -883,9 +822,6 @@ Accept wildcard characters: False
```
### -ExceptIfSubjectOrBodyContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfSubjectOrBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field or body of messages.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -898,6 +834,7 @@ The corresponding condition parameter to this exception is SubjectOrBodyContains
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -907,9 +844,6 @@ Accept wildcard characters: False
```
### -ExceptIfWithImportance
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfWithImportance parameter specifies an exception for the Inbox rule that looks for messages with the specified importance level. Valid values are:
- High
@@ -922,6 +856,7 @@ The corresponding condition parameter to this exception is WithImportance.
Type: Importance
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -931,9 +866,6 @@ Accept wildcard characters: False
```
### -ExceptIfWithinSizeRangeMaximum
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfWithinSizeRangeMaximum parameter specifies part of an exception for the Inbox rule that looks for messages that smaller than specified maximum size.
When you enter a value, qualify the value with one of the following units:
@@ -954,6 +886,7 @@ The corresponding condition parameter to this exception is WithinSizeRangeMaximu
Type: ByteQuantifiedSize
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -963,9 +896,6 @@ Accept wildcard characters: False
```
### -ExceptIfWithinSizeRangeMinimum
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfWithinSizeRangeMinimum parameter specifies part of an exception for the Inbox rule that looks for messages that are larger than the specified minimum size.
When you enter a value, qualify the value with one of the following units:
@@ -986,6 +916,7 @@ The corresponding condition parameter to this exception is WithinSizeRangeMinimu
Type: ByteQuantifiedSize
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -995,9 +926,6 @@ Accept wildcard characters: False
```
### -ExceptIfWithSensitivity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ExceptIfWithSensitivity parameter specifies an exception for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are:
- Normal
@@ -1011,6 +939,7 @@ The corresponding condition parameter to this exception is WithSensitivity.
Type: Sensitivity
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1020,9 +949,6 @@ Accept wildcard characters: False
```
### -FlaggedForAction
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FlaggedForAction parameter specifies a condition for the Inbox rule that looks for messages with the specified message flag. Valid values are:
- Any
@@ -1041,6 +967,7 @@ The FlaggedForAction parameter specifies a condition for the Inbox rule that loo
Type: String
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1050,9 +977,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet.
@@ -1061,6 +985,7 @@ A confirmation prompt warns you if the mailbox contains rules that were created
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1070,9 +995,6 @@ Accept wildcard characters: False
```
### -ForwardAsAttachmentTo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ForwardAsAttachmentTo parameter specifies an action for the Inbox rule that forwards the message to the specified recipient as an attachment. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -1088,6 +1010,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1097,9 +1020,6 @@ Accept wildcard characters: False
```
### -ForwardTo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ForwardTo parameter specifies an action for the Inbox rule that forwards the message to the specified recipient. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -1115,6 +1035,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1124,9 +1045,6 @@ Accept wildcard characters: False
```
### -From
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The From parameter specifies a condition for the Inbox rule that looks for the specified sender in messages. You can use any value that uniquely identifies the sender. For example:
- Name
@@ -1144,6 +1062,7 @@ The corresponding exception parameter to this condition is ExceptIfFrom.
Type: RecipientIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1153,9 +1072,6 @@ Accept wildcard characters: False
```
### -FromAddressContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The FromAddressContainsWords parameter specifies a condition for the Inbox rule that looks for messages where the specified words are in the sender's email address.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -1168,6 +1084,7 @@ The corresponding exception parameter to this condition is ExceptIfFromAddressCo
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1177,9 +1094,6 @@ Accept wildcard characters: False
```
### -HasAttachment
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The HasAttachment parameter specifies a condition for the Inbox rule that looks for messages with attachments. Valid values are:
- $true: The rule action is applied to messages that have attachments.
@@ -1191,6 +1105,7 @@ The corresponding exception parameter to this condition is ExceptIfHasAttachment
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1200,9 +1115,6 @@ Accept wildcard characters: False
```
### -HasClassification
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The HasClassification parameter specifies a condition for the Inbox rule that looks for messages with the specified message classification. You can find message classifications by using the Get-MessageClassification cmdlet. You can specify multiple message classifications separated by commas.
The corresponding exception parameter to this condition is ExceptIfHasClassification.
@@ -1211,6 +1123,7 @@ The corresponding exception parameter to this condition is ExceptIfHasClassifica
Type: MessageClassificationIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1220,9 +1133,6 @@ Accept wildcard characters: False
```
### -HeaderContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The HeaderContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the header fields of messages.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -1235,6 +1145,7 @@ The corresponding exception parameter to this condition is ExceptIfHeaderContain
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1244,9 +1155,6 @@ Accept wildcard characters: False
```
### -Mailbox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
- Name
@@ -1264,6 +1172,7 @@ The Mailbox parameter specifies the mailbox that contains the Inbox rule. You ca
Type: MailboxIdParameter
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1273,9 +1182,6 @@ Accept wildcard characters: False
```
### -MarkAsRead
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MarkAsRead parameter specifies an action for the Inbox rule that marks messages as read. Valid values are:
- $true: Messages that match the conditions of the rule are marked as read.
@@ -1285,6 +1191,7 @@ The MarkAsRead parameter specifies an action for the Inbox rule that marks messa
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1294,9 +1201,6 @@ Accept wildcard characters: False
```
### -MarkImportance
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MarkImportance parameter specifies an action for the Inbox rule that marks messages with the specified importance flag. Valid values are:
- Low
@@ -1307,6 +1211,7 @@ The MarkImportance parameter specifies an action for the Inbox rule that marks m
Type: Importance
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1316,9 +1221,6 @@ Accept wildcard characters: False
```
### -MessageTypeMatches
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MessageTypeMatches parameter specifies a condition for the Inbox rule that looks for messages of the specified type. Valid values are:
- AutomaticReply
@@ -1339,6 +1241,7 @@ The corresponding exception parameter to this condition is ExceptIfMessageTypeMa
Type: InboxRuleMessageType
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1348,9 +1251,6 @@ Accept wildcard characters: False
```
### -MoveToFolder
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MoveToFolder parameter specifies an action for the Inbox rule that moves messages to the specified mailbox folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
For the value of `MailboxID`, you can use any value that uniquely identifies the mailbox. For example:
@@ -1372,6 +1272,7 @@ Example values for this parameter are `john@contoso.com:\Marketing` or `John:\In
Type: MailboxFolderIdParameter
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1381,9 +1282,6 @@ Accept wildcard characters: False
```
### -MyNameInCcBox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MyNameInCcBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the Cc field. Valid values are:
- $true: The rule action is applied to messages where the mailbox owner is in the Cc field.
@@ -1395,6 +1293,7 @@ The corresponding exception parameter to this condition is ExceptIfMyNameInCcBox
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1404,9 +1303,6 @@ Accept wildcard characters: False
```
### -MyNameInToBox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MyNameInToBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the To field. Valid values are:
- $true: The rule action is applied to messages where the mailbox owner is in the To field.
@@ -1418,6 +1314,7 @@ The corresponding exception parameter to this condition is ExceptIfMyNameInToBox
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1427,9 +1324,6 @@ Accept wildcard characters: False
```
### -MyNameInToOrCcBox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MyNameInToOrCcBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the To or Cc fields Valid values are.
- $true: The rule action is applied to messages where the mailbox owner is in the To or Cc fields.
@@ -1441,6 +1335,7 @@ The corresponding exception parameter to this condition is ExceptIfMyNameInToOrC
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1450,9 +1345,6 @@ Accept wildcard characters: False
```
### -MyNameNotInToBox
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The MyNameNotInToBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner isn't in the To field. Valid values are:
- $true: The rule action is applied to messages where the mailbox owner isn't in the To field.
@@ -1464,6 +1356,7 @@ The corresponding exception parameter to this condition is ExceptIfMyNameNotInTo
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1473,9 +1366,6 @@ Accept wildcard characters: False
```
### -PinMessage
-
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The PinMessage parameter specifies an action for the Inbox rule that pins messages to the top of the Inbox. Valid values are:
- $true: Message that match the conditions of the rule are pinned to the top of the Inbox.
@@ -1485,6 +1375,7 @@ The PinMessage parameter specifies an action for the Inbox rule that pins messag
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1494,15 +1385,13 @@ Accept wildcard characters: False
```
### -Priority
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Priority parameter specifies a priority for the Inbox rule that determines the order of rule processing. A lower integer value indicates a higher priority,
```yaml
Type: Int32
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1512,9 +1401,6 @@ Accept wildcard characters: False
```
### -ReceivedAfterDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReceivedAfterDate parameter specifies a condition for the Inbox rule that looks for messages received after the specified date.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -1525,6 +1411,7 @@ The corresponding exception parameter to this condition is ExceptIfReceivedAfter
Type: ExDateTime
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1534,9 +1421,6 @@ Accept wildcard characters: False
```
### -ReceivedBeforeDate
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The ReceivedBeforeDate parameter specifies a condition for the Inbox rule that looks for messages received before the specified date.
Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
@@ -1547,6 +1431,7 @@ The corresponding exception parameter to this condition is ExceptIfReceivedBefor
Type: ExDateTime
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1556,9 +1441,6 @@ Accept wildcard characters: False
```
### -RecipientAddressContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RecipientAddressContainsWords parameter specifies a condition for the Inbox rule that looks for messages where the specified words are in recipient email addresses.
You can specify multiple values separated by commas. The maximum length of this parameter is 255 characters.
@@ -1569,6 +1451,7 @@ The corresponding exception parameter to this condition is ExceptIfRecipientAddr
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1578,9 +1461,6 @@ Accept wildcard characters: False
```
### -RedirectTo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The RedirectTo parameter specifies an action for the Inbox rule that redirects the message to the specified recipient. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -1596,6 +1476,7 @@ You can enter multiple values separated by commas. If the values contain spaces
Type: RecipientIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1605,9 +1486,6 @@ Accept wildcard characters: False
```
### -SendTextMessageNotificationTo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The SendTextMessageNotificationTo parameter specifies an action for the Inbox rule that send a text message notification to the specified telephone number.
@@ -1618,6 +1496,7 @@ You can specify multiple values separated by commas.
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -1627,9 +1506,6 @@ Accept wildcard characters: False
```
### -SentOnlyToMe
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SentOnlyToMe parameter specifies a condition for the Inbox rule that looks for messages where the only recipient is the mailbox owner. Valid values are:
- $true: The rule action is applied to messages where the mailbox owner is the only recipient.
@@ -1641,6 +1517,7 @@ The corresponding exception parameter to this condition is ExceptIfSentOnlyToMe.
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1650,9 +1527,6 @@ Accept wildcard characters: False
```
### -SentTo
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SentTo parameter specifies a condition for the Inbox rule that looks for messages with the specified recipients. You can use any value that uniquely identifies the recipient. For example:
- Name
@@ -1670,6 +1544,7 @@ The corresponding exception parameter to this condition is ExceptIfSentTo.
Type: RecipientIdParameter[]
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1679,9 +1554,6 @@ Accept wildcard characters: False
```
### -SoftDeleteMessage
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
{{ Fill SoftDeleteMessage Description }}
@@ -1690,6 +1562,7 @@ This parameter is available only in the cloud-based service.
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -1699,9 +1572,6 @@ Accept wildcard characters: False
```
### -StopProcessingRules
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The StopProcessingRules parameter specifies an action for the Inbox rule that stops processing additional rules if the conditions of this Inbox rule are met. Valid values are:If set to $true, the StopProcessingRules parameter instructs Exchange to stop processing additional rules if the conditions of this Inbox rule are met.
- $true: Stop processing more rules.
@@ -1711,6 +1581,7 @@ The StopProcessingRules parameter specifies an action for the Inbox rule that st
Type: Boolean
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1720,9 +1591,6 @@ Accept wildcard characters: False
```
### -SubjectContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SubjectContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field of messages.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -1735,6 +1603,7 @@ The corresponding exception parameter to this condition is ExceptIfSubjectContai
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1744,9 +1613,6 @@ Accept wildcard characters: False
```
### -SubjectOrBodyContainsWords
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The SubjectOrBodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field or body of messages.
To specify multiple words or phrases, use the following syntax: `Word1,"Phrase with spaces",word2,...wordN`. Don't use leading or trailing spaces.
@@ -1759,6 +1625,7 @@ The corresponding exception parameter to this condition is ExceptIfSubjectOrBody
Type: MultiValuedProperty
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1768,15 +1635,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1786,9 +1651,6 @@ Accept wildcard characters: False
```
### -WithImportance
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WithImportance parameter specifies a condition for the Inbox rule that looks for messages with the specified importance level. Valid values are:
- High
@@ -1801,6 +1663,7 @@ The corresponding exception parameter to this condition is ExceptIfWithImportanc
Type: Importance
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1810,9 +1673,6 @@ Accept wildcard characters: False
```
### -WithinSizeRangeMaximum
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WithinSizeRangeMaximum parameter specifies part of a condition for the Inbox rule that looks for messages that are smaller than specified maximum size.
When you enter a value, qualify the value with one of the following units:
@@ -1833,6 +1693,7 @@ The corresponding exception parameter to this condition is ExceptIfWithinSizeRan
Type: ByteQuantifiedSize
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1842,9 +1703,6 @@ Accept wildcard characters: False
```
### -WithinSizeRangeMinimum
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WithinSizeRangeMinimum parameter specifies part of a condition for the Inbox rule that looks for messages that are larger than the specified minimum size.
When you enter a value, qualify the value with one of the following units:
@@ -1865,6 +1723,7 @@ The corresponding exception parameter to this condition is ExceptIfWithinSizeRan
Type: ByteQuantifiedSize
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -1874,9 +1733,6 @@ Accept wildcard characters: False
```
### -WithSensitivity
-
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WithSensitivity parameter specifies a condition for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are:
- Normal
@@ -1890,6 +1746,7 @@ The corresponding exception parameter to this condition is ExceptIfWithSensitivi
Type: Sensitivity
Parameter Sets: Identity
Aliases:
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md b/exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md
similarity index 94%
rename from exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md
rename to exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md
index 8b9e46152e..0e1826be8c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md
+++ b/exchange/exchange-ps/exchange/New-InformationBarrierPolicy.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-informationbarrierpolicy
applicable: Security & Compliance
+title: New-InformationBarrierPolicy
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailflow-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-informationbarrierpolicy
-schema: 2.0.0
-title: New-InformationBarrierPolicy
+ms.reviewer:
---
# New-InformationBarrierPolicy
@@ -91,15 +90,13 @@ This example creates a policy that allows the *Research* segment to communicate
## PARAMETERS
### -Name
-
-> Applicable: Security & Compliance
-
The Name parameter specifies a unique name for the information barrier policy that you want to create. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: 0
@@ -109,15 +106,13 @@ Accept wildcard characters: False
```
### -AssignedSegment
-
-> Applicable: Security & Compliance
-
The AssignedSegment parameter specifies the Name value of segment that you want to include in the information barrier policy. You can find existing segments by running the following command: `Get-OrganizationSegment | Format-List Name,UserGroupFilter`.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -127,15 +122,13 @@ Accept wildcard characters: False
```
### -SegmentAllowedFilter
-
-> Applicable: Security & Compliance
-
This parameter is reserved for internal Microsoft use.
```yaml
Type: String
Parameter Sets: OrganizationSegmentAllowedFilter
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -145,9 +138,6 @@ Accept wildcard characters: False
```
### -SegmentsAllowed
-
-> Applicable: Security & Compliance
-
The SegmentsAllowed parameter specifies the segments that are allowed to communicate with the segment in this policy (users defined by the AssignedSegment parameter). Only these specified segments can communicate with the segment in this policy.
You identify the segment by its Name value. If the value contains spaces, enclose the value in quotation marks ("). You can specify multiple segments separated by commas ("Segment1","Segment2",..."SegmentN").
@@ -158,6 +148,7 @@ You can't use this parameter with the SegmentsBlocked parameter.
Type: MultiValuedProperty
Parameter Sets: OrganizationSegmentsAllowed
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -167,9 +158,6 @@ Accept wildcard characters: False
```
### -SegmentsBlocked
-
-> Applicable: Security & Compliance
-
The SegmentsBlocked parameter specifies the segments that aren't allowed to communicate with the segment in this policy (users defined by the AssignedSegment parameter). You can specify multiple segments separated by commas ("Segment1","Segment2",..."SegmentN").
You identify the segment by its Name value. If the value contains spaces, enclose the value in quotation marks ("). You can specify multiple segments separated by commas ("Segment1","Segment2",..."SegmentN").
@@ -180,6 +168,7 @@ You can't use this parameter with the SegmentsAllowed parameter.
Type: MultiValuedProperty
Parameter Sets: OrganizationSegmentsBlocked
Aliases:
+Applicable: Security & Compliance
Required: True
Position: Named
@@ -189,15 +178,13 @@ Accept wildcard characters: False
```
### -Comment
-
-> Applicable: Security & Compliance
-
The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -207,15 +194,13 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Security & Compliance
-
The Confirm switch doesn't work on this cmdlet.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -225,9 +210,6 @@ Accept wildcard characters: False
```
### -Force
-
-> Applicable: Security & Compliance
-
The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
@@ -236,6 +218,7 @@ You can use this switch to run tasks programmatically where prompting for admini
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -245,15 +228,13 @@ Accept wildcard characters: False
```
### -ModerationAllowed
-
-> Applicable: Security & Compliance
-
{{ Fill ModerationAllowed Description }}
```yaml
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -263,9 +244,6 @@ Accept wildcard characters: False
```
### -State
-
-> Applicable: Security & Compliance
-
The State parameter specifies whether the information barrier policy is active or inactive. Valid values are:
- Active
@@ -276,6 +254,7 @@ Type: EopInformationBarrierPolicyState
Parameter Sets: (All)
Aliases:
Accepted values: Inactive, Active
+Applicable: Security & Compliance
Required: False
Position: Named
@@ -285,15 +264,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Security & Compliance
-
The WhatIf switch doesn't work in Security & Compliance PowerShell.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Security & Compliance
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md b/exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md
similarity index 91%
rename from exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md
rename to exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md
index dd86a9f2b3..4e22683783 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/exchange/New-IntraOrganizationConnector.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-intraorganizationconnector
applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-IntraOrganizationConnector
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-intraorganizationconnector
-schema: 2.0.0
-title: New-IntraOrganizationConnector
+ms.reviewer:
---
# New-IntraOrganizationConnector
@@ -50,15 +49,13 @@ This example creates an Intra-Organization connector named "MainCloudConnector"
## PARAMETERS
### -Name
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Name parameter specifies a friendly name for the Intra-Organization connector. If the value contains spaces, enclose the value in double quotation marks.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: 1
@@ -68,15 +65,13 @@ Accept wildcard characters: False
```
### -DiscoveryEndpoint
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The DiscoveryEndpoint parameter specifies the externally-accessible URL that's used for the Autodiscover service for the domain that's configured in the Intra-Organization connector.
```yaml
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -86,9 +81,6 @@ Accept wildcard characters: False
```
### -TargetAddressDomains
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The TargetAddressDomains parameter specifies the domain namespaces that will be used in the Intra-organization connector. These domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity.
You specify multiple domain values separated by commas.
@@ -97,6 +89,7 @@ You specify multiple domain values separated by commas.
Type: MultiValuedProperty
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: True
Position: Named
@@ -106,9 +99,6 @@ Accept wildcard characters: False
```
### -Confirm
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
@@ -118,6 +108,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -127,9 +118,6 @@ Accept wildcard characters: False
```
### -DomainController
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
-
This parameter is available only in on-premises Exchange.
The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
@@ -138,6 +126,7 @@ The DomainController parameter specifies the domain controller that's used by th
Type: Fqdn
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
Required: False
Position: Named
@@ -147,9 +136,6 @@ Accept wildcard characters: False
```
### -Enabled
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The Enabled parameter enables or disabled the Intra-organization connector. The valid values for this parameter are $true or $false. The default value is $true.
When you set the value to $false, you completely stop connectivity for the specific connection.
@@ -158,6 +144,7 @@ When you set the value to $false, you completely stop connectivity for the speci
Type: Boolean
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
@@ -167,9 +154,6 @@ Accept wildcard characters: False
```
### -TargetSharingEpr
-
-> Applicable: Exchange Online
-
This parameter is available only in the cloud-based service.
The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services that will be used in the Intra-Organization connector.
@@ -178,6 +162,7 @@ The TargetSharingEpr parameter specifies the URL of the target Exchange Web Serv
Type: Uri
Parameter Sets: (All)
Aliases:
+Applicable: Exchange Online
Required: False
Position: Named
@@ -187,15 +172,13 @@ Accept wildcard characters: False
```
### -WhatIf
-
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
-
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
Required: False
Position: Named
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md b/exchange/exchange-ps/exchange/New-JournalRule.md
similarity index 87%
rename from exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md
rename to exchange/exchange-ps/exchange/New-JournalRule.md
index 0103a92195..2812bcf0ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md
+++ b/exchange/exchange-ps/exchange/New-JournalRule.md
@@ -1,13 +1,12 @@
---
+external help file: Microsoft.Exchange.TransportMailControl-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-journalrule
applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+title: New-JournalRule
+schema: 2.0.0
author: chrisda
-external help file: Microsoft.Exchange.TransportMailControl-Help.xml
-Locale: en-US
-Module Name: ExchangePowerShell
ms.author: chrisda
-online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-journalrule
-schema: 2.0.0
-title: New-JournalRule
+ms.reviewer:
---
# New-JournalRule
@@ -35,7 +34,7 @@ New-JournalRule -Name -JournalEmailAddress